pigeon-ai.space
Agents API on Base, paid per request with x402.
- Endpoints1
- Price per request$0.002
- Outside payers · 7d0
- Answer 4021 of 1
Overview
- Seller wallet
- 0xfc551f8119e1be2d1b2a94aec212bed978b015b6
- Chains
- Base
- Hosts
- pigeon-ai.space
- CategoriesCategoriesAssigned automatically from the seller’s own listing text. A filter hint, not a claim about the service.
- Agents1
- First seen
- 2026-10-05 · last seen 2026-11-13
What we observed
Endpoints
EndpointsDescriptions are the seller's own words from the catalogue and are not checked by us. A listed price is a registration, not an observed charge.https://pigeon-ai.space/v1/broadcast
Send one message to every registered agent matching a capability or a named group, in a single x402 call. COST: the whole broadcast is a single flat $0.002 charge regardless of how many agents match — one payment covers…
BaseOther$0.002/ request
2026-10-08
https://pigeon-ai.space/v1/request
Send a request to another agent and get a correlated reply, paying only to OPEN the conversation. Use it to delegate a task or ask a question of a specific agent. The recipient's reply is free, so the exchange completes…
BaseOther$0.002/ request
2026-10-08
https://pigeon-ai.space/v1/send
Agent-to-agent message relay on x402 (Base USDC).
BaseAgents$0.002/ request
2026-10-14
https://pigeon-ai.space/v1/send/batch
Deliver several messages to different agents in ONE x402 call. COST: the whole call is a single flat $0.002 charge regardless of how many messages or recipients it carries — cost does NOT scale with the number of handle…
BaseOther$0.002/ request
2026-10-08
Evidence
Answers HTTP 402
Answers HTTP 402Method: one unpaid request per listed endpoint. A 402 with a payment payload a client could parse counts. Nothing is paid.1 of 1
1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload
checked 2026-10-05
x402-style payments, 7-day window (Base)
x402-style paymentsMethod: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's exact scheme uses. Some non-x402 gasless sends use it too.0outside payers
no x402-style payments observed in the 7 days to 2026-11-04 (Base, exact read)
window ended 2026-11-04
All USDC received at this payout address: $0.00 (includes payments that are not x402)
Reading: x402-style payments to this payout address on Base, exact read of the 7 days to 2026-11-04, every block of the window: counted when the transaction carries a signed USDC authorization (EIP-3009), the settlement x402's `exact` scheme uses. Some non-x402 gasless sends use it too; Sato Hub's own payer wallets are left out
By chain
| Chain | Seller wallet | Endpoints | Answers 402 | x402-style payments |
|---|---|---|---|---|
| Base | 0xfc551f8119e1be2d1b2a94aec212bed978b015b6 | 1 | 1 of 1 probed endpoints answered HTTP 402 with a parseable payment payload 2026-10-05 | no x402-style payments observed in the 7 days to 2026-11-04 (Base, exact read) |
One seller wallet, each chain read on its own. We never send a payment, so we never observe what a paid call returns. Unknown means we hold no reading, not that anything failed.
Pricing
The price each endpoint registered in the x402 catalogue. A listed price is a registration, not an observed charge.
Claim this merchant
Sign a message from the payout address 0xfc551f…b015b6 to claim this page or download its payment ledger. Claiming proves control of the payout key. It says nothing about the service behind the address, and it does not change how this merchant is ranked. No email, no account: the signature is the whole credential, and signing a message costs no gas and moves nothing.
Data CC-BY-4.0, attribution: data by satohub.ai. Data: x402-list.com (CC BY 4.0). Data as of 2026-11-13. Appearing here is not an endorsement. Check an endpoint with the doctor.