Beggar Bot

Base USDC payment verification, address risk scores and signed receipts for AI agents, $0.01 per call via x402. Routes: GET /v1/verify, GET /v1/risk, POST /v1/receipt. MCP: https://github.com/beggar-bot-x402/beggar-bot-mcp

1 of 3 routes settlement-verified · $0.02 USDC/request · 3 endpoints / 3 tools · Data · base network · x402 protocol

Verified routes

• GET /v1/verify · $0.02 · Verified with a $0.02 test payment on 31 Oct 2026 · receipt

Other routes are unverified.

Networks: Base (settlement-verified)

Discovery is free. Agents search the catalogue here. Payment happens on the listing 402, not on PayAPI.

url https://payapi.market/mcp

Listing facts

Provider

Beggar Bot

Hosted at

beggar-bot-demand.beggarbot.workers.dev

Category

Data

Price

$0.02 USDC per request

Endpoints

3

MCP tools

3

Payment networks

Base

Settlement-verified

1 route, last checked 2026-10-31

Listed on PayAPI Market

2026-10-25

Try Beggar Bot

Call a verified route without paying first. The server should answer HTTP 402 Payment Required with the price, the USDC asset, the network and the wallet to pay. An x402 client pays that amount on Base and retries with the payment header.

curl -i "https://beggar-bot-demand.beggarbot.workers.dev/v1/verify"

About this API

Beggar Bot is listed in the Data category with pricing at $0.02 USDC/request. One route has been settlement-verified by PayAPI Market on 2026-10-31. View receipt on Basescan.

Payments settle on base in USDC via the x402 protocol. AI agents discover this API through the PayAPI Market MCP server and pay per request without API keys or accounts.

This API exposes 3 endpoints. Only the verified route has been tested by PayAPI Market. Other routes are unverified.

Questions about this API

What does Beggar Bot do?

Base USDC payment verification, address risk scores and signed receipts for AI agents, $0.01 per call via x402. Routes: GET /v1/verify, GET /v1/risk, POST /v1/receipt. MCP: https://github.com/beggar-bot-x402/beggar-bot-mcp It is provided by Beggar Bot.

How much does Beggar Bot cost?

Beggar Bot is priced at $0.02 USDC per request, paid per call with no subscription. Verified with a $0.02 test payment on 31 Oct 2026. The exact amount for each call is in the HTTP 402 response before any money moves.

Do I need an API key or account to use Beggar Bot?

No. Beggar Bot uses the x402 protocol, so an agent pays per request in USDC on Base and gets the response, with no API key, account or signup.

Has Beggar Bot been verified?

Yes, 1 route of its 3 endpoints. PayAPI Market paid for a real call from its own wallet, received real data back and recorded the USDC settlement on-chain, most recently on 2026-10-31. Routes that were not paid for are unverified.

How does an AI agent find Beggar Bot?

Through the free PayAPI Market MCP server at https://payapi.market/mcp, using search_apis or get_api, or over plain HTTP at https://payapi.market/agent/search. Discovery is free; the agent pays the provider directly on the listing's own 402.

More Data APIs · Browse the marketplace · List your own API

Related APIs

• EefRead · 1 route verified · Send any public URL, get back clean readable text plus title, word count and fetch metadata. Scripts, styles, nav and comments stripped server-side; 20,000-character cap with an explicit truncated flag; private and link-local addresses refused. No key, no signup.
• Base32 length check · 1 route verified · RFC 4648 or Crockford base32 alphabet and length check. Decoded bytes are not returned. Unknown input returns 404 and is not charged.
• HTTP status code · 1 route verified · IANA HTTP status code meaning. Unassigned codes return 404 and are not charged. Not a live server status.
• UUID version and variant · 1 route verified · RFC 9562 version and variant bits for a UUID. Malformed values return 404 and are not charged. Not a registry lookup.
• Semantic version compare · 1 route verified · Semantic Versioning 2.0.0 precedence for two versions. Build metadata is ignored. Invalid versions return 404 and are not charged. Not a package registry.
• File extension media type · 1 route verified · Apache httpd mime.types media type for a file extension. Unknown extensions return 404 and are not charged. Not a filename lookup and not a content sniff.

More from Beggar Bot

• Beggar Bot x402 Agent Utilities
• View all from Beggar Bot

By Beggar Bot