JSON Sorter
Sort JSON object keys alphabetically at every level, or sort arrays by a field.
Generate prefixed API keys in the format modern providers use.
The API Key Generator produces keys in the shape modern providers use: a prefix naming the service and environment, a cryptographically random body, and an optional checksum so a malformed key can be rejected without a lookup.
Modern API keys are not just random strings. They carry a prefix identifying the service and the environment — sk_live_, pk_test_, ghp_ — because that is what lets a secret scanner recognise a leaked key in a public repository and revoke it before it is used.
This generates keys in that shape: a prefix you choose, a separator, and a cryptographically random body of the length you set. There is an optional CRC32 checksum suffix, the trick GitHub uses so a key can be validated as well-formed without a database lookup. The entropy of the random part is reported, because that is the only part that provides security — the prefix is metadata, and public.
A recognisable prefix is what lets a secret scanner spot a leaked key in a public repository and alert you within minutes.
A CRC32 suffix, the trick GitHub uses, so a typo can be caught locally and scanners get far fewer false positives.
The prefix is public metadata, so the strength figure counts only the random part — which is the honest number.
Common shapes such as sk_live and pk_test are one click away, so a new scheme starts from a proven convention.
The page says to store a hash rather than the key, and to show the key exactly once.
Something like sk_live or pk_test, identifying the service and environment.
The entropy figure updates so you can see what you are getting.
Optional, and lets a key be checked for typos without a lookup.
Store only a hash of the key on your server, never the key itself.
So it can be recognised. Secret scanners in GitHub and elsewhere match known prefixes and can alert the provider when a key leaks, which is how a committed key gets revoked within minutes rather than months.
Hashed, exactly like passwords — SHA-256 is fine, since the key already has full entropy and does not need stretching. Show the key once at creation and never again.
At least 128 bits of entropy in the random part. Over a 62-character alphabet that is 22 characters; 32 is a common choice and leaves plenty of margin.
It lets you reject a mistyped or truncated key immediately, without a database lookup, and it lets scanners identify keys with far fewer false positives. It adds no security on its own.
What people who use the API Key Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the API Key Generator. It takes half a minute and no account.
Write the first reviewSort JSON object keys alphabetically at every level, or sort arrays by a field.
Find what runs on a port, with a note on whether it should be exposed.
Turn text into a block-letter ASCII banner for a README or a CLI.
Convert JSON into a PHP array literal or a typed class you can paste into a project.
Break a user agent string into browser, engine, operating system and device.
See a float’s sign, exponent, mantissa and its exact decimal value.
Turn an SVG into a React component with the attributes React expects.
Convert YAML config into JSON and see exactly how each value was typed.