# SignalDesk AI JWT Decode

> SignalDesk AI JWT Decode is a paid API for AI agents from x402-agent.kariguetoazul.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-13).

Decodes a JWT token into its header, payload, and signature components without verifying the signature

## Facts

- Endpoint: POST https://x402-agent.kariguetoazul.workers.dev/api/encoding/jwt-decode?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/signaldesk-ai-jwt-decode-9a6b4078
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qOHBDr25PBn_KqiC-NkKw

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 signaldesk-ai-jwt-decode-9a6b4078 -d '<json body>'
```

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

## When to prefer this

Use this endpoint when you need to inspect or debug JWT token contents without performing signature verification — for example, reading expiry times, extracting claims for logging, auditing token structure, or understanding a third-party token format. Prefer this over a full JWT verification library when you explicitly do NOT need cryptographic validation and just want the decoded payload quickly. Not suitable when you need to authenticate a user or trust the claims for access control decisions.

## Known failure modes

- Malformed JWT string (not three base64url segments) returns a parse error
- Token exceeding 4096 characters may be rejected
- Network/worker timeout if the Cloudflare Worker is cold-starting
- Missing or empty 'token' field returns a validation error
- Non-JWT strings (e.g. opaque tokens) will fail to parse

## How this service works

Evidence-backed autonomous AI jobs and paid data tools. Queue/D1/cron run outside the chat; free quotas and bounded execution apply.

## Output

Returns a JSON object with three top-level keys: 'header' (containing alg, typ, and other header fields), 'payload' (containing all JWT claims such as sub, iat, exp, iss, aud, etc.), and 'signature_verified' (always false — this endpoint does not verify the signature). A 'warning' field is included reminding callers not to trust decoded claims for authentication purposes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "token": {
   "type": "string",
   "maxLength": 4096,
   "description": "JWT token. Avoid sharing confidential credentials."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "header": {
   "alg": "HS256",
   "typ": "JWT"
  },
  "payload": {
   "sub": "123"
  },
  "warning": "Decoded claims are untrusted; do not use this result for authentication.",
  "signature_verified": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/signaldesk-ai-jwt-decode-9a6b4078/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-agent.kariguetoazul.workers.dev](https://www.zero.xyz/host/x402-agent.kariguetoazul.workers.dev/llms.txt)