# SperaxOS Contract ABI Fetcher

> SperaxOS Contract ABI Fetcher is a paid API for AI agents from chat.sperax.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-03).

Retrieves the ABI (Application Binary Interface) for any EVM smart contract on supported chains, payable via x402 micropayment

## Facts

- Endpoint: POST https://chat.sperax.io/api/x402/tools/contract-explorer/getContractABI?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/speraxos-contract-abi-fetcher-625eb148
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BvGyMgpHqR_ofsIpez3s1

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability speraxos-contract-abi-fetcher-625eb148 -d '<json body>'
```

Example prompt: Can you fetch the ABI for the smart contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum so I can see what functions and events it exposes?

## When to prefer this

Use this endpoint when you need to programmatically interact with a smart contract and require its ABI without manually searching block explorers like Etherscan. Ideal for AI agents building DeFi integrations, decoding transaction data, or inspecting contract interfaces on the fly — especially when no API key is available and pay-per-use micropayments via x402 are preferred.

## Known failure modes

- Unverified or unverifiable contract — ABI not available if contract source was not published/verified on the block explorer
- Invalid address format — returns error if address is not a valid 0x EVM address
- Unsupported chain — returns error if chain name is outside the supported set (ethereum, arbitrum, polygon, base, optimism, avalanche, bsc)
- Payment failure — x402 payment rejected or insufficient USDC balance
- Proxy contract — may return proxy ABI rather than implementation ABI
- Contract not found — address has no deployed contract on specified chain

## How this service works

AI-powered DeFi intelligence APIs payable via the x402 HTTP payment protocol. No API key required — pay per request with USDC on Base. Identity-only (SIWX) endpoints are free for wallets with an agentcash identity.

## Output

Returns the full ABI JSON array for the specified smart contract, including all function signatures (name, inputs, outputs, state mutability), event definitions, and error types — enabling programmatic interaction with the contract.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string",
   "description": "Chain name: ethereum, arbitrum, polygon, base, optimism, avalanche, bsc. Defaults to ethereum."
  },
  "address": {
   "type": "string",
   "description": "EVM contract address (0x…)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/speraxos-contract-abi-fetcher-625eb148/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chat.sperax.io](https://www.zero.xyz/host/chat.sperax.io/llms.txt)