x402basequality 0.85

Human-readable transaction interpretation, metadata, and balance changes for any onchain transaction.

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://public.zapper.xyz/x402/transaction-details

What it does

The Zapper Transaction Details endpoint returns a human-readable interpretation of a specific blockchain transaction, including metadata about the involved parties, the dApp used, balance changes (deltas), and a processed natural-language description. You provide a transaction hash and chain ID, and receive structured data covering from/to addresses, timestamps, app attribution, and a polymorphic list of display items (tokens, NFTs, actors) involved in the transaction.

This endpoint is part of the broader Zapper API suite, which covers onchain data across 60+ chains including token prices, NFTs, portfolios, and transaction history. The transaction-details tool is specifically useful for agents or applications that need to explain what happened in a transaction without parsing raw calldata or event logs. Payment is handled via the x402 protocol on Base using USDC at a fixed price of $0.001125 per call (1125 base units of USDC with 6 decimals). The endpoint accepts POST requests with a JSON body containing `hash` (the 0x transaction hash) and `chainId` (the numeric chain ID where the transaction occurred).

The response includes a `transactionDetailsV2` object with nested `transaction` (hash, timestamp, fromUser, toUser), `app` (displayName, imgUrl), `interpretation` (processedDescription, descriptionDisplayItems), and `deltas` (balance changes). This makes it straightforward for AI agents to summarize or display transaction activity in user-facing contexts.

Capabilities

transaction-interpretationbalance-delta-trackingdapp-attributionmulti-chain-supporthuman-readable-descriptionsx402-paymentper-call-pricing

Use cases

  • —AI agent explaining a user's recent transaction in plain language
  • —Wallet app displaying a human-readable transaction summary
  • —Analytics dashboard attributing transactions to specific dApps
  • —Chatbot answering 'what did this transaction do?' queries
  • —Audit tool reviewing balance changes from a specific tx hash

Fit

Best for

  • —Agents that need to explain blockchain transactions to end users
  • —Applications requiring structured transaction metadata across 60+ chains
  • —Developers building transaction explorers with dApp attribution

Not for

  • —Submitting or signing new transactions (read-only endpoint)
  • —Bulk historical transaction scanning (use transaction-history endpoint instead)
  • —Non-EVM chains or networks not supported by Zapper

Quick start

curl -X POST https://public.zapper.xyz/x402/transaction-details \
  -H "Content-Type: application/json" \
  -H "X-Payment: <x402-payment-token>" \
  -d '{"hash": "0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060", "chainId": 1}'

Example

Request

{
  "hash": "0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060",
  "chainId": 1
}

Response

{
  "data": {
    "transactionDetailsV2": {
      "app": null,
      "deltas": {},
      "transaction": {
        "hash": "0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060",
        "toUser": {
          "address": "0x5df9b87991262f6ba471f09758cde1c0fc1de734"
        },
        "fromUser": {
          "address": "0xa1e4380a3b1f749673e270229993ee55f35663b4"
        },
        "timestamp": "2015-08-07T03:30:33Z"
      },
      "interpretation": {
        "processedDescription": "Sent 0.1 ETH",
        "descriptionDisplayItems": []
      }
    }
  }
}

Endpoint

URLhttps://public.zapper.xyz/x402/transaction-details
Transporthttp
Protocolx402
Pay to0x43a2a720cd0911690c248075f4a29a5e7716f758
CurrencyUSD COIN

Quality

0.85/ 1.00

Full OpenAPI schema with input/output descriptions, live 402 challenge confirmed, clear pricing ($0.001125/call in USDC on Base), and example request body provided. Response schema is documented as type outlines rather than full concrete examples, and no separate docs page was found (404), which slightly limits completeness.

Warnings

  • —The legacy Zapper API at /api shows a deprecation notice pointing to build.zapper.xyz; the x402 endpoints appear to be the current offering.
  • —No dedicated documentation page was found at /docs or /pricing (both return 404); schema information comes entirely from the OpenAPI spec and x402 challenge.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:10:24Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/qTfd9M