HMAC
POST /api/hmacHMAC signature of a message with a shared key. Send POST /api/hmac with the required fields text and key 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 algo, hex and base64.
Algorithms: sha256 (default), sha512, sha1. Returns hex and base64.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
text | string | yes | Message to sign (max 100KB) Also accepted as content, str, string, input, body, data. |
key | string | yes | Shared secret key |
algo | string | no | sha256 | sha512 | sha1 |
Example request
curl -i -X POST https://agent402.tools/api/hmac \
-H "Content-Type: application/json" \
-d '{"text":"payload","key":"secret","algo":"sha256"}'
Without payment this returns HTTP 402 Payment Required with the exact price for hmac; any x402 v2 or MPP client pays it and retries.
Example response
{
"algo": "sha256",
"hex": "f7bc…",
"base64": "97w…"
}
| Field | Type | Always present | In the example |
|---|---|---|---|
algo | string | yes | sha256 |
hex | string | yes | f7bc… |
base64 | string | yes | 97w… |
From an MCP client
catalog.call {
"slug": "hmac",
"params": {
"text": "payload",
"key": "secret",
"algo": "sha256"
}
}
On the hosted connector at https://agent402.tools/mcp, catalog.call runs hmac free (rate-limited, no wallet). Local install: npx -y agent402-mcp.
Errors and behavior
textandkeyare 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/hmac 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/hmac", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"text": "payload",
"key": "secret",
"algo": "sha256"
}),
});
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=hmac")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/hmac", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"text":"payload","key":"secret","algo":"sha256"}) });
Related tools
Webhook signature verify
POST /api/webhook-verifyVerify a webhook's HMAC signature against the correct per-provider scheme: GitHub (X-Hub-Signature-256, sha256=hex), Str…
Base58
POST /api/base58Base58 encode or decode text (Bitcoin/IPFS alphabet). mode: encode (default) or decode.
Hash
POST /api/hashCryptographic hash of a text string (UTF-8): returns algo, hex and base64 digests. Algorithms: sha256 (default), sha512,…
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 verify (HMAC)
POST /api/jwt-verifyVerify an HS256/384/512 JWT signature against a secret and check expiry. Returns valid + decoded payload. (HMAC algorith…
Function selector / event topic lookup
POST /api/selector-lookupResolve a 4-byte function selector or a 32-byte event topic hash to its known human-readable Solidity signatures, via th…