Install Jentic One Beta

Connect the Agartala Smart City - Mauja and plot number to property id details (UAT) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agartala Smart City - Mauja and plot number to property id details (UAT), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapmyindia.in%2Fagartala-smart-city-mauja-and-plot-number-to-property-id" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmapmyindia.in%2Fagartala-smart-city-mauja-and-plot-number-to-property-id" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Agartala Smart City - Mauja and plot number to property id details (UAT) API.

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

GET STARTED

Start building with Agartala Smart City - Mauja and plot number to property id details (UAT) API

Explore with Jentic One

View OpenAPI Document

★ 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.

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.

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.

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

2 endpoints — 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.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Agartala Smart City - Mauja and plot number to property id details (UAT) API through Jentic.

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.

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

Browse all Mapmyindia In APIs

AI ReadinessFoundational (C-)53/100

See full scorecard

Community OpenAPI document · agent-readyFinanceTaxapiKey2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For 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.

Use for: Look up plot 1596 in mauja village code 922851, Get the payment record for an Agartala plot by mauja and plot number, Check whether a plot in this mauja shows a PAID status, Retrieve the transaction id linked to a plot number

Not supported: 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.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: ASignals: 4

73%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

21%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

85%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Agartala Smart City - Mauja and plot number to property id details (UAT) to your agent

Capabilities

Start building with Agartala Smart City - Mauja and plot number to property id details (UAT) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

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

Jentic AI Readiness Score

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

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness