# OmniAPI Crypto Contract Read

> OmniAPI Crypto Contract Read is a paid API for AI agents from omni-api-cyan.vercel.app, paid per call via x402, $0.039079/call, status unknown (last checked 2026-09-15).

Reads data from a smart contract on one of 9+ supported blockchains via a pay-per-call USDC API

## Facts

- Endpoint: POST https://omni-api-cyan.vercel.app/api/crypto/contract/read
- Price: $0.039079/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/omniapi-crypto-contract-read-a19be601
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_E1hLJJKrf-8y9GKL_iIxq

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 omniapi-crypto-contract-read-a19be601 -d '<json body>'
```

Example prompt: Can you read the current token balance stored in the USDC contract at address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum — specifically call the balanceOf function for wallet 0x742d35Cc6634C0532925a3b844Bc454e4438f44e?

## When to prefer this

Choose this endpoint when you need to perform a read-only (view/pure) call to a smart contract across any of 9+ supported chains and want to pay per call in USDC via the x402 protocol without managing your own RPC node or blockchain infrastructure. It is especially useful for agents that need ad-hoc contract reads across multiple chains without setting up chain-specific SDKs.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty result
- Unsupported chain causes a routing failure
- Malformed query string or incorrect ABI function name returns a parse error
- Payment failure via x402 (insufficient USDC) blocks the request
- Contract function requires arguments not provided, resulting in a revert or bad data
- Rate limiting or Vercel cold-start latency may cause timeouts

## How this service works

444 endpoints across 9+ chains. Crypto, AI, Social, Finance, Weather, Tools. Pay per call in USDC via x402 with 4 facilitators: Dexter, Meridian, FluxA, GoPlausible.

## Output

Returns the result of a smart contract read call — typically the decoded return value(s) of the specified contract function, such as a balance, address, boolean flag, or other on-chain state variable, wrapped in a JSON response object.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "Input data for the endpoint"
  },
  "query": {
   "type": "string",
   "description": "Search query or input text"
  },
  "params": {
   "type": "object",
   "description": "Additional parameters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "API response data"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/omniapi-crypto-contract-read-a19be601/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from omni-api-cyan.vercel.app](https://www.zero.xyz/host/omni-api-cyan.vercel.app/llms.txt)