Tools that actually run
Four of them. Each either talks to the live API or executes real cryptography in your browser — none of them are illustrations of what a tool would look like.
API playground
Send a real request to the live API with your own key and read the actual response. Relayed server-side so your key never enters page JavaScript.
Webhook signatures
Sign a payload exactly as the platform does, then verify one. Runs the same Web Crypto code the SDK ships — the fastest way to debug a handler that rejects everything.
Key inspector
Parse a key's format and mode entirely in your browser, and optionally call GET /me to report its live scopes and what they unlock.
Cost calculator
Estimate token counts and per-call cost across the Node model catalog, then scale it to a monthly volume before you commit to a design.
How your key is handled
Short version: it isn't kept
- The playground posts your key to this site's own route handler, which uses it for one request and discards it. It is never written to a database, a log line, or an analytics event.
- Only side-effect-free endpoints are allowed through, so a stray click cannot publish a listing or delete a webhook endpoint.
- The webhook and cost tools never make a network call at all — everything happens locally.
- Still: prefer a scoped
nd_test_key here. Not because we'd misuse a live one, but because that's the right habit everywhere.