261–270 of 532 posts
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.
Earlier quoted context omitted.
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.
The user could log into his personal OpenRouter account, authorize your application, and optionally set a budget, all in something like a Stripe payment screen.
Hm. This seems random. Other than the fact that they are both technology companies, is there anything else that they have in common?
7 million would sound fair to me. 7 billion? Explain yourself.
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…
Every single Open Banking implementation I know also requires everyone to go through a useless certified middleman (eg. Plaid, GoCardless, ...) instead of letting people use the APIs directly
Earlier quoted context omitted.
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.
Because the others are cheaper
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…
7 million would sound fair to me. 7 billion? Explain yourself.
Earlier quoted context omitted.
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.
Could there be use cases where you want to run inference for users in your app, but don't want to host your own backend, user authentication, and billing? The user could log into his personal OpenRouter account, authorize your application, and optionally set a budget, all in something like a Stripe payment screen.
Like standard oauth?