# DESK LEAD x402 – Pons Token Filter

> DESK LEAD x402 – Pons Token Filter is a paid API for AI agents from desk-x402.desk-x402-gh.workers.dev, paid per call via x402, $1/call, status unknown (last checked 2026-09-15).

Returns a risk verdict (e.g. WATCH, SAFE, DANGER) for a given token address or a recent-scan stub, paid via x402 micropayment

## Facts

- Endpoint: GET https://desk-x402.desk-x402-gh.workers.dev/pons/filter
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/desk-lead-x402-pons-token-filter-48d6e779
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uX0124bdNAvIFFJm4H3wI

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 desk-lead-x402-pons-token-filter-48d6e779
```

Example prompt: Can you check if the token at address 0x1234abcd... on Base is safe to interact with — I want to know its Pons filter verdict before I do anything with it.

## When to prefer this

Use this endpoint when you need a fast, on-demand risk verdict for a specific token address on the Base blockchain and are willing to pay $1 USDC per call via x402 micropayment. Prefer it over manual on-chain analysis when you need a structured WATCH/SAFE/DANGER classification without building your own heuristics. It is especially suited for agent workflows that gate trading or interaction decisions on a token risk score.

## Known failure modes

- Missing or invalid token address returns a stub/fallback mode rather than an error
- Payment not provided or invalid x402 payment header results in 402 Payment Required
- Unsupported network (non-Base eip155:8453 for v2) may cause payment rejection
- Malformed query parameters return a 400-level error
- Token not indexed or unknown may return a generic or inconclusive verdict

## How this service works

Micropay research APIs (x402 v2 + bazaar). Free catalog at /.well-known/x402.json. Primary v2 accepts: Base eip155:8453 only. Legacy X-PAYMENT-TX still supports bsc|base via acceptsV1. Headers: X-PAYMENT-TX, X-PAYMENT-NETWORK, PAYMENT-SIGNATURE. No financial advice.

## Output

A JSON object with an 'ok' boolean, a 'mode' string (e.g. 'token'), a 'report' object containing a 'verdict' field (e.g. WATCH, SAFE, DANGER), and a 'product' label ('pons_filter'). When no token is supplied, returns a recent-scan stub instead.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "token": {
       "type": "string",
       "description": "Optional Pons token address; omit for recent-scan stub"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "mode": "token",
  "report": {
   "verdict": "WATCH"
  },
  "product": "pons_filter"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/desk-lead-x402-pons-token-filter-48d6e779/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from desk-x402.desk-x402-gh.workers.dev](https://www.zero.xyz/host/desk-x402.desk-x402-gh.workers.dev/llms.txt)