mercator-address-evidenceBefore you send a transaction, check that the chain and contract address you are about to use is the one the entity actually publishes. Not a scam or rug assessment — provenance. You supply the entity, the chain and the candidate address; the answer is whether the entity's own source and an independent chain source support that exact claim, with the URL, the verbatim excerpt and a transact true/false. Disagreeing sources return no address at all. Paid per call over x402 on Base ($0.25 USDC), with a free preflight. You pay from your own wallet — see "Who pays" below. Triggers: "is this the official contract for X", "verify this address before I trade", "did X publish this address", "which chain is this contract on and who says it's theirs".
Install via ClawdBot CLI:
clawdbot install arzuo/mercator-address-evidenceGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://mercator-entity-evidence.fly.devAudited Oct 9, 2026 · audit v1.0
Generated Oct 9, 2026
An autonomous DeFi agent extracts a contract address from a Telegram signal, a Discord message, or a scraped docs page and is about to swap funds into it. Before signing, it calls MERCATOR with the entity domain, chain, and candidate address to confirm the entity itself publishes that exact address on that chain. Only a transact:true lets the trade proceed.
A DAO operations lead is configuring a new treasury, bridge, or staking position and needs to verify that a multisig or staking contract address claimed by a contributor is genuinely published by the protocol. The skill returns the entity's own source plus an independent chain explorer source, both quoting the chain and address, so the DAO doesn't fund a copycat contract.
A custodial platform or wallet provider needs to confirm that a token contract or bridge address a customer is about to interact with is the official one published by the issuer. The platform runs the free preflight to describe what will be checked, then the paid route for the binding answer before enabling the transaction in the UI.
An x402-enabled agent receives a payment request referencing a contract address and must decide whether to pay. It uses MERCATOR to confirm provenance of the address in the request, paying $0.25 USDC on Base via its own x402 signer per check. Disagreeing sources return no address at all, so the agent refuses to transact.
A security analyst receives a report that a project published a new contract address for a bridge or token migration. Before deeper and more expensive forensics, the analyst runs every claim through MERCATOR to filter out unverifiable or contradictory addresses from further review.
The skill exposes a paid HTTP endpoint at $0.25 USDC on Base per evidence lookup, settled via the x402 exact scheme from the caller's own wallet. A free preflight route describes what will be checked without charging, while the paid route returns the full PASS/FAIL result with evidence, URLs, and an excerpt.
Platforms and agent frameworks embed the evidence check directly into their transaction-signing flow, so every outbound transaction is gated by a provenance lookup. The platform's managed wallet signs the x402 payment, making the skill a per-transaction toll collected invisibly on behalf of end users.
Exchanges, custodians, and trading desks that verify many addresses daily could consume the endpoint under a prepaid or subscription arrangement rather than retail per-call pricing, with the same per-request x402 mechanics but negotiated rates. The free preflight and stale-defect disclosure support trust-building for these larger buyers.
💬 Integration Tip
Set the X_PAYMENT header with a pre-signed x402 payment from your own signer and fall back to the free /validate preflight when no signer is configured; always supply the candidate address, since omitting it returns transact:false with candidate_address_required rather than guessing the target.
Scored Oct 9, 2026
Access CoinMarketCap data via x402 pay-per-request protocol with USDC payments on Base. Use when users mention x402, want CMC data without API keys, ask abou...
Purchasing, payments and saved details through Aftercard
Plisio integration. Manage Invoices, Payouts, Wallets, Transactions, Users. Use when the user wants to interact with Plisio data.
Send and receive money via Venmo using Strider Labs MCP connector. Pay friends, request payments, split bills, check balances. Complete autonomous P2P paymen...
Send and receive money via PayPal using Strider Labs MCP connector. Send payments, request money, check balance, view transactions. Complete autonomous onlin...
Molt Motion Pictures platform skill. Create AI-generated Limited Series content, manage studios, submit scripts for agent voting, and earn 1% of tips. Wallet-based auth, x402 payments.