ApiToll

Load one skill. Ask in plain English.

Drop our skill into Claude, Cowork, or any agent that reads markdown skills. Then ask for any reference data we sell — the agent handles the wallet, signs the payment, calls the API, returns the answer.

Step 1

Load the skill into your agent.

Two paths:

Programmatic agent (Claude desktop, Cowork, MCP): paste this URL where your agent accepts a skill URL:

https://apitoll.io/skill/SKILL.md

Local skill folder (Claude Code, etc.): drop these files into your skills directory:

Download SKILL.md ↓ Python client ↓ Node client ↓ services.json ↓

Live catalog (always current): apitoll.io/v1/services

Step 2

Ask in natural language.

The skill triggers on any reference-data question. Examples that work:

What’s the EUR/USD rate? Geolocate 8.8.8.8 Public holidays in Japan 2026 What bank issued BIN 424242? Dialling code for South Africa
Step 3

Done.

Your agent will:

  • generate or detect a Base Sepolia wallet
  • ask you to fund it (~$0.50 from a faucet) on the first call
  • sign EIP-3009 and call the matching service
  • return the answer + the on-chain settlement tx

Subsequent calls are just typing.

What’s in the skill

One file, all of apitoll.

The skill covers every service we sell — today and going forward. When we add a service, you don’t reinstall anything; the agent re-fetches SKILL.md and the new service is just there.

  • Service router. The skill knows how to map “EUR/USD rate” → fx-rates, “is this card from Japan?” → bin-lookup, etc.
  • Wallet handling. Generates a sandbox-only test wallet on first run; remembers it for subsequent calls.
  • x402 round-trip. Handles 402 → sign EIP-3009 → retry → 200. You don’t need to know the protocol.
  • Sandbox by default. Free test USDC, curated fixtures. Production switch requires explicit user confirmation.
  • Error recovery. If the call fails (insufficient balance, payment rejected, data not found), the skill explains what to do.

Who this works with

Any agent that reads markdown skills.

The skill is a plain markdown file with frontmatter. It works wherever you can hand an agent a markdown skill:

  • Claude Code / Cowork — load via the skills directory or paste the URL.
  • Claude desktop — supports skills directly.
  • Custom agents — whatever your agent loads into its system prompt or tool registry.
  • Other models — the markdown is generic; if your agent can read it, it can use it.

The skill instructs the agent to fetch apitoll_client.py if it doesn’t already have it — ~250 lines of Python with two pure-Python deps (requests, eth-account). No compilation, no x402 SDK, no Node required.

If you prefer to integrate by hand

The DIY path is still here.

Not every buyer wants the skill abstraction. If you’d rather code the integration yourself, the catalog detail pages document the wire format directly — /agents/ has the round-trip explained step by step, and every service catalog page (fx-rates, bin-lookup, etc.) has an inline curl-style quickstart.

The skill and the DIY path call the same endpoints. You can mix — agents using the skill, your backend using your own client.