# PrimeAPI JWT Decode

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

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

## Facts

- Endpoint: POST https://prime-api-seven.vercel.app/api/tools/jwt/decode
- Price: $0.160058/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/primeapi-jwt-decode-bce04d35
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fVrU-6B2CPSqXor9BrkOL

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

Example prompt: Can you decode this JWT for me and show me the payload claims, especially the expiration and subject fields? Here's the token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyMTIzIiwiZXhwIjoxNzAwMDAwMDAwfQ.signature

## When to prefer this

Use this endpoint when you need to quickly inspect the contents of a JWT without setting up a local library or when operating in an agent workflow that needs to read token claims (e.g., checking expiry, extracting user identity) as a standalone paid microservice call via x402/USDC on Base.

## Known failure modes

- Invalid or malformed JWT string returns a parse error
- Empty query input returns a 400-level error
- Token with non-standard encoding may fail to decode correctly
- Network or server error returns a 5xx response
- Payment failure (insufficient USDC balance) returns a 402 error before processing

## 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 constituent parts: the header (algorithm, token type), the payload (all claims such as sub, iss, iat, exp, and any custom fields), and the raw signature. The payload claims are returned as a readable JSON object.

## 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/primeapi-jwt-decode-bce04d35/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prime-api-seven.vercel.app](https://www.zero.xyz/host/prime-api-seven.vercel.app/llms.txt)