get_locality_insights

Aggregated insights for a locality in a covered city — ₹/sqft, supply, demand pulse, livability grade.

Endpoint POST https://api.avnester.com/public/v1/get_locality_insights

Parameters

The most-used parameters. Full schema in the OpenAPI document.

localitystringrequired: Locality name within an Indian city.
citystringrequired: Indian city (required).

Worked example

# get insights for Saravanampatti

curl -X POST https://api.avnester.com/public/v1/get_locality_insights \
  -H 'Content-Type: application/json' \
  -d '{
       "locality": "Saravanampatti",
       "city": "Coimbatore"
     }'

Response

{
  "supported": true,
  "city": "Coimbatore",
  "locality": "Saravanampatti",
  "insights": {
    "pricePerSqftInr": 5400,
    "avgPriceInr": 6750000,
    "rent2bhkInr": 18500,
    "rentalYieldPct": 4.1,
    "priceGrowth1YPct": 12,
    "supplyCount": 142,
    "demandPulse": "high",
    "livabilityScore": 78,
    "livabilityScoreBasis": "editorial-estimate",
    "investmentGrade": "A",
    "highlights": ["IT corridor", "strong rental demand"],
    "watchouts": ["traffic peaks 8–10am"],
    "priceTrends": [{ "period": "2026-09", "avgPriceInr": 6750000 }],
    "strengthTags": ["it_proximity", "schools"]
  },
  "freshness": { "updatedAt": "2026-09", "sourceCount": 2, "confidence": "medium" },
  "disclaimer": "Livability + investment grades are AVnester estimates, not professional advice.",
  "attribution": "AVnester"
}

Run this example in the playground

Rate limits

OAuth (Developer)

30 / min

The same ceiling applies to every tool on a given plan, on both the MCP and REST transports; every plan’s is on Pricing. OAuth registration is free and self-serve. Calls made without signing in have their own per-IP limits — see the quickstart.

Common errors

200supported: false in body
Out-of-coverage queries are not HTTP errors — surface the scopeMessage from the response body to the user.
429Rate limit exceeded
Back off until the time in the Retry-After header. Signed in with OAuth, the per-tool limit is counted per user instead of per address; a paid plan raises it.
429Daily call limit reached (calls without signing in)
Retry-After counts to 00:00 UTC, and only calls that returned an answer count. Signed in, calls count against your plan instead of your IP address.
429Daily new-locality limit reached
Localities you have already queried today still work; Retry-After counts to 00:00 UTC. Signing in on the free plan does not lift this limit — a commercial licence does.

Next steps

→ Try get_locality_insights in the playground (no signup)
→ Register an OAuth client (free on the Developer plan)
→ Browse the other 10 tools
→ Full schema in the OpenAPI spec