Skip to content
Toolcall logo

Toolcall

Pay-per-call HTTP APIs, paid in USDC on Base via x402, offering crypto gas prices, FX rates, domain and email checks, and chemical safety lookups.
At a glanceswept Oct 20, 2026

not read yet

Use

For
Developers and AI agents calling pay-per-call data and lookup APIs over HTTP
Runs as
API
Used for
  • check a domain's registration age and mail setup
  • verify email deliverability without sending any mail
  • fetch chemical hazard data by CAS number
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 23, 2026
  • MCP serverclick.toolcall/toolcallverified in the MCP registry
  • Stateanswers, 20 toolschecked 2026-10-23
  • Address to connecttoolcall.click/mcp
  • OpenAPI spec20 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Toolcall with

Pick up to two.

All 10 alternatives to Toolcall →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Toolcall for?

Sign in to leave a note
Questions this page answers
  • What is Toolcall?

    Pay-per-call HTTP APIs, paid in USDC on Base via x402, offering crypto gas prices, FX rates, domain and email checks, and chemical safety lookups. It is listed in the Atlas under Developer tools.

  • Who is Toolcall for?

    Developers and AI agents calling pay-per-call data and lookup APIs over HTTP

  • Do people use Toolcall?

    Little sign of use.

  • What are alternatives to Toolcall?

    In Developer tools, by use: APITier, Verifox AI, UptyBots, SMTPfast, Agentery, Skinwinking.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk