Skip to content

Coinslot

Serves small paid API calls, each settled in USDC over HTTP 402 with no signup, for agents and humans.
At a glanceswept Oct 24, 2026

not read yet

Use

For
AI agents that need micro APIs they can pay for per call in USDC via x402
Runs as
API
Used for
  • Fetch the machine-readable API catalog index
  • Pay for single API calls in USDC without signing up
  • Try a free small-response sample call before paying
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 26, 2026
  • MCP serverdev.coinslot/coinslotverified in the MCP registry
  • Stateanswers, 13 toolschecked 2026-10-26
  • Address to connectcoinslot.dev/mcp
  • API docscoinslot.dev/docs.htmlthe vendor's page ↗

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 Coinslot with

Pick up to two.

All 10 alternatives to Coinslot →

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 Coinslot for?

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

    Serves small paid API calls, each settled in USDC over HTTP 402 with no signup, for agents and humans. It is listed in the Atlas under Developer tools.

  • Who is Coinslot for?

    AI agents that need micro APIs they can pay for per call in USDC via x402

  • Do people use Coinslot?

    Little sign of use.

  • What are alternatives to Coinslot?

    In Developer tools, by use: Context Mode, Locus, LinkList, Karada.ai, Not Human Search, RMCP.

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