canonical: https://jentic.com/apis/gstinapi.in/gstinapi

# Gstinapi In GSTIN Verification API

The GSTIN Verification API looks up an Indian GSTIN for its legal name, trade name, registration status, taxpayer type, and registered address, sourced live from India's official GSP network. It also verifies PANs, finds every GSTIN under a PAN, reports return filing status and compliance, generates and manages e-way bills and e-invoices, and files GSTR-1 and GSTR-3B returns with an OTP. Vendor GSTINs can be watched for change events delivered by webhook.

## For AI agents

Lets an AI agent verify Indian GSTINs and PANs, check GST filing status, generate e-way bills, and file GSTR-1 and GSTR-3B returns.

## Scope

Does not handle income-tax filing, accounting ledgers, or payment collection. Use for GSTIN verification, GST returns, and e-way bills only.

## Capabilities

- Look up an Indian GSTIN for legal name, status, taxpayer type, and address
- Verify a PAN and find every GSTIN registered under it
- Check GST return filing status, frequency, and compliance
- Generate, update, and cancel e-way bills, including consolidated trip sheets
- Save and file GSTR-1 and GSTR-3B returns with an OTP
- Watch vendor GSTINs and receive change events by webhook

## Use cases

### Agent-driven GSTIN verification

An AI agent can verify a counterparty before a transaction through the GSTIN Verification API by looking up the GSTIN's legal name, registration status, taxpayer type, and address, all sourced live from India's GSP network. A free test GSTIN returns a sample in the live response shape, so the flow can be rehearsed. Connected through Jentic, the agent calls only the lookup operations it needs.

Example prompt: Look up a GSTIN and return its legal name, registration status, and registered address

### GST return filing

Businesses filing GST returns need a programmatic path to save, preview, and file. The GSTIN Verification API saves and previews GSTR-1 and GSTR-3B, requests the filing OTP, and files the return once the OTP is entered, and it can generate and cancel e-invoices. An agent can prepare a return and complete filing with the OTP step in the loop.

Example prompt: Save a GSTR-3B return, request the filing OTP, and file it once the OTP is supplied

### E-way bill and vendor monitoring

Logistics and procurement teams generate e-way bills and keep an eye on vendor GST status. The API generates, updates, extends, and cancels e-way bills, including consolidated trip sheets, and watches vendor GSTINs for change events delivered by webhook. An agent can issue an e-way bill for a shipment and alert on a vendor's status change.

Example prompt: Generate an e-way bill for a shipment and add the counterparty's GSTIN to a watchlist for change events

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/gstin/{gstin}` | Look up a GSTIN |
| GET | `/v1/pan/{pan}/verify` | Verify a PAN and get the registered name |
| GET | `/v1/pan/{pan}/gstins` | Find every GSTIN registered under a PAN |
| POST | `/v1/ewaybill` | Generate an e-way bill |
| POST | `/v1/gstr3b/file` | File GSTR-3B with the OTP |
| POST | `/v1/einvoice` | Generate an e-invoice |
| POST | `/v1/watchlists` | Create a watchlist of vendor GSTINs |

## Key resources

- **GSTIN lookup** — Verify a GSTIN and read returns, filing preference, and compliance
- **PAN** — Verify a PAN and find every GSTIN registered under it
- **E-way bills** — Generate, update, extend, cancel, and consolidate e-way bills
- **Returns** — Save and file GSTR-1 and GSTR-3B, and generate e-invoices
- **Watchlists and webhooks** — Watch vendor GSTINs and receive change events

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 48 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 63 / 100
  - AI Discoverability: 76 / 100
- **View full report:** https://jentic.com/apis/gstinapi.in/gstinapi/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the GSTIN Verification API by hand means handling its x-api-key header, switching to a Bearer JWT for watchlist routes, and sequencing the save, OTP, and file steps of a GST return yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The GSTIN Verification API carries the GSTIN, PAN, and return data in the path and body, so a rule bounds which operations your agent may call rather than which taxpayer. You choose the operations it may call, so return filing and e-way-bill generation are not included unless you add them.
- **Credential handling:** Your x-api-key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up a GSTIN' or 'file a GST return', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **AvaTax API** — Global tax compliance and calculation versus this API's India GST focus.
- **TaxJar Sales Tax API** — US sales-tax calculation and filing versus this API's Indian GST operations.
- **Fast GST Refund** — Indian GST refund processing to pair with GSTIN verification and filing.

## FAQ

### What authentication does the GSTIN Verification API use?

The GSTIN Verification API authenticates with an x-api-key header on the GSTIN and filing endpoints, per its OpenAPI spec, and the watchlist routes additionally accept a Bearer JWT dashboard session token. Through Jentic the x-api-key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

### Can I verify a GSTIN and find GSTINs under a PAN with this API?

Yes. The GSTIN lookup returns the legal name, trade name, registration status, taxpayer type, and registered address, sourced live from India's GSP network. The PAN operations verify a PAN and return every GSTIN registered under it.

### What are the rate limits for the GSTIN Verification API?

The OpenAPI spec does not publish fixed rate limits, and every account instead gets up to 75 free lookups that never expire before billed usage begins. Check https://www.gstinapi.in for current limits.

### How do I verify a GSTIN with the GSTIN Verification API through Jentic?

Search Jentic for 'look up a GSTIN' and it returns the GSTIN lookup operation with its input schema, so your agent passes the GSTIN and calls it. Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the GSTIN Verification API from the API Directory, and store your x-api-key once. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the GSTIN Verification API?

Yes. Write a rule that allows only the GSTIN-lookup and PAN-verification operations, so the agent can verify counterparties but cannot file returns or generate e-way bills, and every call it makes is logged.

### Is there a GSTIN Verification API MCP server?

You don't need an MCP server to connect your agent to the GSTIN Verification API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers and calls the operations it needs on demand.