Skip to content
EntRoute logo

EntRoute

Ranks and probe-verifies pay-per-request x402 API endpoints so agents can discover and call them, paid in USDC.

At a glanceswept 2026-10-13

34 installs/mo

Emerging

For
AI agents and developers who need to discover and call pay-per-request APIs at runtime
Price
Price not read
Activity
Maintainedrelease 6 months ago · site updated 3 months ago
Company
Domain since 2026domain registered
Runs as
API
What people do with it
  • find ranked, verified pay-per-request API endpoints for a capability
  • look up current DeFi token prices
  • get DeFi swap quotes between tokens
The companyeach fact with its source · read 2026-10-14
  • Domain since2026domain registered
How a program reaches itfound, not claimed · read 2026-10-14
  • MCP servercom.entroute/entrouteverified in the MCP registry
  • Stateanswers, 3 toolschecked 2026-10-14
  • Address to connectmcp.entroute.com/mcp

MCP server details →

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

All Developer tools tools →

Questions this page answers
  • What is EntRoute?

    Ranks and probe-verifies pay-per-request x402 API endpoints so agents can discover and call them, paid in USDC. It is listed in the Atlas under Developer tools.

  • Who is EntRoute for?

    AI agents and developers who need to discover and call pay-per-request APIs at runtime

  • Do people use EntRoute?

    Emerging: 34 installs/mo (npm).

  • Is EntRoute still maintained?

    Maintained: release 6 months ago · site updated 3 months ago.

  • What are alternatives to EntRoute?

    In Developer tools, by use: CROO, AI Infrastructure Tools Directory at Infrabase.ai, Nango, DocVerify, Replay.io Agent, Manifest.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

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.