> Tokens are simply a lightweight valuable asset
(Not picking on you here, you just provided a well-written peg for a popular narrative. I'm aiming to sharpen my own thinking here & perhaps learn something.)
This seems like a stretch given the rise of local inference, especially the Prism Labs rumors from a few weeks ago.
One way I think about LLMs is they are akin to fancy databases in that they are software of which you can ask questions and get answers if you ask properly. Oracle & SQL Server are akin to OpenAI and Anthropic, and there are analogues for MySQL, PostgreSQL, SQLite, MongoDB, PlanetScale, etc. (This is an analogy, it's not going to be a perfect fit.)
In that view, would it make sense for someone to say that their credit card processor just bought the company that makes their ODBC driver? Would anybody suggest that the TPS of their RDS instance is a lightweight asset?
I don't see this as strategic beyond the obvious idea that Stripe wants to get closer to AI, and they haven't been able to get the market to care about their natural linkage to AI (Radar).
> they can start hosting their own models and competing as an AWS for tokens
The financial pressure of doing this has caused cuts to core product teams at the richest companies (which Stripe isn't!). I would not want my payments processor to go down this road and to get worse at processing payments.
> would it make sense for someone to say that their credit card processor just bought the company that makes their ODBC driver? Would anybody suggest that the TPS of their RDS instance is a lightweight asset?
Would is make sense to say that their online bookstore now sells Ethernet cables, bidets, and delivers groceries? Sells _cloud infrastructure_??
Amazon made two transitions:
1. Amazon the online bookseller => Amazon "The Everything Store"
2. Amazon the online retailer => Amazon the Cloud Services company
I believe what Stripe is doing here is closer to (1). "We are good at high-throughput APIs that wrap complexity with thin margins. We did it for credit cards, then ~all payment methods, now other digital bits."
In this context, tokens are much, much easier than international payments.
Now: Is it outlandish for their customers?
Not really. Every engineer knows stripe as an engineering company. I don't think Stripe is what it once was, but it's certainly a generational company. You're asking engineers—who broadly have a positive impression of Stripe—to use this product they already know. OpenRouter gets the positive brand association (trust) of Stripe; Stripe expands into a new domain whose technical needs are extremely similar.
Your simplification itself is compressing away the meaningful point, and then you're confused about your own over-simplification.
Stripe is not a "credit card processor", and that's not the point of OP's comment. The point is that being the intermediary between merchants and processors is the valuable expertise in terms of an OpenRouter acquisition.
It's been a few years, but I used to work on almost exactly this (not at Stripe, but we processed hundreds of billions annually). If you're a big enough merchant (or Stripe itself), you can choose to send a credit card transaction to any one of potentially many processors, each of which have their own performance characteristics (one may approve at a higher rate, the other may charge better fees, etc). All of this subject to attributes of the transaction itself (ticket size, geography, card type, many others). You know quite a bit about the transaction itself before you send it out, so you can build up routing knowledge to optimize for whatever thing you care about (usually transaction success rates or fees).
See how this starts to look a lot like OpenRouter with money instead of tokens? I'm not sure I 100% believe that's how it'll shake out, but there is a transferable skillset.