# B20 Policy Admin Reader

> B20 Policy Admin Reader is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.04/call, status unknown (last checked 2026-09-14).

Reads the policy administrator and pending admin for each active transfer/mint policy of a B20 token from the Policy Registry.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/b20-policy-admin
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/b20-policy-admin-reader-375ae8c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rmVIOXzfPy79bkhtlA_oA

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 b20-policy-admin-reader-375ae8c8
```

Example prompt: Who is the policy admin for this B20 token at address 0xAbCd1234...? I want to know if there's a pending admin handover too.

## When to prefer this

Use this endpoint when you need to determine who administers the compliance and transfer-restriction policies for a B20 token — specifically to identify policyAdmin and pendingPolicyAdmin from the Policy Registry. Prefer this over b20-control (which reads the token's own roles) when you need the full picture of who can freeze or seize tokens via the policy layer.

## Known failure modes

- Invalid or non-B20 token address returns an error or empty result
- Token address not found in the Policy Registry
- Network/RPC error when reading from Base chain
- Missing required 'address' query parameter returns a 400-level error
- Non-checksummed address format may cause lookup failure

## How this service works

🆕 b20-control reads the token's own roles; the address that can actually add you to a blocklist lives in the Policy Registry. This reads WHO administers each active transfer/mint policy (policyAdmin), and whether that control is being handed over (pendingPolicyAdmin) or renounced. The other half of 'who can freeze/seize you', straight from the registry.

## Output

Returns the current policyAdmin address and pendingPolicyAdmin address (if any) for each active transfer and mint policy registered for the given B20 token, revealing who holds control over freeze/seize/blocklist capabilities.

## 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"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "address": {
       "type": "string",
       "description": "B20 token address"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/b20-policy-admin-reader-375ae8c8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)