The supported-providers table assumes the router holds a credential for every upstream it sends traffic to, the self-hosted row being the only one with nothing to supply.
There is a shape missing there: an upstream that charges for the call itself instead of presenting a key. BlockRun is an OpenAI-compatible endpoint where chat, image, video, music, speech and sound effects all sit behind one base URL and each call settles on its own in USDC over x402. No account, no API key, nothing to configure on the security policy side because there is no credential at all. Docs and the endpoint list are at https://blockrun.ai.
Does a provider like that belong in the table, and would a page beside the existing connect-providers ones make sense? Happy to write it in the same shape as the others if it does, and fine to hear that a paid upstream with no credential is out of scope by design.
The supported-providers table assumes the router holds a credential for every upstream it sends traffic to, the self-hosted row being the only one with nothing to supply.
There is a shape missing there: an upstream that charges for the call itself instead of presenting a key. BlockRun is an OpenAI-compatible endpoint where chat, image, video, music, speech and sound effects all sit behind one base URL and each call settles on its own in USDC over x402. No account, no API key, nothing to configure on the security policy side because there is no credential at all. Docs and the endpoint list are at https://blockrun.ai.
Does a provider like that belong in the table, and would a page beside the existing connect-providers ones make sense? Happy to write it in the same shape as the others if it does, and fine to hear that a paid upstream with no credential is out of scope by design.