pitcrew-
pitcrew-
Check any x402 paid endpoint before paying it: does it return a valid 402 challenge, which networks/tokens/prices it accepts (decoded to USD), whether amounts are valid atomic units, payTo sanity, testnet-only offers, missing Bazaar input schema, redirects and latency. Returns a verdict (payable / payable with warnings / broken / unreachable) and the exact problems. Useful for agents choosing between paid APIs and for sellers debugging why x402scan or the CDP Bazaar skipped their route.
Live
Last successful check: 26 Oct 2026, 09:00 UTC.
- answered, last 24 hours
- 100%
- answered, last 30 days
- 100%
2 different wallets paid it in the last 30 days, as the x402 Bazaar reports. Payments
How addrbook checks →Connect
https:x402: an unpaid request gets a 402 with the price and pay-to wallet. addrbook never pays.
Who's behind it
- Listed by
- x402 Bazaarlast seen UTC
- Wallets named
- 0xb442dacae60c07bb5db8f33c8a6c1572d8f24e83named by x402 Bazaar
- Listed since
Payments
- different wallets paid it, last 30 days
- 2
- paid calls, last 30 days
- 2
- last paid call (UTC)
As the x402 Bazaar reports, from payments Coinbase's facilitator settled. Read . addrbook has not counted these payments itself.
How it asks to be paid
| Network | Price | Paid in | Settled by | Pays to |
|---|---|---|---|---|
| Base | $0.005 | USDC | Per request | 0xb442dacae60c07bb5db8f33c8a6c1572d8f24e83 |
| Arbitrum | $0.005 | USDC | Per request | 0xb442dacae60c07bb5db8f33c8a6c1572d8f24e83 |
From its own 402 answer at UTC. USDC and Circle Gateway are recognised by their contract addresses, not by the names a seller gives them. How payments are read
Checks by endpoint
| Host | Protocol | State | Last checked (UTC) | Last answered (UTC) | 24 hours | 30 days | Tools |
|---|---|---|---|---|---|---|---|
| pitcrew- | x402 | Live | 100% | 100% | — |
Also listed as
Other entries that share an endpoint with this one.