# Aether Base Contract Onchain Data Lookup

> Aether Base Contract Onchain Data Lookup is a paid API for AI agents from aether-x402.vercel.app, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-12).

Fetches onchain metadata and risk signals for a contract address on Base, including proxy details, code size, ERC standards, and x402 payability audit results.

## Facts

- Endpoint: POST https://aether-x402.vercel.app/v1/base/contract?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aether-base-contract-onchain-data-lookup-8890db38
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gUVz-exHQTQIyeitomNc7

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 aether-base-contract-onchain-data-lookup-8890db38 -d '<json body>'
```

Example prompt: Can you look up the contract at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base and tell me whether it's a proxy, what ERC standards it implements, and whether it looks risky to interact with?

## When to prefer this

Choose this endpoint when you need onchain ground-truth data about a specific Base network contract address — especially for token risk assessment, proxy detection, ERC standard identification, or verifying x402 payability. It is purpose-built for Base and pays per call via USDC over x402, making it suitable for agent-native workflows without API key management.

## Known failure modes

- Invalid address format (not a valid 0x hex address) returns validation error
- Address is an EOA (not a contract) — isContract returns false with no further data
- Contract not deployed on Base network — returns empty or error response
- Network or RPC issues causing timeouts
- Payment failure via x402 if USDC balance is insufficient

## How this service works

Pay-per-call Base onchain data, token risk verdicts and x402 payability audits over x402 (USDC on Base).

## Output

A JSON object containing: proxy details (implementation address if applicable), codeBytes (size of contract bytecode), standards array (e.g. ['erc20']), and isContract boolean. May also include token risk verdict and x402 payability audit flags depending on the endpoint variant.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "proxy": {
   "implementation": "0x..."
  },
  "codeBytes": 1234,
  "standards": [
   "erc20"
  ],
  "isContract": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aether-base-contract-onchain-data-lookup-8890db38/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aether-x402.vercel.app](https://www.zero.xyz/host/aether-x402.vercel.app/llms.txt)