Cenogram

Cenogram Parcels API

Parcel-first lookup: resolve a cadastral identifier, read the parcel core, the deed history recorded against it, and per-parcel context layers (flood, zoning, permits, buildings, heritage, landslide, subsurface, surroundings, transit, road access, agricultural use). Works for any existing parcel, including parcels that have never been transacted.

GitHub OpenAPI

Operations 19

GET /api/v1/parcels/{key}/permits Building permits & notifications for the parcel #
GET /api/v1/parcels/{key}/farmland Agricultural land-eligibility for the parcel #
GET /api/v1/parcels/{key}/planning General-plan zoning for the parcel #
GET /api/v1/parcels/{key}/buildings Buildings standing on the parcel #
GET /api/v1/parcels/{key}/flood Flood-zone risk for the parcel #
GET /api/v1/parcels/{key}/heritage Heritage-listing status for the parcel #
GET /api/v1/parcels/{key}/landslide Landslide-hazard for the parcel #
GET /api/v1/parcels/{key}/nature Nature (forest amenity + protected-area restriction) for the parcel #
GET /api/v1/parcels/{key}/subsurface Subsurface constraints for the parcel (mining terrains + groundwater reservoirs) #
GET /api/v1/parcels/{key}/surroundings Surroundings distances for the parcel #
GET /api/v1/parcels/{key}/transit Public transport access for the parcel #
GET /api/v1/parcels/{key}/land-class Land-use and soil-quality classification for the parcel #
GET /api/v1/parcels/{key}/mpzp Local spatial development plans (MPZP) covering the parcel #
GET /api/v1/parcels List parcels #
GET /api/v1/parcels/search Search parcels #
GET /api/v1/parcels/{key} Parcel core (cadastral) #
GET /api/v1/parcels/{key}/transactions Parcel transaction history #
GET /api/v1/parcels/resolve Resolve a parcel #
GET /api/v1/parcels/{key}/report Parcel report (composite dossier) #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/cenogram-pl/openapi/cenogram-pl-parcels-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/cenogram-pl:cenogram-pl-parcels-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

cenogram-pl-parcels-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Cenogram Parcels API
  version: 1.0.0
  description: 'Property and parcel intelligence for Poland. 8M+ verified transactions from the official RCN registry (Rejestr Cen Nieruchomości) — prices from notarial deeds, not asking/listing prices, from 2003 to present, nationwide. On top of prices: the picture we hold of a parcel — cadastral core, the deed history recorded against it, and context layers (flood hazard, general-plan zoning, building permits, structures, heritage, landslide hazard, subsurface constraints from mining terrains and groundwater reservoirs, surroundings, transit access, road access, agricultural use), plus municipality-level demographics and infrastructure signals, and a comparable-based valuation estimate. Context layers are sourced from official public registers. Transaction coverage is nationwide; the cadastral parcel corpus is near-complete but not the whole register and not live — every parcel collection carries a `corpus_coverage` block measuring what we hold for the counties it addresses. Access is metered in tokens: a new account starts with a token allowance and a trial, after which a free account keeps calling on a recurring free allowance, and paid plans raise it. Current allowances, trial length and prices live at https://cenogram.pl/api and are deliberately not repeated here, because a figure frozen into this description goes stale on its own. A 402 response carries the current balance and, on a free account, the date the next tokens arrive. Every operation states its price both in prose and machine-readably, in the `x-cenogram-token-cost` extension field, generated from the one pricing table. Tokens and credits are the same unit under two names: the response headers (`X-Credits-Cost`, `X-Credits-Balance`, `X-Credits-Refunded`) and some older endpoint descriptions say credits. Working with an AI assistant? Give it https://cenogram.pl/api/llms.txt — this whole surface as one plain-text file, costs, refund rules and response conventions included.'
servers:
- url: https://cenogram.pl
security:
- apiKey: []
tags:


# --- truncated at 32 KB (52 KB total) ---
# Full source: https://artifacts.apis.io/cenogram-pl/openapi/cenogram-pl-parcels-api-openapi.yml