# x402-tools JWT Decode

> x402-tools JWT Decode is a paid API for AI agents from x402.nichospt.net, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-11).

Decodes and inspects a JWT token (header, payload, signature) without verifying its signature, returning structured JSON components.

## Facts

- Endpoint: POST https://x402.nichospt.net/jwt-decode?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-tools-jwt-decode-2cda9497
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2l9ds7Mxo63lgOtKRxvdR

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 x402-tools-jwt-decode-2cda9497 -d '<json body>'
```

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

## When to prefer this

Use this endpoint when you need to quickly inspect or debug the contents of a JWT token and do not need cryptographic signature verification. Ideal for extracting claims, reading expiration metadata, or identifying the algorithm used, without needing access to the signing secret or public key.

## Known failure modes

- Malformed JWT string (not three dot-separated base64 segments) returns an error
- Empty or missing token field returns a validation error
- Token with non-standard encoding may fail to parse correctly
- Network or service downtime returns a 5xx error

## How this service works

Pay-per-call utility APIs for AI agents, settled in USDC via the x402 protocol.

## Output

Returns a JSON object with the decoded JWT header (e.g. algorithm, type), payload (e.g. sub, name, custom claims), raw signature string, and an expiration status field indicating if the token is expired. A 'verified' field is always false since signature verification is not performed.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token": {
   "type": "string",
   "description": "A JWT (header.payload.signature). NOT verified."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "header": {
   "alg": "HS256",
   "typ": "JWT"
  },
  "expired": null,
  "payload": {
   "sub": "1234",
   "name": "Ada"
  },
  "verified": false,
  "signature": "SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-tools-jwt-decode-2cda9497/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.nichospt.net](https://www.zero.xyz/host/x402.nichospt.net/llms.txt)