# India Rent Stats – NoBroker rents by city and locality (`listingworks/india-rent-stats`) Actor

Median monthly rent, rent per m² and size of apartments to rent on NoBroker.in in Bengaluru, Mumbai, Pune, Chennai and Hyderabad, by locality and by BHK, with listing counts. Aggregates only, no listings, addresses or names. Read live each run.

- **URL**: https://apify.com/listingworks/india-rent-stats.md
- **Developed by:** [Yusuke Suda](https://apify.com/listingworks) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 listing analyzeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## India Rent Stats – NoBroker rents by city and locality

Median monthly rent, rent per m² and size of apartments to rent on NoBroker.in in Bengaluru, Mumbai, Pune, Chennai and Hyderabad, by locality and by number of bedrooms (BHK), with the number of listings behind each figure. Delhi NCR is not covered: NoBroker has no city page for it.

### Example

| Region | Sale / rent | Listings | Median asking price | Median price per m² | Median size |
|---|---|---:|---:|---:|---:|
| Pune / Hinjawadi | rent | 18 | ₹27,250 | ₹432 | 69.55 m² |
| Mumbai / Kandivali West | rent | 13 | ₹35,000 | ₹628 | 56.7 m² |
| Bengaluru / other | rent | 125 | ₹25,000 | ₹284 | 95 m² |

Default input, run on 21 October 2026: 1,000 listings read in 3.6 minutes, 290 aggregate rows; at $1.50 per 1,000 listings read the run cost $1.50.

### What you get, and what you don't

- **Counts, not listings.** The run returns aggregate rows only: no titles, no advertisers, no addresses, no texts,
  no links, no contact details, no person's name. Nothing about an individual listing leaves the run.
- **List pages only.** The run reads the site's public search-result pages, paced as the site's own Actor in this
  catalogue is (one request every 2 seconds), and never opens a listing's own page.
- **A sample of the newest listings.** The site lists newest first; the run counts up to `maxListings` of them. The
  summary row says how many were read and, where the site shows it, the site's own total.
- **Medians need 5 values.** A median is shown only where at least 5 listings have the value; otherwise it is empty.
- The last row of every run is a `summary` per site: listings read, the site's own total where shown, whether the run
  stopped at `maxListings`, and any warning (an unknown place, a blocked page).

### Input

| Field | What it does |
|---|---|
| `maxListings` | Listings to read and count at most (default 1,000, up to 10,000), shared evenly across the places searched. |
| `region` | One place only (see below). Empty: every place listed below. |

Example: `{"region": "Pune", "maxListings": 2000}`. An input the run cannot use (a place the site does not know) ends
SUCCEEDED with no rows and the reason in the status message and the run report (`RUN_REPORT`).

### Output

| Field | Meaning |
|---|---|
| `level` | `region` (one row per place and sale / rent), `region_rooms` (per place, sale / rent and bedrooms) or `summary`. |
| `date` | Day of the run (UTC). |
| `source` | The site counted. |
| `region` | The place searched. |
| `transaction` | `sale` or `rent`. |
| `rooms` | Bedrooms (BHK): `0` (studio), `1`, `2`, `3`, `4+`, `unknown`; `all` on `region` rows. |
| `listings` | Listings read in this group. |
| `median_asking_price` | Median asking price (rent: per month); empty below 5 listings. |
| `median_price_per_m2` | Median of price / living area; empty below 5 listings with an area. |
| `median_size_m2` | Median living area. |
| `currency` | INR. |

### How the counts are made

`region` is `city / locality` as NoBroker names the locality. In each city the 15 localities with the most listings in the run keep their own rows; the rest are `<city> / other`. With no `region` the run reads all five cities, sharing `maxListings` evenly (200 each by default); name one city for more of its localities.

Rents are the monthly rents shown. Area is converted from square feet to m²; rent per m² is rent divided by that area.

### Pricing

$1.50 per 1,000 listings read (event `listing-analyzed`), no start fee. The aggregate rows themselves
are free: a default run reads up to 1,000 listings and costs at most $1.50. Set a maximum charge per run
in the run options to cap it.

### Good to know

- The data is what NoBroker.in shows on its public list pages on the day of the run.
- Run it on a schedule (daily or weekly) and keep the datasets for a time series; each row carries its `date`.
- Questions or a missing region: open an issue on this Actor.

# Actor input Schema

## `maxListings` (type: `integer`):

How many listings the run reads and counts at most (charged per listing read). The counts are a sample of the newest listings, not the whole market, unless the site holds fewer. Shared evenly across the places and sale / rent searched.

## `region` (type: `string`):

Count only this place: give one of Bengaluru, Mumbai, Pune, Chennai or Hyderabad; Delhi NCR has no city page on NoBroker. Empty: all 5 cities.

## Actor input object example

```json
{
  "maxListings": 1000,
  "region": ""
}
```

# Actor output Schema

## `overview` (type: `string`):

The aggregate rows of the run.

## `summary` (type: `string`):

One row per site: listings read and warnings.

## `runReport` (type: `string`):

Every search made, with its verdict.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("listingworks/india-rent-stats").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("listingworks/india-rent-stats").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call listingworks/india-rent-stats --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,listingworks/india-rent-stats"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/dzITFqbx6okKWdceB/builds/P2HUrsdJ66mdagxyN/openapi.json