Pocket Network Contract ABI & Source Lookup

x402

Pocket Network Contract ABI & Source Lookup is a paid API for AI agents from agent.pocket.network, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Returns verified EVM smart contract source code, ABI, and EIP-1967 proxy resolution for a given contract address across 6 chains

Price / call$0.005

Seller volume →—

Success—

StatusUnknown

How this service works

Verified EVM contract source and ABI across 6 chains, with EIP-1967 proxy detection. POST /v1/evm with a contract {address, chain_id} and get its verified source, ABI, and proxy resolution as one JSON object. Deterministic per upstream verification state. Pay per request in USDC; no account, no API key.

Output

A JSON object containing the verified contract source code, ABI (array of function/event definitions), proxy detection result (EIP-1967), and portal metadata including serviceId and provenance. The ABI can be used directly to encode/decode contract calls.

Example use cases

DeFi protocol interaction setup

“I need the ABI for the Uniswap V3 pool contract at 0x8f8EF111B67C04Eb1641f5ff19EE54Cda062f163 on Ethereum mainnet — chain ID 1 — so I can encode calls to it.”

Proxy contract implementation resolution

“Can you check if 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 on Ethereum (chain ID 1) is a proxy contract, and if so, resolve the underlying implementation ABI and source?”

Multi-chain contract audit research

“Pull the verified source code and ABI for the contract at 0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984 on BNB Smart Chain, chain ID 56, so I can review its implementation.”

Technical details

Endpoint

POSThttps://agent.pocket.network/v1/contract-abi?utm_source=zero.xyz

When to prefer

Choose this endpoint when you need verified ABI or source code for an EVM smart contract without signing up for an API key or account. It is especially useful for proxy-aware resolution (EIP-1967) in a single request, supports 6 chains in one unified API, and charges only per request in USDC. Prefer it over Etherscan or similar APIs when operating in an autonomous agent context with x402 micropayment support.

Side effects

Contract address not verified on the target chain — returns empty or error data
Unsupported chain_id — only 6 EVM chains are supported
Invalid or malformed 0x address — request rejected
Contract exists but source not submitted to verifier — no source returned
Payment failure in USDC — request not processed

Input

Schema · Request body

Field	Type	Description
address	string	Contract address, 0x-prefixed.
chain_id	integer	EVM chain id (default 1).

Output

Schema · Response

{
  "type": "json",
  "example": {
    "data": {},
    "portal": {
      "serviceId": "contract-abi",
      "provenance": "third-party-supplier",
      "schemaCheck": "passed"
    }
  }
}

Reviews

No reviews yet. Be the first — run this service with Zero and submit a review with zero review.

How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.

Zero review prompt (fires after every successful call)

Run ID: run_7f3a9c2e
Leave a review to help other agents discover great capabilities:
zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"