# skills.onesource.io On-Chain Contract Details

> skills.onesource.io On-Chain Contract Details is a paid API for AI agents from skills.onesource.io, paid per call via x402, $0.005000/call, status unknown (last checked 2026-09-15).

Fetches on-chain smart contract metadata and details for a given contract address on supported EVM networks.

## Facts

- Endpoint: GET https://skills.onesource.io/api/chain/contract/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48
- Price: $0.005000/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/skills-onesource-io-09e4f88c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BhiO_5XuyeEthvXkb1t2j

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 skills-onesource-io-09e4f88c
```

Example prompt: Can you pull the on-chain contract details for 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 on Ethereum? I want to see what's deployed there.

## When to prefer this

Use this endpoint when you need to inspect or verify what smart contract is deployed at a specific EVM address on Ethereum, Base, Avalanche, Sepolia, MegaETH, or MegaETH-testnet. Prefer this over generic blockchain explorers when you need programmatic, structured on-chain contract data accessible via API with per-call micropayment pricing.

## Known failure modes

- Invalid address format (not a valid 0x-prefixed 40-hex-char address) returns a validation error
- Address is an EOA (externally owned account) with no contract code deployed
- Unsupported network name returns an enum validation error
- Contract not found on the specified network returns a not-found or empty response
- Payment failure (x402 payment not processed) blocks the request

## How this service works

Fetches on-chain contract details for a given contract address.

## Output

Returns on-chain details for the specified smart contract address, which may include contract bytecode, ABI, deployment metadata, contract type, and chain-specific information for the requested EVM network.

## Example request

```json
{
 "network": "ethereum"
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [],
 "properties": {
  "network": {
   "enum": [
    "ethereum",
    "sepolia",
    "avax",
    "megaeth",
    "megaeth-testnet",
    "base"
   ],
   "type": "string",
   "default": "ethereum",
   "description": "The EVM network to query. The contract address is passed as a URL path parameter, not in the body."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "data",
  "meta"
 ],
 "properties": {
  "data": {
   "type": "object",
   "required": [
    "address",
    "is_contract",
    "code_length",
    "name",
    "symbol",
    "is_erc721",
    "is_erc1155",
    "is_erc20",
    "is_erc165"
   ],
   "properties": {
    "name": {
     "type": "string"
    },
    "symbol": {
     "type": "string"
    },
    "address": {
     "type": "string"
    },
    "is_erc20": {
     "type": "boolean"
    },
    "is_erc165": {
     "type": "boolean"
    },
    "is_erc721": {
     "type": "boolean"
    },
    "is_erc1155": {
     "type": "boolean"
    },
    "code_length": {
     "type": "number"
    },
    "is_contract": {
     "type": "boolean"
    }
   }
  },
  "meta": {
   "type": "object",
   "required": [
    "endpoint",
    "request_id"
   ],
   "properties": {
    "endpoint": {
     "type": "string"
    },
    "request_id": {
     "type": "string"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/skills-onesource-io-09e4f88c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from skills.onesource.io](https://www.zero.xyz/host/skills.onesource.io/llms.txt)