Back to Browse
Blockchain Money Map x402 Failure Fact Classifier
x402
Blockchain Money Map x402 Failure Fact Classifier is a paid API for AI agents from api.blockchainmoneymap.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).
Classifies and diagnoses x402 payment protocol failure facts by comparing actual vs expected payment parameters to identify the root cause of a failed x402 transaction.
Price / call$0.01
Success—
StatusUnknown
How this service works
Choose Blockchain Money Map for human-readable public blockchain reports or x402-paid agent API services.
Output
A JSON response containing the classification of the x402 payment failure, identifying the failure category, likely root cause, and potentially actionable diagnostics based on the comparison between the provided failure facts and expected payment parameters.
Example use cases
Debug x402 challenge step failure
“My x402 agent hit an HTTP 402 on /api/reports and failed during the challenge step — the facilitator returned error code 'scheme.unsupported' on Base network for a 0.01 USDC payment to receiver 0xABC123. Can you classify what went wrong?”
Diagnose x402 amount mismatch in production
“In production, my client 'MyAgent v1.2' failed to settle an x402 payment at the retry step — the expected amount was 0.05 USDC but the actual was 0.01 USDC on Ethereum, and the target returned error 'amount.insufficient'. Classify this x402 failure for me.”
Identify x402 receiver mismatch error
“During integration testing, my x402 payment to resource /api/v1/data on Base failed at the sign step with target error code 'receiver.mismatch' — expected receiver was 0xDEF456 but actual receiver was 0xXYZ789. What category of x402 failure is this?”
Technical details
Endpoint
POSThttps://api.blockchainmoneymap.com/api/x402/x402-failure-fact-classifierWhen to prefer
Choose this endpoint when an AI agent or integration needs to programmatically diagnose why a specific x402 payment transaction failed — particularly when you have structured failure facts such as error codes, network, amount, and integration step available. It is purpose-built for x402 protocol debugging, unlike generic blockchain transaction status lookups or human-readable reports.
Side effects
- Invalid input schema — missing required failure_facts fields returns a 400 error
- Payment required (402) if x402 micropayment of 0.01 USDC not provided
- Unknown or unrecognized error codes may result in low-confidence or unclassified output
- Mismatched schema version (x402_version out of range 1-2) returns validation error
- Empty or null failure_facts object yields no meaningful classification
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| failure_facts | object | |
| caller_context | object | |
| expected_facts | object |
Output
Schema · Response
{
"type": "json"
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"