Free · private by design

Make the constraint actionable.

Deterministic tools powered by the same sourced observations as the reference pages. No account, upload, or server-side input storage.

Choose the tool by the failing constraint

Use the context calculator when the combined prompt, history, retrieval, tools, and expected output may exceed a model budget. Use the upload checker when bytes, encoding, extracted tokens, or an intermediate gateway may reject a file. Use the rate calculator for sustained requests and token throughput, and the timeout checker for work that could outlive a function, workflow, client, or gateway deadline.

The error decoder is the starting point when you already have a stable status code or identifier. It maps reviewed messages to diagnostic pages without sending the pasted text to an external model. Redact secrets and customer data before using any diagnostic workflow.

From estimate to production decision

  1. Start with representative measured inputs rather than a best-case example.
  2. Read the result together with its assumptions and every linked first-party source.
  3. Confirm the exact account, plan, model, runtime, region, endpoint, and response headers in the live environment.
  4. Keep operational headroom and test failure behavior at, below, and above the expected boundary.
Transparent inputs

The assumptions are part of the answer.

Every tool displays its scope, source, and verification date. Results are planning aids—not a substitute for checking the active plan, account, region, model, or response headers.