Skip to main content
From one prompt, the agent installs the AnyAPI skills, mints its own free trial key, and makes its first call. You create no account and hand over no credentials. When the trial budget runs out, one human approval keeps it going.
This page is for an autonomous agent that calls AnyAPI at runtime. If a coding agent is integrating AnyAPI into an app you’ll ship, create a dashboard key on your funded account and see Agent skills. Trial keys have a small budget and expire in 7 days, so they do not belong in shipped code.

The one thing you do

Prompt your agent:
To have the agent spend from your funded account instead, hand it an API key and skip the trial.

What the agent does on its own

1

Installs the CLI (if it has a shell)

An agent with a shell runs one command that installs the skills, mints the trial key, and writes local credentials:
anyapi init also offers MCP registration and saves the key to ~/.anyapi/config.json. After init, the agent calls the anyapi binary directly.
2

Mints its own free trial key

Without a shell (a hosted chat or no-code runtime), the agent posts to the public signup endpoint:
The body is optional; label tags the key. The response returns the key once, plus the upgrade details:
The agent stores secret as ANYAPI_API_KEY and relays notice to you verbatim.
3

Starts working immediately

The agent lists APIs, reads schemas, checks its USD balance, and runs calls over MCP, the CLI, or REST.

What it costs you to start

Nothing. A trial key carries about $0.05 of requests (capUsd), creates no account, and self-expires in 7 days if never upgraded.
When the trial budget is spent, calls return HTTP 402 with error code trial_cap_reached and an upgrade object in the body. Approve continued spend below.

Upgrade past the trial

Continuing takes one human approval through OAuth 2.1. You approve a spend limit, and the agent keeps working on the same session without a new key. Approve from your personal account. A trial can’t be continued on a Team.
Connect the MCP server for live tools, or use the CLI to keep tool schemas out of the agent’s context window.