Free GST Verification API: What's Actually Free?

There is no unlimited free GST verification API, and any service claiming otherwise is capping you somewhere you cannot see. What does exist, and is genuinely free: five GSTIN lookups a day through our GST number search tool with no signup, 20 free API credits when you create an account, the government's own Search Taxpayer page on gst.gov.in for manual checks, and offline format validation, which costs nothing and always will.

This page explains what each of those is good for, why the economics rule out a free unlimited tier, and what the "free" workarounds actually cost once you count the maintenance.

What is genuinely free right now

Four things, with no asterisks worth hiding.

The free tool is not a crippled preview. It returns the same taxpayer record the paid API does — status, constitution, jurisdiction, places of business, e-invoicing enablement and return-filing history. The only difference is volume and the fact that you cannot call it from code.

Why an unlimited free GST API cannot exist

The reason is unglamorous: a GSTIN lookup is not a database read on the provider's own server. It is a request into the government data supply chain, and someone pays for it every single time. Add infrastructure, monitoring, retries, schema normalisation and the engineering to keep all of that working through portal changes, and you have a per-request marginal cost that does not go to zero at scale the way a static web page's does.

So when a service advertises an unlimited free GST API, one of four things is true. It is capping you invisibly and will start failing quietly at volume. It is serving a stale cached snapshot rather than a current record, which is worse than no answer. It is scraping the portal and passing the fragility on to you. Or it is a funded experiment that will introduce pricing or shut down — the outcome that hurts most, because by then it is wired into your onboarding flow.

The "free" alternatives, and what they actually cost

Three workarounds come up constantly. All three are free in licence fee and expensive in every other currency.

Scraping the GST portal. The classic build-versus-buy answer that looks cheap for about three weeks. The portal was designed for a human with a browser: captchas, session handling and markup that changes without notice. Crucially, mandatory multi-factor authentication was rolled out across the taxpayer base by turnover and extended to all taxpayers from 1 April 2025, which breaks unattended session-replay scraping outright. What you actually buy with a scraper is permanent maintenance plus silent failure. The full comparison is in GST API versus scraping the GST portal.

Captcha-solving services. These are paid, so "free" is already gone, and they exist specifically to defeat an access control the site owner put there deliberately. That is a different category of decision from paying a provider for data access, and it is worth naming rather than burying in an architecture diagram. It also does not solve MFA.

Unofficial API wrappers. Open-source packages that wrap the portal are useful for learning and genuinely risky as a production dependency: no availability commitment, no schema stability, no one on call when the portal changes, and you inherit the terms-of-use question of automating a government site you have no agreement with. The maintainer owes you nothing, correctly.

The honest framing is not "free versus paid". It is "someone else's maintenance burden versus your own".

The part that really is free: format validation

One half of the problem genuinely costs nothing, forever, and a surprising number of teams pay for it by accident.

A GSTIN is 15 characters: a 2-digit state code, a 10-character PAN, an entity code, a literal Z, and a check digit computed as a Luhn mod-36 checksum. You can verify all of that in your own code in microseconds. 27AAACR5055K1Z7 passes; a transposed digit does not. Every typo you catch this way is a paid request you never make, which on a 10,000-row vendor master is real money.

What validation cannot tell you is whether the number was ever issued, who holds it, or whether the registration is active today. A well-formed GSTIN that was never allocated will pass every offline check you can write. That distinction — and how fraudsters exploit it — is covered in how to check a fake GST number, and the character-by-character breakdown is in GSTIN format explained.

What a free tier is genuinely good for

Free tiers are not a lesser version of the paid product. They are the right tool for three specific jobs.

• Evaluation. 20 credits is enough to run your own known-status GSTINs through the real endpoint and check that the response actually contains what you need before you spend anything. Include a cancelled vendor and a suspended one — those are where providers differ.
• Genuinely low volume. If you verify a handful of GSTINs a month, the free tool at 5 a day covers you indefinitely and you should not integrate anything.
• One-off checks. A single suspicious invoice, a new supplier's paperwork, a GSTIN on a quotation that does not look right. Paste it into the tool and move on.

Where a free tier stops working is anything with a schedule attached: a signup form that must check every registration, a nightly batch over a vendor master, an accounts payable gate before payment release. Those need a quota you control and an error contract you can code against.

The point where paying becomes the cheaper option

There is a fairly clean threshold. The moment verification becomes part of a repeatable process rather than a human decision, the free options stop being free — they start costing staff time, and staff time is the most expensive input in the whole chain.

Concretely: at ₹0.50 per verification (₹0.40 once a purchase crosses 2,500 credits), checking 1,000 vendors costs ₹500. One person pasting 1,000 GSTINs into a portal one at a time, solving a captcha each round, will spend the better part of two working days on it and make mistakes. The comparison is not close, and it is not really about the money — it is that the manual version cannot be run monthly, which means your vendor master silently goes stale. We work through the arithmetic properly in GST API pricing explained, and the manual-versus-API comparison in API versus manual verification.

If you are past that threshold, the honest next step is not to read more comparisons — it is to run 20 free credits against your own data. Sign up, verify your email, and the API key and credits are available immediately; current per-call rates are on the pricing page, and the evaluation method is in how to choose a GST verification API provider.

Frequently asked questions