X402 agent commerce digital twin x402 REST usage
Builds a sanitized go-live twin of an agent-commerce mission before a buyer allows payment, delegation, or live execution.
api.blockchainmoneymap.com · 105 listed services · provider site
Builds a sanitized go-live twin of an agent-commerce mission before a buyer allows payment, delegation, or live execution.
Scan supplied recommendation, seller, and relationship evidence for conflict-of-interest review signals.
Query or append signed evidence-backed agent limitation records with correction and dispute handling.
Check timestamp, finality, block, validity-window, and causal-order compatibility.
Plan and authorize migration from one opted-in service to one opted-in target, with outbound disabled by default.
Buyers need confidence that wallet, agent card, domain label, MCP server, seller profile, and x402 receiver belong together.
Checks MCP server release metadata for registry and paid-tool readiness.
Detect elevated control-bypass risk from fragmented, delegated, wallet-hopped, near-threshold, burst, repeated, or concentrated autonomous spend.
Creates or verifies hash-only caller-submitted x402 response provenance records with scoped idempotency and one-time lookup secrets.
Compares sanitized autonomous-task facts against wallet policy coverage.
Audits sanitized AP2-style mandate facts for missing autonomous-purchase constraints.
Issue or verify a canonical human mandate checksum and deterministic action constraints, including signature trust-policy checks.
Turns sanitized failed-payment facts into a conservative buyer-agent recovery playbook.
Checks whether a bounded spend permission fits a caller-supplied paid-agent workload.
Simulates sanitized buyer-agent payment workloads against wallet spend-policy facts.
Classifies one-shot MCP paid-tool metadata changes for buyer-agent compatibility risk.
Grades paid MCP tool names, descriptions, schemas, and output labels for buyer-agent clarity.
Maps paid MCP tool surfaces against x402 routes and possible unpaid aliases.
Builds an advisory failover ladder for caller-supplied x402 facilitator and network options.
Explains buyer-agent approval friction for EIP-3009, Permit2, and unsupported transfer methods.
Advises whether an x402 route should use dollar-string pricing or explicit TokenAmount facts.
Scores signed offer and receipt metadata for paid-service delivery confidence.
Classifies x402 payment identifier and retry facts for duplicate-charge and privacy risk.
Plans safer x402 network, token, amount-format, and transfer-method routing from caller facts.
Scores caller-supplied x402 facilitator facts for production readiness.
Checks x402 price display units for decimal, atomic-unit, currency, and network consistency.
Normalizes sanitized agent-commerce error facts into a stable taxonomy.
Audits sanitized MCP paid-tool permission scope declarations.
Normalizes safe agent-commerce profile facts across x402, MCP, and AP2-style surfaces.
Classifies sanitized agent spend facts into operational categories.
Provider identity is derived from the domain or repository in the source record. If two vendors share a host, they appear together here — that is a limitation of the data, not a statement about ownership.