[pixel_popping]

You are not allowed to resell Openrouter as an API yourself, so for example if you make a service that charge per token, you can't use Openrouter API for that, this is specified in their ToS, so no, you can't do what you want, what FUD?

Quote from their own TOS: access the Site or Service for purposes of reselling API access to AI Models or otherwise developing a competing service;

[embedding-shape]

Yeah, you're not allowed to do things that are specifically spelled out in the ToS, how is this surprising? Of course you don't get "unlimited access to do whatever you technically can", APIs never worked like that, why would they suddenly work like that?

When you say "you don't have the right to do what you want with the API Key" it makes it sound like specific use cases are disallowed, or something similar. "You don't have the right to go against the ToS, for some reason they block you then!" would have been very different, and of course it's like that.

Bit like complaining that Stripe is preventing you from accepting credit card payments for narcotics. Yes, just because you have an API key doesn't mean somehow you can do whatever you want.

[pixel_popping]

That's very different from the Stripe example, as opening a service like Openrouter isn't illegal, so that's only coming from it being opinionated, nothing to do with the law. And my example was for not so specific use cases but quite general one which is just to open let say a service like Opencode Zen and use Openrouter as a backend, this is explicity forbidden by Openrouter and it isn't against the law, that's not just a "niche use case".

Are we allowed yes or not to make a service that charge per Token to end-users, like giving access to Kimi K2.5 to end-users through Openrouter in a pay per token basis?