Live data from Hacker News

OpenRouter is joining Stripe

openrouter.ai

241–250 of 532 posts

Re: OpenRouter is joining Stripe

#241
post #124

On acquisition pricing: Why smarter AI models could drive up compute prices 10x (at least temporarily). This seems mind blowing, but the big boys seem to be behaving as if it's directionally true. If compute is constrained and expensive, OpenRouter is what you'll use to get around the constraints at individual providers. https://x.com/dwarkesh_sp/status/2084333160075055122?s=20

It seems like a misunderstanding of basic economics to assume that the price for this would track FTE salaries.

Re: OpenRouter is joining Stripe

#242
post #199
post #130

Earlier quoted context omitted.

And... How do they combine? I really curious.

Their business models are actually kind of similar. Stripe is just passing money between financial institutions and taking a small cut. OpenRouter is basically the same thing. They might have shared ability on how to run an effective pass through business.

So… they’re both middlemen. And that’s enough to justify a $7B acquisition???

Re: OpenRouter is joining Stripe

#243
post #32

Hm. This seems random. Other than the fact that they are both technology companies, is there anything else that they have in common?

Stripe has a lot of money, but not a lot of AI-buzzword compliance. OpenRouter is highly AI-buzzword compliant, but doesn't have a lot of money. It's a match made in heaven

Re: OpenRouter is joining Stripe

#245
post #221
post #202

Earlier quoted context omitted.

That's what OpenRouter already does, so the Stripe value add here is still unclear

Not OP, but I could see the vision. Right now OpenRouter is developer-paid with no way to pass costs onto the end user. Stripe could help bill and meter at the user level for per-user billing. I would also think more SDKs/easier ways to add AI features (paid for via openrouter) into apps and websites.

Open router supports per-request usage metering, as well as per-key. Building user-level metering from this is trivial, and there are many implementations of this out there. Supporting per-user first-class is trivial considering Open router already has per-request and already supports per-request attribution. How important that is, is a big question, but definitely not something that requires Stripe to build.

Re: OpenRouter is joining Stripe

#246

I rather have protocols be built and less middlemen PaaS. One great example is Open Banking. I would support an Open Router that mirrors Open Banking, unfortunately the Open here doesn’t carry the same connotation. Kudos to the team for succeeding in executing around a clear DX issue during the chaos of providers, though long term I am not really a fan of it staying as is even if Stripe gets to be the one carrying it…

What open banking? I can't even get a read-only token for my personal use to see the balance on my account and I sit two team calls away from people who cooked the API

Deleted. I don’t like starting rage baits… ;)

Re: OpenRouter is joining Stripe

#247
post #65

Earlier quoted context omitted.

Curious on what OpenRouter's true moat is? It's just an LLM API routing framework, right?

OpenRouter’s “moat” is currently “why would I use anything else?”. Stripe has presumably only purchased them because they think there’s consumer-surplus to monetize here, which presumably will soon be giving me lots of reasons to use something else.

It isn't clear to me what advantages OpenRouter has over running a similar router-aggregator locally for ~free. I guess they have stronger bargaining power than a solo engineer or small startup, and can therefore negotiate volume discounts with model providers. The question is if those discounts let them offer cheaper rates than a local router-aggregator even after the markup. And if they can do that, then OpenRouter is undercutting the providers themselves on price, which I would imagine the providers would not want to see.

Re: OpenRouter is joining Stripe

#248
post #205
post #183

Earlier quoted context omitted.

Every token/llm provider already has usage metering...so not sure what exactly you're imagining stripe adds here

A single policy location for multiple models with usage limits/rate limits, spend limits all configurable using a common syntax + deep integration with account levels and high visibility into subscription/payments related to meter usage to help understand whether or not your pricing model is underwater as costs change is exceptionally valuable. AFAIK each product consuming model providers without an openrouter style…

You're just describing what OpenRouter already does?

Re: OpenRouter is joining Stripe

#249
post #191

AI products are going to have to deal with accounting. An agent performs some work. It uses some models and perhaps some other metered services. Someone has to meter that activity. They have to attribute costs, apply the product's pricing rules, bill the customer, collect, reconcile with vendors, and maintain the ledger. Stripe can use OpenRouter to build the financial and accounting infrastructure for every product…

At some point AI will be able to deal with the repetitive and template based parts of accounting better than accounting. Which is saying a lot.

I'm not sure that's true. LLMs seem too unreliable for accounting.
Post reply on HN