---
title: "Where a street sits in its locality"
method: POST
path: "/api/v1/tools/locality_value_context"
---

# Where a street sits in its locality

`POST /api/v1/tools/locality_value_context`

## Request

- Base URL: `https://verified.realestate`
- URL: `https://verified.realestate/api/v1/tools/locality_value_context`
- Auth: HTTP bearer

Put a guideline value in context: where a street's rate sits within the range of its village, its SRO and its registration zone, with the cheapest and dearest comparable streets named, the street count, and the sub-registrar office address, phone and email. Use for "is that expensive for the area", "how does this street compare to the rest of the village", "what is the cheapest/priciest street around here", "which streets nearby are dearer", and to add a sanity check after a guideline value lookup. Pass the village and zone (the guideline value lookup or the parcel lookup returns them); street_name is optional and when omitted you get the village picture without a specific street. 1 credit. Costs 1 credit per call, waived when nothing is found.

## Request body

- object
  - `street_name` string: Street name to benchmark. Partial names match. Omit for a village-level picture.
  - `village` string: Village name as it appears in the guideline register
  - `sro` string: Sub-registrar office name
  - `zone` string: Registration zone, e.g. Chennai

## Response `200`

The envelope: ok, status, data, credits_charged, balance_after, request_id

## Other responses

- `401`: No valid credential
- `402`: Not enough credits
- `429`: Rate limit

---

[API](https://skmtc.dev/verified/apis/landlens-tool-api.md) · [All operations](https://skmtc.dev/verified/apis/landlens-tool-api/llms.txt) · [OpenAPI document](https://skmtc.dev/verified/apis/landlens-tool-api/revisions/7923c1c24431?raw)