Skip to main content
AgentKey gives your agent the same providers through two surfaces. They share one key, one balance and one console; they differ in who decides which upstream tool runs and what the response looks like.

​
Side by side

Methods are deliberately fewer than catalog tools: one method aggregates every endpoint with the same capability, and only operations whose contract and normalized output can be kept stable are promoted. See Why fewer methods than catalog tools.

​
When to use which

Reach for a Scenario Method when the capability is covered and you will parse the result in code: searching posts on a platform, fetching a product or a quote, scraping a page into markdown. You get one schema to code against, failover you don’t have to build, and a price you can budget. Reach for the catalog when you need an operation the methods don’t expose — a niche endpoint, a parameter only one provider has, a platform that has no method yet — or when the caller is an LLM that can read a tool description and adapt. The catalog is where every new provider appears first.
Both surfaces can be mixed in one agent. A common pattern: Scenario Methods for the hot paths your product depends on, find_tools for the rest.

​
What’s the same

  • One key. The ak_... master key authenticates both.
  • One balance. Credits are shared; agentkey_account reports it for both.
  • One set of providers. A Scenario Method is a contract on top of the same catalog tools; describe shows which tool each provider binding calls.

Scenario Methods

The REST surface: contract, routing, pricing, errors.

Discover → Describe → Execute

How agents use the catalog through MCP.