USDC pay-per-call API.
Simple to integrate.

How it works

Make a GET request. The first response returns HTTP 402 Payment Required and a PAYMENT-REQUIRED header with the exact amount, asset, Base network and receiver. An x402-compatible client signs a payment and retries with the PAYMENT-SIGNATURE header. The facilitator verifies and settles the payment; only then can the protected API return its result.

GET https://www.skavio.eu/x402/v1/usdc/verify?tx_hash=0x...&network=base
→ HTTP 402 · native USDC / eip155:8453 · 0.02 USDC
→ Client submits signed x402 payment
→ Paid GET response: JSON evidence

No wallet private keys are shared with Skavio. Do not send seed phrases. All data endpoints are read-only.

Verify a native USDC transaction

GET /x402/v1/usdc/verify

tx_hash=0x...  (EVM hash) or Solana base58 transaction signature
network=base | polygon | arbitrum | optimism | ethereum | avalanche | solana

Returns blockchain, native token address/mint, confirmation or finalization status, transfer owners, native USDC amounts and transaction timestamp. Pending / not fully confirmed transfers are never reported as finalized.

Match exact recipient and amount

GET /x402/v1/usdc/match

tx_hash=0x... (or Solana base58 signature)
network=polygon
recipient=0x... (for Solana: base58 owner wallet)
amount=12.500000

Returns matched: true only when exactly one finalized native USDC transfer matches the recipient and exact six-decimal amount. Duplicate matching transfers return false to avoid ambiguity.

Download transaction evidence PDF

GET /x402/v1/usdc/evidence.pdf

tx_hash=0x... (or Solana base58 signature)
network=ethereum

Returns a timestamped PDF document of public blockchain evidence. It is not a tax invoice, receipt for a commercial sale or a guarantee of third-party authorization.

Connect Skavio as a paid MCP server

Use our public Streamable HTTP endpoint in an MCP client: https://www.skavio.eu/mcp. Discovery of all tools and the free skavio_catalog tool require no payment. The server offers these paid tools:

verify_native_usdc(tx_hash, network="base")     0.02 USDC
match_native_usdc_payment(tx_hash, recipient, amount, network="base")   0.03 USDC
usdc_transfer_evidence_pdf(tx_hash, network="base")  0.05 USDC
domain_dns_tls_audit(domain)                   0.05 USDC

Payment protocol: x402 MCP transport v2. An unpaid tool call returns a machine-readable PaymentRequired result, including the native Circle USDC address on eip155:8453. An x402-capable agent prepares its own signed payment, retries with params._meta["x402/payment"], and the server independently verifies, executes and settles the transaction.

General MCP clients can browse the catalog. Paid execution requires an x402-aware MCP client capable of signing payments. The MCP server cannot access a buyer's wallet, and Skavio never requests private keys. A standard x402 HTTPS API is also available above.

Documentation for automated agents

Exact merchant prices are in the HTTP 402 payment challenge and never change according to the blockchain being inspected. Payment chain is eip155:8453, not the selected inspection network. Network data is sourced from independent public RPC providers and can be temporarily unavailable.