Install Jentic One Beta

Connect the Agartala Smart City - Beneficiary Payment Status APIs (UAT) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agartala Smart City - Beneficiary Payment Status APIs (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-beneficiary-payment-status" | 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-beneficiary-payment-status" | 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 - Beneficiary Payment Status APIs (UAT) API.

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

GET STARTED

Start building with Agartala Smart City - Beneficiary Payment Status APIs (UAT) API

Explore with Jentic One

View OpenAPI Document

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

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.

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.

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

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

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

POST

/amc-ext/api/plot/beneficiary_payment_status

Look up a plot's payment status

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, 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 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 '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.

FAQs

Specific to using Agartala Smart City - Beneficiary Payment Status APIs (UAT) API through Jentic.

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.

Mapmyindia In Agartala Smart City - Beneficiary Payment Status APIs (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

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.

Use for: Check whether plot 1596 in village code 922851 has been paid, Get the transaction id for a beneficiary payment on an Agartala plot, Retrieve the payment date and amount for a plot number, I need to verify a property payment before issuing a clearance

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

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.

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 - Beneficiary Payment Status APIs (UAT) to your agent

Capabilities

Start building with Agartala Smart City - Beneficiary Payment Status APIs (UAT) API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

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

Jentic AI Readiness Score

Agartala Smart City - Beneficiary Payment Status APIs (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