Skip to main content
AnyAPI ships an official Agent Skill that teaches your agent the AnyAPI workflow — discover an API, read its schema, run it, and handle pricing and errors correctly. It complements the MCP server: the skill teaches the workflow; MCP provides the live tools. The skill also works without MCP by falling back to plain REST.
Which page do you want? This page is for integrating AnyAPI into your app — your coding agent runs against a key on your funded account (it can mint one for you and you claim it, or you create one in the dashboard), and the app is the caller in production. If instead you’re running an autonomous agent that calls AnyAPI itself at runtime, it provisions and holds its own key — see Let your agent onboard itself.

​
Install

Works with every agent that reads .agents/skills/:

​
Setup

The skill handles the key for you. On first use it reads ANYAPI_API_KEY; if that’s empty, it asks which email to tie the account to and mints a key — no dashboard trip.
1

Already have a key? Export it

The skill reads the key from the environment — it never hardcodes credentials:
No key yet? Skip this step — the skill provisions one on first use.
2

Let the skill provision a key

With nothing in ANYAPI_API_KEY, the skill asks for your email and calls the public self-signup endpoint, drops the new key into the environment, and starts working on a small starter credit. It never prints the secret.
3

Claim it for the full credit

The starter key is capped and expires in 7 days until you claim it. Sign in at the dashboard with that email, open API keys → Claim agent key, and paste the claim token the skill shows you. Claiming lifts the cap, makes the key permanent, and adds your one-time $1 account credit — the same key keeps working, now on your funded wallet.
4

Ask for data

Ask your agent for third-party data — “get the top posts in r/golang”, “scrape this TikTok profile” — and it will discover the right API, check the per-request USD price, and run it.

​
What the skill covers

  • The discover → inspect → run flow over MCP or REST.
  • Cost discipline: reading nested flat or linear USD offers, estimating bulk-job cost up front, and checking the wallet balance.
  • Result semantics: the {found, data} envelope — a found: false is a successful answer, not an error.
  • Error handling: every machine-readable error prefix and what the agent should do about each (none are charged).
Prefer giving your agent live tools instead of (or alongside) the skill? Connect the MCP server directly.