# Base Contract Risk Verdict

> Base Contract Risk Verdict is a paid API for AI agents from api.jagent.dev, paid per call via x402, $0.0099/call, status unknown (last checked 2026-10-10).

Analyzes a Base mainnet smart contract address and returns a plain-English risk verdict including proxy type, token standards, and privileged function details.

## Facts

- Endpoint: POST https://api.jagent.dev/v1/contract-risk-verdict?utm_source=zero.xyz
- Price: $0.0099/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-contract-risk-verdict-6551d996
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_94juH8y22SyrNg7lFdM59

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 base-contract-risk-verdict-6551d996 -d '<json body>'
```

Example prompt: Before I interact with this contract at 0x4200000000000000000000000000000000000006 on Base, can you give me a plain English risk verdict — is it a proxy, what standards does it implement, and are there any privileged functions I should know about?

## When to prefer this

Choose this endpoint when you need a fast, plain-English security assessment of a specific Base mainnet smart contract before interacting, approving, or investing. It is purpose-built for Base (not generic EVM chains) and returns structured risk signals including proxy patterns and privileged functions — making it ideal for pre-transaction safety checks in DeFi, NFT, or wallet agent workflows where a human-readable verdict is needed alongside structured JSON data.

## Known failure modes

- Invalid or malformed address (not 0x + 40 hex) returns a validation error
- Contract address does not exist on Base mainnet returns not-found or empty analysis
- Request body exceeds 4 KB limit returns a payload-too-large error
- Contract bytecode is not verifiable or is an EOA returns limited or inconclusive results
- Response latency may reach up to 30 seconds for complex contracts
- Payment failure via x402 protocol prevents call from completing

## How this service works

Plain English risk verdict for a Base smart contract. JSON body: address (0x + 40 hex), one contract per call, body max 4 KB, 2 to 30 s. Returns JSON: proxy type, standards, privileged functions (min…

## Output

A JSON response containing the contract's proxy type (e.g. transparent, UUPS, or none), implemented token/interface standards (e.g. ERC-20, ERC-721), a list of privileged functions with their access control details, and an overall plain-English risk summary describing the contract's safety profile.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-contract-risk-verdict-6551d996/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jagent.dev](https://www.zero.xyz/host/api.jagent.dev/llms.txt)