Request: index/test Satoshi API x402 endpoints

[Bortlesboat]

Hi Merit/x402scan team - could you sanity-check indexing/discovery for Satoshi API?

Production mainnet surface:

• https://bitcoinsapi.com/x402
• https://bitcoinsapi.com/.well-known/x402
• https://bitcoinsapi.com/openapi.json
• AgentCash currently discovers 10 paid x402 endpoints from OpenAPI.

Stable Base Sepolia proof origin:

• https://x402.bitcoinsapi.com
• https://x402.bitcoinsapi.com/.well-known/x402
• https://x402.bitcoinsapi.com/openapi.json
• AgentCash: npx agentcash@latest discover https://x402.bitcoinsapi.com --format json
• Paid test route: npx agentcash@latest fetch 'https://x402.bitcoinsapi.com/merchant-payout-plan?batchSize=24&targetBlocks=3&urgency=balanced'

CDP search and merchant discovery both saw the proof origin after tx 0x30ff7b33ec19dff3d77373794584b40315ce497942bfe6f2b064a28e7d56e7d5; CDP resources had not yet picked it up when checked.

Could you try indexing/discovery and reply with the first failure or metadata mismatch you see? Totally fine to close if this belongs somewhere else.

[lww54200]

@lww54200 Taking a look at indexing/discovery for the Satoshi API x402 endpoints. Will report back with findings on any failures or metadata mismatches.

[lww54200]

Indexing/Discovery Test Results for Satoshi API x402 Endpoints

Production Mainnet (�itcoinsapi.com)

✅ Status: All endpoints accessible and properly configured

• https://bitcoinsapi.com/x402 → HTTP 200, returns valid x402 config (v2)
• https://bitcoinsapi.com/.well-known/x402 → Returns complete seller config with 10 paid resources
• https://bitcoinsapi.com/openapi.json → Valid OpenAPI 3.1.0 spec with x-payment-info annotations

Discovered Resources (10 endpoints):

1. /api/v1/fees/landscape - .005 - Bitcoin fee landscape
2. /api/v1/ai/fees/advice - .01 - AI fee advice
3. /api/v1/mining/nextblock - .01 - Next-block fee forecast
4. /api/v1/ai/explain/transaction/{txid} - .01 - Transaction explainer
5. /api/v1/fees/observatory/scoreboard - .005 - Fee estimator scoreboard
6. /api/v1/ai/explain/block/{hash_or_height} - .01 - Block explainer
7. /api/v1/ai/chat - .01 - Bitcoin Q&A chat
8. /api/v1/broadcast - .01 - Broadcast transaction
9. /api/v1/fees/observatory/block-stats - .005 - Block fee stats
10. /api/v1/fees/observatory/estimates - .005 - Multi-source fee estimates

Config Details:

• Network: eip155:8453 (Base mainnet)
• Asset:

[Bortlesboat]

Thanks for checking the production surface - this is useful. Two small follow-ups:

1. The second result comment appears to cut off after Asset:, so I may be missing the rest of your findings.
2. Could you also sanity-check the stable Base Sepolia proof origin when you get a chance?

Shell-safe commands:

npx agentcash@latest discover https://x402.bitcoinsapi.com --format json
npx agentcash@latest fetch 'https://x402.bitcoinsapi.com/merchant-payout-plan?batchSize=24&targetBlocks=3&urgency=balanced'

The production mainnet confirmation already gives us one useful external-discovery signal; the remaining question is whether the testnet proof origin indexes/discovers cleanly too.

[Bortlesboat]

Small follow-up: I tightened the external test handoff so reviewers do not have to infer command order from the catalog.

Tester kit: https://x402.bitcoinsapi.com/x402-facilitator/tester.json

It includes:

• no-wallet 402 check: curl -i "https://x402.bitcoinsapi.com/weather"
• cheapest paid HTTP call: npx agentcash@latest fetch "https://x402.bitcoinsapi.com/weather"
• merchant paid route: npx agentcash@latest fetch "https://x402.bitcoinsapi.com/merchant-payout-plan?batchSize=24&targetBlocks=3&urgency=balanced"
• MCP status: curl https://mcp.bitcoinsapi.com/status

Public MCP is now live too, and a paid MCP buyer run settled on Base Sepolia: 0x27f2db0c850823bf1e6c4f35a589106e00f39cc96a5ecf68e9a164184c3d79f1.

Current discovery state from my side: CDP search sees the proof origin; CDP resources still does not return it, so that remains a useful failure surface to confirm or explain.

If you try one thing, the most useful reply is just one label plus first failure: discovery_ok, 402_metadata_mismatch, paid_fetch_failed, paid_fetch_succeeded, or outside_scope.