AP
Payments · x402 · early usage
Builds an advisory failover ladder for caller-supplied x402 facilitator and network opt…
Builds an advisory failover ladder for caller-supplied x402 facilitator and network options.
by api.blockchainmoneymap.com · discovered, not yet claimed by its owner · updated 2026-10-05
30d calls2
30d payers2
MethodPOST
Outputjson
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Builds an advisory failover ladder for caller-supplied x402 facilitator and network options.
Tags: bazaar
Call contract
- Method
- POST
- Input
- json
- Output
- json
- Last paid call
- 2026-10-05
Input example from Bazaar metadata
{
"facts": {
"allowed_networks": [
"eip155:8453",
"eip155:137"
],
"duplicate_settlement_caution_present": true,
"fallback_policy": "try secondary facilitator then manual review",
"manual_review_policy": "stop if both facilitators fail",
"primary_facilitator": "production-facilitator-a",
"secondary_facilitator": "production-facilitator-b",
"settlement_caveats": "manual review for duplicate settlement warnings"
},
"mode": "analyze"
}No output exampleProvider did not publish one in Bazaar metadata.
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/39675.jsonfor the price and payment options. - Pay. Call
GET https://api.blockchainmoneymap.com/api/x402/x402-multi-chain-facilitator-failover-planner. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.01 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 2 calls · 2 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.01 | 0x2211E12e6Bc8Da27B48B9DD66A55f5C3388D713a | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x2211E12e6Bc8Da27B48B9DD66A55f5C3388D713a",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "10000",
"amountUsd": 0.01,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"type": "json"
}Example shape — generated from the schema, not a captured live response
nullExamples
curl
curl "https://api.blockchainmoneymap.com/api/x402/x402-multi-chain-facilitator-failover-planner"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidJavaScript
const res = await fetch("https://api.blockchainmoneymap.com/api/x402/x402-multi-chain-facilitator-failover-planner");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}Python
import httpx
res = httpx.get("https://api.blockchainmoneymap.com/api/x402/x402-multi-chain-facilitator-failover-planner")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- api.blockchainmoneymap.com
- Endpoint
- https://api.blockchainmoneymap.com/api/x402/x402-multi-chain-facilitator-failover-planner
- Machine-readable
/resources/39675.json