Omniagent looks quite similar to OpenRouter (https://openrouter.ai/). - Source: Hacker News / 17 days ago

It's very easy to use other providers. See https://openrouter.ai/ which also let's you filter by where the provider is hosted and their data retention policy. - Source: Hacker News / 2 months ago

If you want to try it yourself: grab OpenCode, point it at OpenRouter, select GLM 5.2, and give it a real task instead of a benchmark. The z.ai docs have the rest of the details. - Source: dev.to / 2 months ago

Hosted, minimal ops. You want to be calling models in five minutes and you are fine paying a small fee for it. OpenRouter is the marketplace default — 400+ models, ~5.5% on credits. Vercel AI Gateway and Cloudflare AI Gateway go further and charge 0% markup, billing you at provider list price while adding routing and caching on top. - Source: dev.to / 2 months ago

I use OpenRouter as the single door to a pile of models. Its BYOK (bring-your-own-key) feature has a trap. You add your own OpenAI key for a model, flip on "Always use for this provider," and read that as never spend OpenRouter credits. It doesn't mean that. - Source: dev.to / 3 months ago

'id' data type and field to help support caching: https://graphql.org/learn/caching/. Source: over 3 years ago

> Take a look at this. I repeat: client-side caching is not a problem, even with GraphQL. The technical problems regarding GraphQL's blockers to caching lies in server-side caching. For server-side caching, the only answer that GraphQL offers is to use primary keys, hand-wave a lot, and hope that your GraphQL implementation did some sort of optimization to handle that corner case by caching results. Don't take my... - Source: Hacker News / over 4 years ago

> Checkout Relay.js: https://relay.dev/ Relay is a GraphQL client. That's the irrelevant side of caching, because that can be trivially implemented by an intern, specially given GraphQL's official copout of caching based on primary keys [1], and doesn't have any meaningful impact on the client's resources. The relevant side of caching is server-side caching: the bits of your system that allow it to fulfill... - Source: Hacker News / over 4 years ago

This is clever! Can anyone help me understand how this lines up with the original value proposition of GraphQL? I was under the impression that the Big Idea behind GraphQL was, amongst other things, client-side caching[1]. I’m probably missing some nuance here, so bear with me: if your GraphQL client is caching properly, then what would this syntax give a developer that a URL query parameter parser couldn’t? [1]... - Source: Hacker News / about 5 years ago