# NexusAPI Crypto Contract Verifier

> NexusAPI Crypto Contract Verifier is a paid API for AI agents from nexus-api-peach-nine.vercel.app, paid per call via x402, $0.109163/call, status unknown (last checked 2026-09-13).

Verifies and validates smart contract code or address authenticity on a blockchain network

## Facts

- Endpoint: POST https://nexus-api-peach-nine.vercel.app/api/crypto/contract/verify
- Price: $0.109163/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nexusapi-crypto-contract-verifier-abe77e0f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LpZuoZfLtHov1aeirHcC_

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 nexusapi-crypto-contract-verifier-abe77e0f -d '<json body>'
```

Example prompt: Can you verify whether the smart contract at address 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 is legitimate and validated on-chain?

## When to prefer this

Use this endpoint when an AI agent needs to confirm whether a smart contract address is verified and legitimate before executing transactions, integrating a DeFi protocol, or advising a user on contract safety. Prefer this over general blockchain explorers when a pay-per-call, no-API-key approach is needed.

## Known failure modes

- Invalid or malformed contract address returns error
- Contract not found on specified network
- Blockchain network unavailable or rate-limited
- Query string missing or empty returns 400-level error
- Unverified contract returns negative/null verification result

## How this service works

Crypto, AI, Social Media, Finance, Weather, Tools &amp; more. Pay per call in USDC on Base. No API keys.

## Output

Returns verification status of the smart contract, including whether the contract source code has been verified, contract metadata, and authenticity signals derived from on-chain data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": "Search query or input parameter"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nexusapi-crypto-contract-verifier-abe77e0f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from nexus-api-peach-nine.vercel.app](https://www.zero.xyz/host/nexus-api-peach-nine.vercel.app/llms.txt)
