Get started

Discover / beggar-bot-demand.beggarbot.workers.dev

Beggar Bot

● Live

Decode an x402 X-PAYMENT / PAYMENT-SIGNATURE header, recover the EIP-3009 signer and match it against 402 requirements; explains facilitator rejections. Pure compute.

Listed price
$0.02
Chain
Base
Paid in
USDC
Live
2 of the last 2 checks
Median response
306 ms
Last checked
8 Nov, 06:22 UTC
In our index since
6 Nov 2026

Our probes look for a payment challenge. They don't test payment or delivery.

Endpoint

curl -i https://beggar-bot-demand.beggarbot.workers.dev/v1/paymentheader
8 listed endpoints · on x402 Bazaar

Checks and payment terms on this page refer to the endpoint above. Other listed endpoints have not been checked individually.

Base URLhttps://beggar-bot-demand.beggarbot.workers.dev/v1

  • GET/gasfee$0.02EIP-1559 gas fee oracle before an agent sends a tx: next base fee, slow/standard/fast maxFeePerGas + priority fee (feeHistory percentiles), congestion, OP-stack L1 data fee upper bound, USD cost of transfer/ERC-20/USDC EIP-3009/swap/Safe exec presets or your gas_limit. Base default; optimism, ethereum, arbitrum, polygon.
  • GET/portfolio$0.02Wallet portfolio enrichment: native ETH + holdings across 24 curated top Base tokens (stables, LSTs, cbBTC, AERO, VIRTUAL, memes) plus your tokens=, each priced on-chain (Uniswap v3/Aerodrome) -> balances, USD values, total, account type. Keyless RPC, fails soft.
  • GET/tokeninfo$0.02ERC-20 token metadata enrichment for agents, ≤20 tokens per call: name, symbol (incl. bytes32), decimals, formatted supply, optional holder balance, spam / USDC-impersonator flags, verdict. Keyless public RPC, Base default.
  • GET/addrprofile$0.02Wallet/address risk profile for agents: EOA vs contract vs EIP-7702 smart-EOA vs proxy (EIP-1967/1167/Safe), implementation/delegate, nonce, native + USDC balance, known labels, 0-100 risk band. Base default; ethereum/optimism/arbitrum/polygon via keyless public RPC, fails soft.
  • GET/nftmeta$0.02NFT decode (ERC-721/1155): owner, tokenURI with ipfs/arweave gateway + inline base64 JSON metadata (name, image, attributes), ERC-2981 royalty, holder ownership, spam/centralized flags. Keyless RPC.
  • GET/tokenprice$0.02On-chain token price for agents, ≤4 tokens/call: spot USD price from Uniswap v3 slot0 + Aerodrome reserves (pools derived by CREATE2, no indexer, no API key), deepest pool by quote-side liquidity, cross-pool spread, thin-liquidity/divergence flags, confidence. Base default; ethereum.
  • POST/paymentheader$0.02Decode an x402 X-PAYMENT / PAYMENT-SIGNATURE header, recover the EIP-3009 signer and match it against 402 requirements; explains facilitator rejections. Pure compute.
  • GET/txsummary$0.02Transaction summary by hash: status, decoded method, fee (incl. L1 fee), all token transfers + approvals, net token flows per address, flags, one-line headline. Base default; ethereum/op/arb/polygon. Keyless RPC.

A dash means the listing gives no price or method. Copy buttons copy the full URL.

Showing 8 of 8 listed endpoints.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/beggar-bot-demand.beggarbot.workers.dev

Recent checks

6 Nov 2026Taller coloured bars mean slower responses; grey means not live.8 Nov 2026
All 2 checks
When (UTC)ResultHTTPResponse
8 Nov, 06:22 UTCLive402226ms
6 Nov, 12:24 UTCLive402386ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 8 Nov, 06:22 UTC, it returned HTTP 402 or another detected payment-challenge signal.

What payment terms does Beggar Bot advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Something wrong on this page? Tell us.