# 100BTC Token Permission Checker (Base Chain)

> 100BTC Token Permission Checker (Base Chain) is a paid API for AI agents from vps-fc89c157-1.taila28d02.ts.net:10000, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Checks ERC-20 token allowance approval status and risk level for one or more owner/token/spender pairs on Base (chain ID 8453)

## Facts

- Endpoint: POST https://vps-fc89c157-1.taila28d02.ts.net:10000/api/permissions?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/100btc-token-permission-checker-base-chain-18eeb76a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZJB5lfL33KSr230NvOfs5

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 100btc-token-permission-checker-base-chain-18eeb76a -d '<json body>'
```

Example prompt: Check the token approval status and risk level for wallet 0xAbC...123 on Base — specifically whether the spender 0xDEF...456 has permission to move token 0x789...ABC.

## When to prefer this

Use this endpoint when you need a read-only, risk-assessed lookup of ERC-20 token approvals on Base chain, especially when checking multiple token/spender pairs in a single call. Prefer it over generic RPC calls when you want structured risk ratings alongside raw approval status, or when operating in a pay-per-call agent context where auditability matters.

## Known failure modes

- Invalid Ethereum address format (must match ^0x[a-fA-F0-9]{40}$) returns validation error
- chain_id must be exactly 8453 (Base); other chain IDs are rejected
- pairs array must have 1–25 items; empty or oversized arrays are rejected
- On-chain RPC errors or node unavailability may cause lookup failure
- Payment failure or insufficient USDC balance causes HTTP 402 and no result

## How this service works

Thirty x402 v2 pay-per-call APIs by 100BTC. Listing data is generated from each live HTTP 402 challenge and runtime Bazaar schema.

## Output

Returns a list of results for each token/spender pair, each containing an approval status (e.g. NONE, APPROVED) and a risk rating (e.g. LOW, MEDIUM, HIGH), along with the chain ID and a confirmation that the query was read-only.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "owner": {
   "type": "string",
   "pattern": "^0x[a-fA-F0-9]{40}$"
  },
  "pairs": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "token",
     "spender"
    ],
    "properties": {
     "token": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
     },
     "spender": {
      "type": "string",
      "pattern": "^0x[a-fA-F0-9]{40}$"
     }
    },
    "additionalProperties": false
   },
   "maxItems": 25,
   "minItems": 1
  },
  "chain_id": {
   "type": "integer",
   "const": 8453
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "scope": "only caller-supplied pairs",
  "results": [
   {
    "risk": "LOW",
    "status": "NONE"
   }
  ],
  "chain_id": 8453,
  "execution": "READ_ONLY"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/100btc-token-permission-checker-base-chain-18eeb76a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vps-fc89c157-1.taila28d02.ts.net:10000](https://www.zero.xyz/host/vps-fc89c157-1.taila28d02.ts.net%3A10000/llms.txt)
