Going live

Use this checklist before you switch from a test key to a live key. Live analyses use real credits and return real results.

Before you switch

Access and credits

• Your organization has credits. Call GET /v1/credits with the live key and check that available is above zero. See Credits.
• The live key is stored in your server configuration, not in code or browser bundles. See Authentication.
• You monitor available and expiringSoon. There is no low-balance alert yet.

Submitting

• You send an Idempotency-Key and keep it while you retry. See Idempotency.
• You send a real northAngle if you know it, and you chose a reviewMode on purpose. See Review flows.
• You handle 402, 429 and 503 by waiting and retrying, and you handle 422 image_unreadable by asking for another image. See Errors.

Results and notifications

• Your webhook endpoint uses HTTPS, verifies the signature, ignores duplicate event IDs, and ignores unknown event types. See Webhooks.
• Your code handles every final status: completed, failed and expired. See Analyses.
• Your code answers review_required analyses, or you only use modes that cannot pause.
• You log the requestId of failed calls so we can help quickly.

What differs from the sandbox

• Results are real and different for each floor plan.
• Each analysis uses one credit while it runs. The credit is returned if it fails or expires.
• Analyses can end as failed and review steps can expire after about 7 days.
• Processing is not instant. No response-time guarantee is published yet, so wait for webhooks or poll patiently.
• Reports can be requested in Hindi or Arabic; translation finishes after the English report.

Try one live analysis first

Submit one real floor plan with the live key, check the credit balance before and after, and confirm your webhook receives the analysis.completed event with livemode: true.