# Automaton Colony · Contract Code Status

> Automaton Colony · Contract Code Status is a paid API for AI agents from automatoncolony.xyz, paid per call via x402, $0.0099/call, status unknown (last checked 2026-09-13).

Retrieves the verified contract code status for a given Base mainnet address, including the block it was read at and its hash, valid for 600 seconds.

## Facts

- Endpoint: POST https://automatoncolony.xyz/api/v1/x402/datos/codigo-verificado
- Price: $0.0099/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/automaton-colony-contract-code-status-38ba1893
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8q0MHvXdVeYJ6CPrtEnGW

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 automaton-colony-contract-code-status-38ba1893 -d '<json body>'
```

Example prompt: Can you check the verified code status of the contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Base mainnet and tell me the block it was read at?

## When to prefer this

Use this endpoint when you need a fast, synchronous answer about whether a specific Base mainnet contract has verified source code, including anchoring metadata (block number and hash) for auditability. Prefer it over full audit endpoints when you only need code verification status, not a complete security screening. Its 600-second validity window makes it suitable for time-sensitive automated pipelines.

## Known failure modes

- Invalid address format (not a valid 0x EVM address) returns a validation error
- Address is an EOA (externally owned account) rather than a contract — may return empty or unverified status
- Contract not deployed on Base mainnet returns not-found or empty code status
- Payment not processed correctly via x402 results in 402 response before data is returned
- Stale result if called again after the 600-second validity window without re-querying

## How this service works

Is the source of this Base contract verified? Returns the verification status and the runtime code hash. Send the Base contract address as targetAddress; without one, it answers for USDC. Answered inline, no polling, with the Base block and hash it was read at. Valid 600s. Payment implies a request for immediate execution. Terms (0x3545cfb9d504c284cb1d528bfb0bebc142afdfc1c92a62967ae83ccc0b3e3c0d): https://automatoncolony.xyz/api/v1/legal/terms

## Output

Returns the verified contract code status for the given Base mainnet address, along with the Base block number at which the data was read and its block hash. The result is valid for 600 seconds from the time of observation, allowing downstream systems to re-verify against the chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "targetAddress": {
   "type": "string",
   "default": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Contract or token address to read, on Base mainnet (eip155:8453). Defaults to USDC when omitted."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/automaton-colony-contract-code-status-38ba1893/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from automatoncolony.xyz](https://www.zero.xyz/host/automatoncolony.xyz/llms.txt)