API console

Open the console to run real Strata queries without installing a client. Sign in through Account, then choose Console in the navigation. Your browser session authorizes requests; the console does not create, expose or save an API key.

1. Choose an example and edit its JSON. Raw and sealed identification, raw pricing, slab identification, graded pricing and registry reads use the same handlers as the public API.
2. Click Run request. Inspect HTTP status, response JSON, request ID and account usage. An HTTP 200 can still contain an ambiguous match, missing price or partial provider error; inspect each result.
3. Copy returned product IDs into the pricing example. For graded markets, copy the slab’s identityRef into ref. A registry product requires a Strata UUID, not a numeric TCGplayer ID. Missing prices are never zero.
4. Click Retry last request to resend the exact last payload and idempotency key, even if you have since edited the composer. Monthly billing deduplicates it; beta attempt quotas do not. Each Run request starts a new operation.
5. Expand the cURL example to run the public endpoint with your own STRATA_API_KEY. The console itself checks your browser session; use cURL to verify bearer-key authentication separately.

Request history is kept only in the current tab and disappears on reload. Response headers expose a request ID for support. Usage differences are account snapshots, not a per-request invoice: concurrent activity and rolling-window expiry can affect them. Quota embedded in a replay is historical. Refresh usage for the current balance.

Sandbox billing before launch

Approved testers can use their existing Strata sign-in at the production console. Choose Test billing · sandbox credits in Environment. No separate Vercel login or sandbox account is needed. This option is restricted to an explicit tester allowlist because real provider lookups incur costs even when Stripe payments are simulated. Other customers keep the regular production console.

The banner must say Test billing · sandbox. Your account identity is shared, but test subscriptions, credits, usage and Stripe customers are separate. Switching environments clears tab history and retry state; test requests never fall back to production. Public API cURL examples are hidden in Test billing mode to prevent accidental production calls.

• Expand Test a subscription, choose Test Pro or Test Scale, and complete hosted Stripe Checkout with 4242 4242 4242 4242, a future expiry and any three-digit CVC. Never use real card details in test mode.
• Checkout returns directly to the console in Test billing mode. Refresh usage; Pro should show a 10,000-credit allowance, Scale 50,000, after the payment webhook arrives.
• Run a confident identification, then retry. On the monthly sandbox the first successful identity costs one credit and the identical retry adds none. Pricing costs an additional credit only when usable. Try Test a validation error; it should return HTTP 400 with no credit change.
• Open the test billing portal to verify invoice visibility, payment-method changes and period-end cancellation. Refresh account state after returning.

This verifies the customer journey. Webhook replay, refunds, disputes, renewal failures, reconciliation and database isolation also require operator integration checks; a successful console lookup alone does not certify payments for launch.

Production mode respects production quotas and billing flags. Test billing does not enable live payments, spend production credits or alter production subscriptions. Credentials for the protected sandbox stay server-side. No payment provider secrets are sent to the browser.