JWT verify (HMAC)
POST /api/jwt-verifyVerify an HS256/384/512 JWT signature against a secret and check expiry. Send POST /api/jwt-verify with the required fields token and secret and pay $0.001 per call over x402 or MPP, or call it free by solving a proof-of-work challenge. It returns a JSON object with valid, algorithm, expired and payload.
Returns valid + decoded payload. (HMAC algorithms only.)
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
token | string | yes | Also accepted as jwt, accessToken. |
secret | string | yes | Also accepted as key, password, passphrase. |
Example request
curl -i -X POST https://agent402.tools/api/jwt-verify \
-H "Content-Type: application/json" \
-d '{"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJhZ2VudDQwMiIsIm5hbWUiOiJkZW1vIGFnZW50IiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjk5OTk5OTk5OTl9.NqggPBGuLX1OA7YuSlQ4S0INJfCOWnwXWT0XUIUrt3s","secret":"my-secret"}'
Without payment this returns HTTP 402 Payment Required with the exact price for jwt-verify; any x402 v2 or MPP client pays it and retries.
Example response
{
"valid": true,
"algorithm": "HS256",
"expired": false,
"payload": {
"sub": "agent402"
}
}
| Field | Type | Always present | In the example |
|---|---|---|---|
valid | boolean | yes | true |
algorithm | string | yes | HS256 |
expired | boolean | yes | false |
payload | object | yes | 1 field: sub |
From an MCP client
catalog.call {
"slug": "jwt-verify",
"params": {
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJhZ2VudDQwMiIsIm5hbWUiOiJkZW1vIGFnZW50IiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjk5OTk5OTk5OTl9.NqggPBGuLX1OA7YuSlQ4S0INJfCOWnwXWT0XUIUrt3s",
"secret": "my-secret"
}
}
On the hosted connector at https://agent402.tools/mcp, catalog.call runs jwt-verify free (rate-limited, no wallet). Local install: npx -y agent402-mcp.
Errors and behavior
tokenandsecretare required. An input the tool rejects returns an HTTP 4xx whose body carrieserror,tool,expected,requiredandexample, so the caller can correct it.- A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
- Free tier: no outbound network call leaves the server for this tool, so proof-of-work (16 leading zero bits of sha256) pays for it.
- A
GETorHEADto /api/jwt-verify returns the same 402 quote, so the price can be read without a body. - An
Idempotency-Keyheader makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).
Paid call (JavaScript agent)
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/jwt-verify", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJhZ2VudDQwMiIsIm5hbWUiOiJkZW1vIGFnZW50IiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjk5OTk5OTk5OTl9.NqggPBGuLX1OA7YuSlQ4S0INJfCOWnwXWT0XUIUrt3s",
"secret": "my-secret"
}),
});
No wallet? Pay with compute
Fetch a challenge, solve the sha256 puzzle (16 leading zero bits, a fraction of a second of CPU), and resend with the X-Pow-Solution header:
import { createHash } from "node:crypto";
const lz = (b) => { let t = 0; for (const x of b) { if (!x) { t += 8; continue; } t += Math.clz32(x) - 24; break; } return t; };
const c = await (await fetch("https://agent402.tools/api/pow/challenge?slug=jwt-verify")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/jwt-verify", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"token":"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJhZ2VudDQwMiIsIm5hbWUiOiJkZW1vIGFnZW50IiwiaWF0IjoxNzAwMDAwMDAwLCJleHAiOjk5OTk5OTk5OTl9.NqggPBGuLX1OA7YuSlQ4S0INJfCOWnwXWT0XUIUrt3s","secret":"my-secret"}) });
Part of these workflows
JWT verify (HMAC) is one step in this skill pack, each sold as a single call:
- JWT toolkit - Decode and verify a JWT in one pass - see the payload and check the signature.
Related tools
JWT sign
POST /api/jwt-signMint a signed JSON Web Token (HMAC: HS256 default, HS384, HS512) from a payload + secret. Pairs with jwt-decode/jwt-veri…
JWT decode
POST /api/jwt-decodeDecode a JWT without verification: header (algorithm), payload claims (subject, issuer, expiration), expiry status, and …
HMAC
POST /api/hmacHMAC signature of a message with a shared key. Algorithms: sha256 (default), sha512, sha1. Returns hex and base64.
Base32
POST /api/base32Base32 (RFC 4648) encode or decode text. mode: encode (default) or decode.
Base58
POST /api/base58Base58 encode or decode text (Bitcoin/IPFS alphabet). mode: encode (default) or decode.
Base64
POST /api/base64Base64 encode or decode text. mode: encode (default) or decode. Handles URL-safe base64 on decode.