# JWT Decode

> JWT Decode is a paid API for AI agents from apex-api-gamma.vercel.app, paid per call via x402, $0.160058/call, status unknown (last checked 2026-09-15).

Decodes a JSON Web Token (JWT) to reveal its header, payload, and signature components without verification

## Facts

- Endpoint: POST https://apex-api-gamma.vercel.app/api/tools/jwt/decode
- Price: $0.160058/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jwt-decode-bd281363
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IH54SX7dQui4oS68GOUys

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 jwt-decode-bd281363 -d '<json body>'
```

Example prompt: Can you decode this JWT for me and show me what's in the payload and header: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

## When to prefer this

Use this endpoint when you need to quickly inspect the contents of a JWT token — such as reading expiration time, subject, issuer, or custom claims — without needing to verify its signature. Ideal for debugging, logging, or displaying token metadata in a UI. Not suitable when cryptographic signature verification is required.

## Known failure modes

- Malformed JWT string that cannot be base64-decoded returns an error
- Input token missing required dot-separated segments fails parsing
- Empty or null query input returns a validation error
- Token with non-standard encoding may fail to parse correctly

## How this service works

Crypto, AI, Social Media, Finance, Weather, Tools &amp; more. Pay per call in USDC on Base. No API keys.

## Output

Returns the decoded JWT broken into its three parts: the header (algorithm and token type), the payload (claims such as sub, iat, exp, name, roles, and other custom claims), and optionally the signature component — all in plain JSON without cryptographic verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": "Search query or input parameter"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "API response data"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jwt-decode-bd281363/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apex-api-gamma.vercel.app](https://www.zero.xyz/host/apex-api-gamma.vercel.app/llms.txt)