# JWT Decode (manylives.me)

> JWT Decode (manylives.me) is a paid API for AI agents from manylives.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-12).

Decodes a JWT token without signature verification, returning the header (algorithm, key ID), payload claims, and timing fields (issued-at, not-before, expiry) with live expiry status.

## Facts

- Endpoint: POST https://manylives.me/paid/util/jwt-decode?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jwt-decode-manylives-me-073a1342
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wD7uDpD588RAjBymvqts0

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-manylives-me-073a1342 -d '<json body>'
```

Example prompt: Can you decode this JWT and tell me what claims it contains, what algorithm it uses, and whether it's expired: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJkZW1vIiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjE3MDAwMDM2MDB9.c2lnbmF0dXJl

## When to prefer this

Use this endpoint when you need to quickly inspect or debug a JWT — reading claims, checking expiry, or identifying the algorithm and key ID — without needing the signing secret or public key. Ideal for debugging, logging pipelines, or pre-processing tokens before forwarding them. Not suitable when you need cryptographic signature verification.

## Known failure modes

- Malformed JWT (not three base64url segments separated by dots) returns an error
- Empty or missing 'token' field returns a validation error
- Token with invalid base64url encoding in header or payload returns a parse error
- Extremely large tokens may be rejected

## How this service works

Decode a JWT without verifying it: header (algorithm, key id), payload claims, and issued, not-before and expiry times with whether it is expired now.

## Output

A JSON object with: header fields (alg, typ, kid if present), payload containing all claims (sub, iat, exp, nbf, and any custom claims), human-readable ISO timestamps for issued-at, not-before, and expiry, a boolean 'expired' field reflecting whether the token is expired right now, and a 'signature_verified: false' flag (since this endpoint decodes without verifying).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token": {
   "type": "string",
   "examples": [
    "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJkZW1vIiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjE3MDAwMDM2MDB9.c2lnbmF0dXJl"
   ],
   "description": "the JWT (required)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "header": {
   "alg": "HS256",
   "typ": "JWT"
  },
  "expired": false,
  "expires": "2026-10-08T06:47:44.000Z",
  "payload": {
   "exp": 1791442064,
   "sub": "…"
  },
  "signature_verified": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jwt-decode-manylives-me-073a1342/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from manylives.me](https://www.zero.xyz/host/manylives.me/llms.txt)
