Password strength
POST /api/password-strengthScore a password's strength: character-set size, entropy bits, a 0–4 rating, and an estimated offline crack time. Send POST /api/password-strength with the required field password 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 entropyBits, score, rating and crackTime.
The password is never stored or logged.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
password | string | yes |
Example request
curl -i -X POST https://agent402.tools/api/password-strength \
-H "Content-Type: application/json" \
-d '{"password":"Tr0ub4dour&3"}'
Without payment this returns HTTP 402 Payment Required with the exact price for password-strength; any x402 v2 or MPP client pays it and retries.
Example response
{
"entropyBits": 72,
"score": 3,
"rating": "strong",
"crackTime": "centuries"
}
| Field | Type | Always present | In the example |
|---|---|---|---|
entropyBits | number | yes | 72 |
score | number | yes | 3 |
rating | string | yes | strong |
crackTime | string | yes | centuries |
From an MCP client
catalog.call {
"slug": "password-strength",
"params": {
"password": "Tr0ub4dour&3"
}
}
On the hosted connector at https://agent402.tools/mcp, catalog.call runs password-strength free (rate-limited, no wallet). Local install: npx -y agent402-mcp.
Errors and behavior
passwordis 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/password-strength 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/password-strength", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"password": "Tr0ub4dour&3"
}),
});
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=password-strength")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/password-strength", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"password":"Tr0ub4dour&3"}) });
Part of these workflows
Password strength is one step in this skill pack, each sold as a single call:
- User onboarding - Take a signup form submission and run the full onboarding workup deterministically: validate the email, score the chosen password, mint a stable internal ID, derive a URL-safe handle from the display name, generate a recovery / API secret, hash the password for storage, and verify the 2FA setup code. One pass, every step a pure-CPU call.
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…
Password generator
GET /api/passwordGenerate cryptographically random passwords. ?length=8..128 (default 24), ?symbols=true|false (default true), ?count=1..…
Card number validate
POST /api/card-validateValidate a payment card number (Luhn checksum) and detect the brand. Numbers are not stored or logged.
Color convert
POST /api/colorConvert a color between hex, RGB, and HSL. Accepts "#1a2b3c", "rgb(26,43,60)", or "hsl(210,40%,17%)".
CSV lint
POST /api/csv-lintValidate CSV structure: consistent column counts across rows, properly closed quotes, delimiter detection. Returns row/c…
Email validate
POST /api/email-validateValidate an email address: syntax check plus live MX record lookup on the domain (deliverability signal, not a guarantee…