blockchainmoneymap

Fast wallet triage for AI agents, including visible balance, token/NFT exposure, recent activity, confidence context, and recommended next action.

Screen up to 10 public EVM wallets in one paid call and return ordered triage snapshots with escalation candidates.

Low-cost transaction receipt, status, confirmation, fee, method, and finality context for a public EVM transaction hash.

Wallet audit API for AI agents. Investigate a public EVM wallet with recent flows, counterparties, token and NFT exposure, failed transaction count, conservative attention signals, confidence context, and optional saved report URL.

Generate a richer Blockchain Money Map report using the existing report-generation and saved-report logic.

Transaction decode API for AI agents. Decode a public EVM transaction hash into plain-English transaction context using status, value, gas, method, contract interaction, and token-transfer fields.

Generate a Blockchain Money Map report and return an unlisted saved-report URL.

Pre-payment public-chain and caller-context checks for an agent before it pays an x402 resource.

Public seller and payment-receiver signals for an x402 service URL and payee address.

Heuristic authenticity signals based on public payment graph observations and caller-provided context.

Receipt-level comparison between a public transaction hash and caller-provided payment expectations.

Public wallet profile signals that help agents reason about payment delegation and visible activity.

Public-chain evidence that compares a transaction hash against a caller-declared payment mandate.

Diagnose malformed or failed agent requests and return safe fix steps plus corrected request templates without executing the failed request.

Detect recursive agent-commerce loops, repeated purchases, delegation depth breaches, fan-out amplification, and bounded projected spend before an autonomous purchase proceeds.

Run deterministic or seeded simulations of paid multi-agent plans without calling submitted providers.

Detect elevated control-bypass risk from fragmented, delegated, wallet-hopped, near-threshold, burst, repeated, or concentrated autonomous spend.

Issue or verify a canonical human mandate checksum and deterministic action constraints, including signature trust-policy checks.

Validate revocation authority separately from x402 payment and prepare bounded propagation to opted-in verified targets.

Detect caller-supplied micropurchase fragmentation before an autonomous purchase proceeds.

Scan supplied recommendation, seller, and relationship evidence for conflict-of-interest review signals.

Estimate comparative evidence value from caller-supplied decision states without causal claims.

Query or append signed evidence-backed agent limitation records with correction and dispute handling.

Evaluate signed agent-version continuity before reputation transfer.

Check timestamp, finality, block, validity-window, and causal-order compatibility.

Select the least-cost verification provider set that satisfies coverage, confidence, independence, and budget policy.

Identify supplied continuity-risk signals without identity, fraud, or wrongdoing claims.

Measure verified dependency concentration and observed-but-undeclared common-mode dependencies.

Plan and authorize migration from one opted-in service to one opted-in target, with outbound disabled by default.

Checks caller-supplied x402 and agent discovery documents for path, price, currency, network, and routing consistency.

Summarizes recent BMM x402 payment-log activity for a payee, chain, currency, and optional paid resource path.

Compares caller-supplied x402 catalog, OpenAPI, MCP/tool metadata, and unpaid challenge samples for endpoint, method, price, currency, network, receiver, and tool drift.

Lints caller-submitted agent API, MCP, and x402 response samples for machine-actionable contract completeness without making network calls.

Classifies sanitized x402 failure facts into safe diagnostic causes without replaying payments or storing raw logs.

Creates or verifies hash-only caller-submitted x402 response provenance records with scoped idempotency and one-time lookup secrets.

Records and verifies hash-only evidence for authorized x402 payee-wallet rotations.

Tracks hash-only completeness snapshots for paid-agent response contracts across releases.

Records and compares hash-only x402, OpenAPI, and MCP operation stability facts.

Audits sanitized AP2-style mandate facts for missing autonomous-purchase constraints.

Compares sanitized autonomous-task facts against wallet policy coverage.

Reconciles sanitized autonomous-purchase intent facts against receipt facts.

Creates and verifies hash-only latency SLA evidence for paid agent tools.

Normalizes safe x402 challenge metadata from multiple provider formats.

Compares caller-supplied x402 facilitator cost facts for buyer-agent routing.

Classifies sanitized agent spend facts into operational categories.

Normalizes safe agent-commerce profile facts across x402, MCP, and AP2-style surfaces.

Audits sanitized MCP paid-tool permission scope declarations.

Checks x402 offer metadata for replay-hygiene controls.

Normalizes sanitized agent-commerce error facts into a stable taxonomy.

Checks x402 price display units for decimal, atomic-unit, currency, and network consistency.

Scores caller-supplied x402 facilitator facts for production readiness.

Plans safer x402 network, token, amount-format, and transfer-method routing from caller facts.

Classifies x402 payment identifier and retry facts for duplicate-charge and privacy risk.

Scores signed offer and receipt metadata for paid-service delivery confidence.

Advises whether an x402 route should use dollar-string pricing or explicit TokenAmount facts.

Explains buyer-agent approval friction for EIP-3009, Permit2, and unsupported transfer methods.

Builds an advisory failover ladder for caller-supplied x402 facilitator and network options.

Maps paid MCP tool surfaces against x402 routes and possible unpaid aliases.

Grades paid MCP tool names, descriptions, schemas, and output labels for buyer-agent clarity.

Classifies one-shot MCP paid-tool metadata changes for buyer-agent compatibility risk.

Simulates sanitized buyer-agent payment workloads against wallet spend-policy facts.

Checks whether a bounded spend permission fits a caller-supplied paid-agent workload.

Turns sanitized failed-payment facts into a conservative buyer-agent recovery playbook.

Compares mandate, signed offer, and receipt facts for agent-commerce evidence fit.

Orders caller-supplied paid agent tools into a clear, trust-preserving upsell path.

Checks caller-supplied HTTP 402 cache and paid-route facts for leakage risk.

Simulates caller-supplied agent checkout state facts for readiness gaps.

Compares agent-commerce quote, checkout, final payment, and order totals for unexplained deltas.

Compares seller checkout facts with caller-supplied agent-rendered buyer views.

Audits paid MCP/tool confirmation prompts for clear buyer spend consent.

Classifies timeout, cancellation, partial result, retry, and charge-policy facts for paid work boundaries.

Checks agent-commerce terms, license, refund, support, and usage-policy URI metadata.

Maps caller-supplied agent-commerce role facts into payment, fulfillment, support, and refund boundaries.

Checks sanitized order, webhook, shipment, delivery, return, refund, and adjustment facts for continuity.

Checks MCP server release metadata for registry and paid-tool readiness.

Creates safe fixture scenario recommendations for agent-commerce payment and checkout tests.

Maps payment rails, handlers, tokens, networks, wallet requirements, and buyer disclosures.

Classifies commerce schema fields for buyer-data minimization risk.

Audits sanitized MCP elicitation prompts and consent facts for scope and record gaps.

Maps aggregate high-volume low-value machine-payment facts for treasury dust and reconciliation risk.

Buyer agents cannot quickly tell whether a public Agent Card has enough identity, skill, interface, security, signature, and documentation evidence before delegation.

Buyer agents need to choose the right remote skill without executing tasks or trusting vague service descriptions.

Buyer agents see multiple similar services but lack one normalized board for price visibility, proof, limitations, and fit.

Buyer agents often see a price and promise but no useful preview that proves what the paid result will contain.

Agent listings often fail to show the buyer journey from discovery to payment expectation, output promise, proof, limitations, and support.

Agent-to-agent task handoffs can fail because payload shape, mode support, status handling, auth disclosure, or failure behavior is unclear.

Public agent listings make capability and trust claims that are hard for buyer agents to connect to actual evidence.

Buyer agents can land on public docs but fail to find service purpose, examples, price, limitations, and support path.

MCP servers can expose sampling behavior that is hard for buyers to understand before connecting or paying.

MCP resource lists can mix public docs, schemas, logs, user data, and restricted-looking resources without clear buyer labels.

Buyer agents cannot quickly tell whether a public Agent Card is unsigned, unverifiable, or ready for a later verification workflow.

Buyer agents can see a price but not whether the public proof is proportional to the value being promised.

Buyer agents and marketplaces cannot quickly tell whether public release notes matter to their workflows.

Workflow builders can see multiple public agents but cannot quickly map which one should lead, specialize, validate, or be excluded.

Public discovery snippets often fail to state who the agent serves, what it does, what it costs, what proof it returns, and what it does not do.

Agent-commerce participants need to explain where money went, what it bought, and which evidence links are missing.

Autonomous spend attempts need a black-box timeline that shows where the flow was safe, uncertain, failed, or completed.

Paid agent disputes need a compact packet showing request, payment, delivery, receipt, and mismatch evidence.

Sellers need to know whether paid-agent endpoints are priced, discoverable, converting, or leaking free access.

Human-not-present purchases need constraint simulation before an autonomous buyer attempts payment.

Agents need a structured deal room before delegating paid work to another agent.

Buyer agents need one portable object to decide whether a paid service is understandable, evidenced, and worth using.

Buyers need confidence that wallet, agent card, domain label, MCP server, seller profile, and x402 receiver belong together.

Agents need a simple route-weather signal before deciding whether now is safe to pay or retry.

MCP/App SDK builders need to know whether tool schemas, action descriptions, privacy metadata, auth notes, and UI hints are ready for review.

Sellers need to know which endpoints should become paid agent products before spending engineering time.

Agent/tool listings often fail to convert buyer agents because price, proof, limits, and value are unclear.

As agent payments scale, operators need to spot unusual payment graph patterns without making fraud accusations.

Operators buying many small paid agent services need to know which calls produced useful value.

BMM needs a showable buyer journey that packages flagship agents into a clear demo story with proof and next steps.

Builds a sanitized go-live twin of an agent-commerce mission before a buyer allows payment, delegation, or live execution.