Cheapest GSTIN API: How to Verify the Claim

Search for the cheapest GSTIN API and every result claims the title. None of them show their working, because the claim is almost never comparable: one quotes a per-call rate that excludes filing history, one quotes a monthly plan, one quotes a rate that only exists above a volume you will never hit, and one quotes a price that expires with your credits. This post gives you the arithmetic that collapses all four into a single number you can rank on — and then runs our own pricing through it, so you can check us the same way you check everyone else.

Why "cheapest" is usually an empty claim

Four things make published GST API prices non-comparable, and vendors rarely reconcile them for you.

Different units. One provider prices per API call, another per GSTIN per month, another per "record". If a provider bills per call and needs two calls — one for the registration record, one for the return-filing history — its true unit price is double the number on the page.

Different scope. A response containing legal name and status answers "does this exist". A response containing status dates, jurisdiction, places of business, e-invoicing enablement and per-period GSTR filing with ARNs answers "should I pay this supplier". Those are not the same product and should not be compared on price alone. The field-by-field breakdown is in the GST verification API guide.

Different commitment. A ₹0.25 rate that requires a ₹1,20,000 annual minimum costs ₹1,20,000 if you make 100,000 calls and ₹1,20,000 if you make 900. Divide by your real volume, not theirs.

Different expiry. Credits that expire convert unused balance into revenue. A pack priced at ₹0.30 with a 90-day expiry, bought by a team that uses 60% of it, effectively cost ₹0.50.

The formula that settles it

One number ranks every vendor honestly. Compute it for each candidate with your volume:

The numerator is what leaves your bank account over a year. The denominator is decisions, not HTTP requests. That distinction is the whole game: a vendor charging ₹0.30 for a response you need to supplement with a second ₹0.30 call is charging ₹0.60, and a vendor charging ₹0.40 for a complete record is the cheaper one.

Normalising four pricing models onto one number

Almost every provider uses one of four shapes. Here is how to convert each into the formula above.

Run the numbers yourself on the GST API cost calculator, or read the longer treatment of each model in GST API pricing explained and the side-by-side method in our GST API price comparison.

What counts as a billable call

This is where two APIs at an identical headline rate diverge by 20–40% in practice. Ask each vendor, explicitly, which of these draws from your balance:

• A GSTIN that fails format or check-digit validation before any upstream lookup happens.
• A well-formed GSTIN that is simply not registered — a legitimate answer, not an error.
• A 429 rate-limit rejection.
• A 5xx caused by the upstream government source being unavailable.
• A repeat query for a GSTIN you already looked up an hour ago.

On our API, a GSTIN that fails format or check-digit validation never reaches upstream and never costs a credit, and an upstream failure returning 502 is not billed either — an outage on our side is not your expense. Validating locally first is free anywhere, and it is the single cheapest optimisation available: see GSTIN format explained and the free GSTIN validator.

Our numbers, run through the same formula

We build one of these APIs, so treat this section as a disclosed interest and verify it rather than trusting it.

• Rate. ₹0.50 per verification pay-as-you-go. ₹0.40 per verification once a single purchase crosses 2,500 credits.
• Commitment. None. No subscription, no monthly minimum, no annual contract, no notice period, no sales call to get a key.
• Scope per call. One GET /api/get-taxpayer-info/{gstin} returns legal and trade name, status and status dates, constitution and taxpayer type, centre and state jurisdiction, principal and additional places of business, e-invoicing enablement, and per-period GSTR filing history with ARNs. Filing history is not a separate SKU, so the denominator in the formula does not get halved.
• Non-billable calls. Format and check-digit failures cost nothing; upstream 502s cost nothing.
• Free tier. 20 credits on email verification, expiring 30 days after issue, plus five public lookups a day on the search tool with no account at all.
• Where it is not cheapest. If your annual volume is genuinely in the millions, a negotiated enterprise contract elsewhere may beat ₹0.40 on unit price. At that volume, ask us for a volume rate before assuming it.

At 10,000 verifications a year that is ₹4,000 — one bulk purchase, no plan, no expiry surprise. At 1,000 it is ₹500. The worked examples across volumes are in what 1,000 GSTIN verifications really cost.

The nine questions to send every vendor

Paste these into one email, send it to every shortlisted provider including us, and rank the replies. The vendors who answer all nine in writing are usually the ones worth buying from.

1. What is your per-verification price at my forecast annual volume, in writing?
2. Is return-filing history included in that call, or billed separately?
3. Do credits expire? After how long?
4. Is there a minimum purchase, monthly floor, or annual commitment?
5. Which failure responses are billable — 4xx, 429, 5xx, unregistered GSTIN?
6. How long do you cache a taxpayer record, and what invalidates it?
7. What is the documented per-key rate limit, and how is a 429 signalled?
8. Can I test against real GSTINs today without talking to sales?
9. What does it cost to leave — notice period, data export, unused balance?

Question 6 is the one that stops a cheap API from being a false economy; the reasoning is in how to choose a GST verification API provider. Questions 4 and 9 are covered in GST API without a subscription, and the traps behind question 5 are catalogued in hidden costs of a cheap GST API.

Frequently asked questions