Skip to content

API & MCP

Put a land verdict inside your own underwriting flow.

The same engine behind the workspace, reachable as a REST API and as an MCP server, so a human, a pipeline or an agent can screen a parcel against all 119 layers without opening a map.

Request API accessAsk for the docs

In production with pilot partners. Keys are issued per engagement, so the schema and limits fit your volume.

Quickstart

One call from a survey number to a decision.

Name the parcel and the intended use. Get back a score, the flags that shaped it, and every field's provenance.

curl -X POST https://api.agtmap.com/v1/parcel/verdict \
  -H "Authorization: Bearer $AGT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "state": "gujarat",
    "survey_no": "412/2",
    "use_context": "urban_landbank"
  }'

Surface

Six endpoints cover almost everything people ask for.

Screening, dossiers, spatial queries and availability checks. Anything beyond is usually a layer request, not an API one.

POST/v1/parcel/verdictScored verdict for a parcel, by survey number or geometry, weighted for a use context.
POST/v1/area/dossierFull report for a drawn area, with every family screened, with sources and read dates.
POST/v1/spatial/queryIntersect any catalogue layer with a point, radius or polygon. Returns GeoJSON or vector tiles.
GET/v1/spatial/availabilityWhich layers are readable at a location, before you spend a call finding out.
POST/v1/risk/assessmentHazard screen: flood history, seismic zone, protected-area overlap, restricted designations.
POST/v1/screen/submitAsynchronous bulk screening across a parcel list, ranked and returned as a shortlist.

Design principles

Built to survive an audit, not just a demo.

Provenance in the payload

Your audit trail is the response body, not a separate export.

Nulls are explicit

An unreadable record returns `unavailable` with a reason code. Never a zero or a guess.

Geometry in, geometry out

Send a survey number, point, radius or polygon. Get back the geometry the answer used.

Deployable where you need it

Managed by us, or inside your own VPC for data that cannot leave it.

Model Context Protocol

Give your agent the ground truth it is currently guessing at.

Point an MCP client at our server and the land tools appear alongside everything else it can do. No prompt engineering about geography. The agent queries PostGIS and gets a real answer.

  • Tools are discovered automatically, with no per-tool wiring
  • Same auth, same provenance guarantees as the REST API
  • Scoped keys, so an agent only reaches the layers you allow
  • Works with Claude, and any other MCP-capable client
{
  "mcpServers": {
    "agtmap": {
      "command": "npx",
      "args": ["-y", "@agtmap/mcp-server"],
      "env": { "AGT_API_KEY": "${AGT_API_KEY}" }
    }
  }
}

// Tools the agent then discovers on its own:
//   agt_parcel_verdict      scored go / no-go
//   agt_area_dossier        report for a drawn area
//   agt_spatial_query       intersect a layer with geometry
//   agt_layer_availability  what is readable here
//   agt_nearby              POIs, infra and hazards in a radius

Tell us your volume and we will get you a key.

Pilot access is issued per engagement. Send us the shape of what you want to run (parcels per month, states, and where the call has to happen) and we will come back with a schema and a quote.

Request API accessBrowse the layers