the agentic api layer that learns how you build. talk to any coding agent, we pick the best api for the task, set up the keys without asking, and rotate them for the rest of the project. usage tracking as the input to a self-tuning system.
cursor, claude code, whatever you already use. you don't change anything about how you build.
routed based on your past usage, for this kind of task, in this region, at this time. no input from you.
provisioned, stored, rotated. no .env. no google doc. no cto babysitting every token your company uses.
"your geocoding queries succeed 23% more when routed to geoapify for the sf area, so we made it your default." that.
your agent is brilliant and blind. it reasons about anything, but it can't see which api is fastest in your region or which key hasn't rate-limited today. invariant is the routing and memory layer that closes the gap.
no. invariant fronts a single key. we hold the provider accounts, absorb the rate limits, and rotate keys for you. you never touch a .env file or sign up for a vendor.
routing is scored from real usage history: accuracy, success rate, latency, and cost for this kind of task in your region. the best-value provider wins the call, and the decision re-tunes as new results come in.
its score drops automatically. we cut its traffic, reroute your calls to the rival, and re-provision keys. zero manual steps on your side.
over mcp or plain http. point your coding agent at one endpoint, authenticate once, and every wired provider is callable through the same key.
you pay for what your agents actually use. invariant fronts the real per-call vendor cost and meters it back transparently. no per-seat lock-in.