canonical: https://jentic.com/apis/mapmyindia.in/agartala-smart-city-mauja-and-plot-number-to-property-id

# Mapmyindia In Agartala Smart City - Mauja and plot number to property id details (UAT)

The Agartala Smart City Mauja and Plot Number API takes a mauja's LGD village code and a plot number and returns the payment record held for that plot in Agartala. Although the title refers to property id details, version 1.0.1 of the published spec exposes one data lookup, the beneficiary payment status call, which returns paymentStatus, transactionId, amount, and paymentDate rather than a property id. It runs on the MapmyIndia UAT staging host, and a client-credentials token call issues the access token that the lookup sends in its Authorization header.

## For AI agents

Send a mauja's LGD village code and a plot number to the Agartala UAT host and get back the plot's payment status, transaction id, amount, and payment date.

## Scope

Does not return property ids, plot boundaries, or ownership documents in its published spec. Use for looking up the payment record of an Agartala plot by mauja village code and plot number only.

## Capabilities

- Resolve a mauja lgdVillageCode and plotNumber pair to the payment record held for that plot
- Read the paymentStatus, transactionId, amount, and paymentDate returned for a plot
- Obtain an access token with a client_credentials grant using client_id and client_secret
- Exercise the Agartala plot lookup against the UAT staging host before production

## Use cases

### Plot record lookup agent through Jentic

A land-records assistant receives a mauja code and plot number from a citizen and calls this API through Jentic to fetch the plot's payment record. It returns paymentStatus, amount, and paymentDate to the user. The client credentials and access token are held by Jentic, so the agent never handles them.

Example prompt: POST `/amc-ext/api/plot/beneficiary_payment_status` with lgdVillageCode '922851' and plotNumber '1596', plus the Accept header application/vnd.taxsaas.v1+json and your X-Account-Id, then summarise the returned payment record

### Payment reference for a plot file

Case workers attaching a payment reference to a plot file can pull the transactionId and paymentDate from one lookup. The spec's example response shows a PAID status with transaction id AMC-1000253445, which indicates the reference format used on the UAT host.

Example prompt: Look up plotNumber '1596' with lgdVillageCode '922851' and return transactionId and paymentDate for the case file

### UAT integration testing for Agartala plot services

The spec targets stg.mapmyindia.in, so it is a test surface for teams integrating Agartala plot services. The flow is a token call with grant_type client_credentials followed by the plot lookup, which makes it a quick end-to-end check that credentials and headers are wired correctly.

Example prompt: POST `/api/security/oauth/token` with grant_type 'client_credentials', client_id, and client_secret, then call the plot lookup once with a known test plot and confirm a 200 response

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/amc-ext/api/plot/beneficiary_payment_status` | Look up a plot by village code and plot number |
| POST | `/api/security/oauth/token` | Get an access token |

## Key resources

- **Token** — Issue an access token from client credentials
- **Plot payment record** — Look up the payment status, transaction id, amount, and date for a mauja 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-mauja-and-plot-number-to-property-id/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, passing the access token in the Authorization header, and adding the X-Account-Id and vendor Accept headers to each lookup. Through Jentic you install once, import it from the API Directory, store your credentials once, and your agent calls it.
- **Permission scoping:** Plots are identified by query parameters rather than a path id, so rules bound which operations your agent may call, not which plots it may look up. Limit the agent to the operations it needs, such as the plot 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 'look up a plot by mauja and plot number', and Jentic returns the matching operation with its input schema so the agent sends the right query parameters and headers.

## Related APIs

- **Agartala Smart City - Beneficiary Payment Status APIs (UAT)** — Sibling Agartala spec that documents the same plot payment status lookup
- **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 MCP server for the Agartala Mauja and Plot Number API?

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

### Does this API return a property id?

Not in the published spec. Version 1.0.1 documents one data call, the beneficiary payment status lookup, and its response fields are lgdVillageCode, plotNumber, paymentStatus, transactionId, amount, and paymentDate. If you need a property id, confirm with the publisher whether a separate operation exists.

### What authentication does the Agartala Mauja and Plot Number API use?

Per its OpenAPI spec, the plot lookup sends an access token in the Authorization header (the ApiKeyAuth scheme). The token comes 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.

### Can I limit what my agent is allowed to do with the Agartala Mauja and Plot Number API?

Yes. Write a rule that allows the plot lookup and the token call it depends on and nothing else, so a land-records assistant can answer plot questions without reaching other services on the staging host. Your own instance runs those calls.

### What are the rate limits for the Agartala Mauja and Plot Number API?

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

### How do I look up a mauja plot through Jentic?

Add this API to Jentic One from the directory and store your client credentials once. Your agent searches for 'look up a plot by mauja and plot number', sends lgdVillageCode and plotNumber, and reads the payment record from the response. To run it on your own infrastructure, install Jentic One from its GitHub repo.