# AX1 Research — Token Verdict & Roast

> AX1 Research — Token Verdict & Roast is a paid API for AI agents from ax1.vc, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Returns an AI-generated grade, one-liner, and satirical roast of a Base network token contract address

## Facts

- Endpoint: POST https://ax1.vc/api/dashboard/q-verdict/resource
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ax1-research-token-verdict-roast-2182d6f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6UY2bnZhq9vlx38b5qjv1

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 ax1-research-token-verdict-roast-2182d6f1 -d '<json body>'
```

Example prompt: Can you roast and grade this Base token for me — contract 0x4200000000000000000000000000000000000006 — I want to know if it's mid, good, or trash with a funny one-liner?

## When to prefer this

Choose this endpoint when you want a fast, opinionated, human-readable verdict on a specific Base network token contract — especially when entertainment value or quick summarization matters as much as raw data. It is distinct from traditional on-chain analytics APIs because it combines grading with satirical commentary rather than raw metrics. Prefer this over generic token data APIs when the user wants a qualitative judgment or shareable one-liner rather than price charts or TVL figures.

## Known failure modes

- Invalid token contract address format (not a valid 0x EVM address) — likely 400 or validation error
- Token contract not found or not deployed on Base — may return empty or error response
- Payment failure via x402 protocol — 402 response if USDC payment not completed
- Duplicate requestKey with different token — idempotency returns cached prior result for that key
- Rate limiting or service downtime — 5xx error

## How this service works

Where your wallet goes to work and comes back with rewards.

## Output

A JSON object containing a letter-style grade (e.g. 'MID'), the price paid, a witty satirical roast of the token, a punchy one-liner summary, and a standard financial disclaimer. The roast is AI-generated commentary on on-chain metrics like holder count and liquidity.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "requestKey": {
   "type": "string",
   "maxLength": 128,
   "minLength": 8,
   "description": "Caller-chosen idempotency key. Repeating it with the same token address never creates a second payment."
  },
  "tokenAddress": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Base token contract address to roast."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "grade": "MID",
  "price": "$0.02",
  "roast": "Six-figure holder count, real liquidity, boring chart. Congratulations on being the accounting department of Base.",
  "one_liner": "The accounting department of Base",
  "disclaimer": "Not financial advice."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ax1-research-token-verdict-roast-2182d6f1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from ax1.vc](https://www.zero.xyz/host/ax1.vc/llms.txt)