Secret Generator: POST /api/secret
Generate cryptographic secrets with CSPRNG randomness and honest entropy accounting: random bytes (hex/base64/base64url), passwords with character-class guarantees, pronounceable strings, UUIDs, prefixed API keys, TOTP seeds (base32), and asymmetric keypairs (Ed25519, ECDSA P-256, RSA-2048) as PEM + JWK. Unbiased rejection sampling. Secrets are never stored or logged. POST a JSON body like: {"type":"password","length":24,"symbols":true,"count":2}
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://keyronne.com/api/secret", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"count",
"length",
"symbols",
"type"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://keyronne.com/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
EVIDENCE
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call.