On this page
Credit sources
| Source | Current behavior |
|---|---|
| Monthly free | 100 credits provisioned on the monthly cycle. |
| Social reward | 200 permanent credits for a successful eligible platform claim, once per claim. |
| Plan allocation | Monthly credits supplied by an active paid plan. |
| Purchased | One-time credits supplied by credit-pack purchases. |
Chargeable API operations consume credits through the backend credit service. An insufficient balance produces a 402 error.
Subscription plans
| Plan | Price | Monthly credits | Rate limit |
|---|---|---|---|
| Developer | ₹499/month | 5,000 | 60 req/min |
| Pro | ₹1,499/month | 25,000 | 180 req/min |
| Business | ₹4,999/month | 100,000 | 600 req/min |
The Developer Console does not hard-code plan prices into its card UI. It fetches the plan catalog from /v1/plans and renders each plan's current priceInr, credit allocation, rate limit, and description.
Single pricing source
Keep numeric API prices in the backend plan catalog rather than duplicating them in static docs. The checkout request also uses the selected backend plan ID, so the backend remains the authoritative product source.
Credit packs
| Pack | Credits | Price source |
|---|---|---|
| 1,000 credits | 1,000 | Loaded from the live /v1/plans response |
| 5,000 credits | 5,000 | Loaded from the live /v1/plans response |
| 25,000 credits | 25,000 | Loaded from the live /v1/plans response |
The Developer Console also loads credit-pack prices from the same /v1/plans response. Packs are available only while a paid API subscription is active.
Rate limits
The quota middleware tracks requests over a one-minute window. Redis is used for shared quota state when configured; without a global quota service, production requests are blocked unless local fallback is explicitly enabled.
| HTTP | Meaning |
|---|---|
| 429 | API rate limit exceeded. |
| 503 | Quota infrastructure unavailable for safe global enforcement. |