Sample input
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiZXhwIjoxNzAwMDAwMDAwfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
Decode JWT header and payload locally and show expiry information.
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiZXhwIjoxNzAwMDAwMDAwfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c
curl -X POST https://toolkit.fun/api/v1/t/jwt-decode \
-H "Authorization: Bearer tk_..." \
-H "Content-Type: application/json" \
-d '{"input":"...","params":{}}'
MCP server: https://toolkit.fun/api/mcp
Read the manifest first, then call the same run contract used by the web UI. The input, output, permissions, and receipt stay consistent across REST and MCP.
Manifest: https://toolkit.fun/api/v1/registry/tools/jwt-decode/manifest REST: POST https://toolkit.fun/api/v1/t/jwt-decode MCP: https://toolkit.fun/api/mcp
Use this tool directly when you need JWT Decoder, want to chain it into a workflow, or want to expose it to an agent over REST API or MCP. This page carries the sample, call syntax, manifest, and version so search engines and generative retrieval can describe the tool accurately.
Decode JWT header and payload locally and show expiry information.