canonical: https://jentic.com/apis/mapmyindia.in/agartala-smart-city-beneficiary-payment-status

# Mapmyindia In Agartala Smart City - Beneficiary Payment Status APIs (UAT)

The Agartala Smart City Beneficiary Payment Status API looks up whether a payment recorded against a land plot in Agartala has been made, using the plot's LGD village code and plot number. A lookup returns the paymentStatus, transactionId, amount, and paymentDate for that plot, in the application/vnd.taxsaas.v1+json media type. The spec describes a UAT deployment on the MapmyIndia staging host, where a client-credentials token call issues the access token that the lookup sends in its Authorization header.

## For AI agents

Check the payment status of an Agartala land plot by LGD village code and plot number, returning status, transaction id, amount, and payment date from the UAT environment.

## Scope

Does not accept payments, issue receipts, or return maps or plot boundaries. Use for looking up the payment status of an Agartala plot only.

## Capabilities

- Look up the paymentStatus of a plot from its lgdVillageCode and plotNumber
- Return the transactionId, amount, and paymentDate recorded for a paid plot
- Obtain an access token with a client_credentials grant using client_id and client_secret
- Test a beneficiary payment integration against the UAT staging host before going live

## Use cases

### Payment check agent through Jentic

A municipal help-desk agent answers "has my plot payment gone through?" by calling the Beneficiary Payment Status API through Jentic. It sends the lgdVillageCode and plotNumber and replies with paymentStatus, amount, and paymentDate. The client credentials and the issued token are handled by Jentic, so the agent never sees them.

Example prompt: POST `/amc-ext/api/plot/beneficiary_payment_status` with lgdVillageCode '922851' and plotNumber '1596', the Accept header set to application/vnd.taxsaas.v1+json and your X-Account-Id, then report paymentStatus and paymentDate

### Clearance pre-check for a plot

Before a property-related service is issued, staff confirm that dues on the plot are settled. One lookup returns paymentStatus such as PAID together with the transactionId, which can be quoted on the clearance record as the payment reference.

Example prompt: Look up plotNumber '1596' in lgdVillageCode '922851', and if paymentStatus is 'PAID' return the transactionId and amount for the clearance record

### UAT integration testing

The spec targets the stg.mapmyindia.in staging host, so it suits building and testing an integration before moving to production credentials. A test run first calls the token operation with grant_type client_credentials, then sends the returned access_token in the Authorization header of the lookup.

Example prompt: POST `/api/security/oauth/token` with grant_type 'client_credentials', client_id, and client_secret, then use the access_token to call the payment status lookup for one known test plot

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/amc-ext/api/plot/beneficiary_payment_status` | Look up a plot's payment status |
| POST | `/api/security/oauth/token` | Get an access token |

## Key resources

- **Token** — Issue an access token from client credentials
- **Beneficiary payment status** — Look up the payment status, transaction id, amount, and date for a plot

## 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:** 53 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 87 / 100
  - AI-Readiness & Agent Experience: 26 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/mapmyindia.in/agartala-smart-city-beneficiary-payment-status/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 this API by hand means calling the client-credentials token endpoint, carrying the access token into the Authorization header, and adding the X-Account-Id and vendor Accept headers. Through Jentic you install once, import it from the API Directory, store your credentials once, and your agent calls it.
- **Permission scoping:** The plot is identified by query parameters, not a path id, so rules bound which operations your agent may call, not which plots. Limit the agent to the operations it needs, such as the payment status lookup.
- **Credential handling:** Your client credentials and access token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check plot payment status', and Jentic returns the matching operation with its input schema so the agent sends lgdVillageCode and plotNumber correctly without reading the docs.

## Related APIs

- **Agartala Smart City - Mauja and plot number to property id details (UAT)** — Companion Agartala Smart City spec from the same publisher, keyed on village code and plot number
- **Authorized Partner API Specification** — Access to government-issued documents in a citizen's DigiLocker account
- **Nominatim Geocoding API** — Geocode a village or locality name to coordinates

## FAQ

### Is there an Agartala Smart City MCP server?

You don't need an MCP server to give your agent the Beneficiary Payment Status API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. The lookup is found by intent when needed, so no extra tool definitions sit in the agent's context.

### What authentication does the Beneficiary Payment Status API use?

Per its OpenAPI spec, the payment lookup sends an access token in the Authorization header (the ApiKeyAuth scheme). You get that token from POST `/api/security/oauth/token`, which needs no Authorization header itself and takes grant_type client_credentials, client_id, and client_secret as query parameters. The lookup also requires an X-Account-Id header.

### What does a payment status lookup return?

The response carries lgdVillageCode, plotNumber, paymentStatus, transactionId, amount, and paymentDate. The spec's example shows paymentStatus as PAID; other status values are not enumerated, so treat the field as open-ended.

### Can I limit what my agent is allowed to do with the Beneficiary Payment Status API?

Yes. Write a rule that allows only POST `/amc-ext/api/plot/beneficiary_payment_status` and the token call it depends on, so a help-desk agent can answer plot payment questions and reach nothing else on the host. Your own instance runs those calls.

### What are the rate limits for the Beneficiary Payment Status API?

The OpenAPI spec does not specify rate limits. Check with MapmyIndia, the publisher of this spec on SwaggerHub, for current limits on the UAT host.

### How do I check a plot's payment status through Jentic?

Add the Beneficiary Payment Status API to Jentic One from the directory and store your client credentials once. Your agent searches for 'check plot payment status', sends lgdVillageCode and plotNumber to the lookup, and reads paymentStatus from the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.