# JWT Decoder with Timing Analysis

> JWT Decoder with Timing Analysis is a paid API for AI agents from toolbelt402.tpoborne.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Decodes a JWT into its header and payload components, and performs timing analysis including issued-at, not-before, and expiry as ISO timestamps, expired flag, and seconds until expiry — without verifying the signature.

## Facts

- Endpoint: POST https://toolbelt402.tpoborne.workers.dev/jwt/decode
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jwt-decoder-with-timing-analysis-6adfeb2b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YuaDgUfHxQGKWpPV56usa

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-decoder-with-timing-analysis-6adfeb2b -d '<json body>'
```

Example prompt: Can you decode this JWT for me and tell me what's in the payload, when it was issued, and whether it's already expired? Here's the token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c

## When to prefer this

Choose this endpoint when you need to quickly inspect the contents of a JWT token — its claims, algorithm, and timing metadata — without performing cryptographic signature verification. Ideal for debugging, monitoring token lifetimes, logging, or extracting user/session claims in a trusted internal pipeline where signature validation has already been handled upstream.

## Known failure modes

- Malformed or non-JWT string returns a parse error
- Token with no exp claim will have null/absent expiry and seconds-until-expiry fields
- Very old or already-expired tokens decode successfully but return expired: true and negative seconds-until-expiry
- Base64 padding errors in the token string may cause decode failure

## How this service works

Decode a JWT — header, payload, and timing analysis (issued/not-before/expiry as ISO timestamps, expired flag, seconds until expiry). Decode only; signature is NOT verified.

## Output

Returns the decoded JWT header object (e.g. algorithm, token type), the decoded payload object with all claims, and timing analysis including issued-at (iat), not-before (nbf), and expiration (exp) as human-readable ISO 8601 timestamps, a boolean expired flag, and the number of seconds remaining until expiry (negative if already expired). Signature is NOT verified.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token": {
   "type": "string",
   "description": "JWS compact JWT (max 16 KB). Decode only — signature is NOT verified."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jwt-decoder-with-timing-analysis-6adfeb2b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from toolbelt402.tpoborne.workers.dev](https://www.zero.xyz/host/toolbelt402.tpoborne.workers.dev/llms.txt)