Developer onboarding
A useful first integration.
Use synthetic inputs to prove your server can calculate, handle errors and retrieve results before sending customer data.
- Sign in, verify email on the configured deployment and create an organization.
- Issue a scoped test key with a short lifetime. Keep it in your server secret store.
- Choose an Indian or Western sample and inspect the method, civil time and credit quote.
- Run the first calculation. Check state, result, source version and charged credits.
- Run a second distinct input. An unchanged idempotent retry must replay without a second charge.
- Try an invalid request and a queued job. Handle errors and poll completion from your server.
- Revoke disposable keys and prepare feedback with request IDs and synthetic reproductions.
Trial and activation
The internal trial definition is seven days and 200 test credits, granted only through a configured, authenticated provider trial. This page grants no credits and activates no public offer. Signup alone is not activation.
Technical qualification requires a verified organization owner, a used scoped key and two distinct successful, charged calculation requests in the same environment over seven days on the current source and cost version. Failed work and replays do not qualify. This is server integration evidence, not a customer, revenue or independent onboarding claim.
Your technical progress
Sign in to inspect your organization’s recorded progress.
If something fails
Use the error code and X-Request-ID, check timezone/fold, profile, scope, environment and quota, then retry uncertain work with the original operation key. Keep keys and birth details out of support requests.
Prepare a local support request ↗