Skip to main content
Glama
814,183 tools. Updated 2026-11-21 00:33

"zoning" matching MCP tools:

  • Checks height, separation, floor area, setbacks and lot coverage of a garden suite against Toronto By-law 849-2025. Preliminary planning only. Example: /api/tools/garden-suite-zoning-checker?zone=yes&laneway=no&lot_area=400&lot_depth=40&lot_frontage=10&house_gfa=180&house_footprint=90&ancillary_footprint=40&suite_height=4&separation=5&suite_gfa=50&rear_setback=2&side_setback=1.5&one_storey=yes&rear_openings=no&side_openings=yes
    ConnectorNo auth
  • What was actually said out loud at a city council meeting, planning-commission hearing, or any other public city-government meeting — about zoning, housing, the city budget, taxes, permits, ordinances, roads, parks, police, or public comment. Keyword search across transcript segments; each hit includes speaker, snippet, timestamp, and — when the speaker matches an elected official — an `official_id` UUID. WHEN: 'What did people say about X?', 'When was Y last discussed?', or any query where the value is *what was spoken in a meeting*. WHEN NOT: For one person's complete speaking history, use search_by_official (better signal, no false positives from name collisions). For ordinance text, packets, or attached PDFs, use search_documents. For 'recent' or 'this year' questions pass `since` — the corpus runs back years, and without a window old material competes with new. For 'what did OFFICIALS say' pass officials_only — it keeps segments whose speaker matched the city roster (elected, appointed or senior staff), because everyone else is unnamed by design and their quotes cannot be cited to a person. EXAMPLES: { "q": "short-term rentals", "cities": ["lehi-ut"] } { "q": "housing affordability", "cities": ["lehi-ut"], "since": "2026-01-01", "officials_only": true } { "q": "downtown parking", "cities": ["lehi-ut"], "meeting_types": ["city_council"] } { "q": "developer Main Street" } — last meetings across allowed cities, newest first hits: [] means no transcript segments matched — simplify the query and retry; never report it as missing access to a city.
    ConnectorAPI key
  • Report BUILDING PERMITS and other construction acts on a property, around it, or in an area (gradbeno dovoljenje, uporabno dovoljenje, inspekcija, legalizacija). INPUT: a property `ref` or a parcel `ref` (from find_parcels / find_by_cadastral_ref — an unbuilt plot), OR an `area` from find_area. Optional `radius_m` (default 300, max 2000) and `since_year` (2015 or later). READ: `subject` — `parcel` answers for that parcel alone. `on_property` for acts on the property's own parcel; `nearby.by_class` for acts within `radius_m`; `municipality.years` for the local rate beside `national_acts_per_1000_addresses`. READ: `act_class` on every row. `build_permit` = work ALLOWED, `use_permit` = building FINISHED, `start_notice` = work STARTED. READ: `is_adverse`. `enforcement` (inspection proceedings) and `legalisation` (built first, legalised after) are FINDINGS against a property, not permissions. READ: `freshness.is_stale` and `freshness.age_days` before saying nothing new was filed. NEVER: add classes into one total, or read `n_pending` as a construction pipeline — most pending acts are `enforcement`, i.e. open proceedings. NEVER: read an empty `on_property` as "never permitted" — old parcel numbers are lost (`freshness.share_keys_resolved_to_parcel`), so a parcel's history is a floor. THEN: `property_land` for the designated use — nothing here is zoning. `neighbourhood` for what stands around it.
    ConnectorOAuth
  • Use when the user is screening a site in Harris County, Texas (Houston) for development, investment or lending and asks what surrounds it: "what is around this lot?", "how much vacant land is nearby?", "is this block mostly commercial or residential?". Returns the parcels within the radius by land-use category from the Harris County Appraisal District, with counts, appraised value, the vacant share and the site parcel’s class. Houston has no zoning code, so this is land use, not zoning; owner names are never returned. Refuses before you are charged outside Harris County or if the totals do not reconcile. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one release (current appraisal year); place: address or lat/lon, radius_miles (Harris County); segment: land-use category (in the result). Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For who lives around the site, use run_trade_area.
    ConnectorNo auth
  • Property-tax rates voted in a French commune for one fiscal year, from DGFiP: taxe foncière sur les propriétés bâties (TFPB) global rate and household-waste tax (TEOM) rate. REQUIRED: code_insee (INSEE commune code, e.g. "33063"; get it from resolve_location) Optional: exercice (fiscal year, default: latest ingested), include_components (constituent rates by authority) Commune rate only, never a property's tax amount: a bill also depends on its taxable base, exemptions and TEOM zoning. Say "taux de taxe foncière dans la commune", never "votre taxe foncière". teom.status is "not_available_or_not_representative" when the rate is null (no TEOM, REOM, or zoned). Always show source.publisher, source.dataset and source.source_updated_at. Cost: 5 credits per call (refunded when no rate is found)
    ConnectorAPI key
  • The whole dossier for one land parcel in one call. Contains the parcel core (location, area, land use, designation); fourteen layers (flood, heritage, landslide, subsurface, surroundings, transit, general-plan zoning (POG), local plans (MPZP), buildings, building activity, agricultural eligibility, land/soil class, nature, road access); the parcel's transactions (newest first, up to 20); local price context (county and gmina median zł/m², last 12 months); municipal context (demographics, infrastructure signals); and a parcel-shape section (outline geometry only). For a coordinate or 'locality + number' use resolve_parcel first; for a street address use list_parcels_in_area. For the plan or designation pass preset="zoning" (core, MPZP, POG, nearby-designation signal only); preset="mpzp" returns the core and the local plans only, preset="land_class" the core and the land-use and soil-quality classification only. preset="mpzp": per plan its title, resolution, legal status, share of the parcel and check date; designations in the municipality's own wording. MPZP is not the general plan (POG): if the state is unknown, preset="zoning" adds POG and a nearby-deeds signal, not a finding on the designation. preset="land_class": the land-use categories and soil grades entered for the parcel, whether any grade is in the protected I-III range, whether the parcel is inside a city boundary (changes the re-designation rule), and a re-designation note with the date the legal state was verified. They come back as SETS with no area, so the answer can never say which category prevails. Answered only where the county publishes the classification. Not legal advice. Section states: covered; covered_no_data (checked, nothing found; billed); not_covered (outside our data; refunded); not_computed (timed out; refunded - the report can be partial). The local-plan section answers in_plan / no_plan / unknown (unknown is never a claim that no plan exists). Context sections use full / low_sample / suppressed / no_data (shape: full / no_data). Long lists are capped with a count. Reading it: the nearby designation signal comes from RCN deeds of neighbouring land, not the planning register - it describes the neighbourhood, not this parcel; confirm with the local plan (MPZP) or a zoning decision. Neither it nor the shape section says whether a parcel can be built on or divided. Construction age is an ESTIMATE with an interval (permit records start in 2016), often "not established". Costs 45 API tokens (preset="zoning": 11), billed by outcome: an unresolvable parcel is refunded; a resolved one with no layer data pays only the 1-token core floor; with a covered layer, in full. preset="mpzp" and preset="land_class" cost 4 each; a checked negative (no_plan, covered_no_data) costs 1, and unknown, not_covered and not_computed are refunded. Calls are rate-limited per API key (shared by parallel agents); on "Too many requests" wait the given seconds and retry sequentially.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to look up public NYC zoning facts for tax lots and zoning districts, including built and allowed FAR, lot and building areas, estimated unused floor area, and district rules. Provides read-only tools for address or BBL lot lookup and zoning district reference data.
    3
    85 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to answer civic questions about Virginia state, county, and municipal public data, including zoning, parcel, boundary, and Code of Virginia lookups, with provenance on every answer.
    5
    1
    Apache 2.0

Matching MCP Connectors

  • Planning and zoning records: 25 jurisdictions in Lake, Orange, Osceola, Polk, Seminole counties, FL

  • Check if a Florida address can build an ADU: county GIS zoning, eligibility verdict, local rules.

  • Deep parcel and building analysis for Slovenia using GURS WFS data. Returns zoning, actual use, heritage protection, road access, buildings on parcel, and utilities. USE FOR: - "Analyze parcel 3086 in Ljubljana center" - "Find buildable parcels ~500m² in Ljubljana" - "What buildings are on this parcel?" - "Find parcels near these coordinates" - "Get full details on building 1234" NOT FOR: simple parcel lookup → use slovenia-cadastre instead (faster, lighter). NOT FOR: spatial/zoning map queries → use slovenia-wfs-expert instead. SEARCH MODES — pick ONE per call: 1. PARCEL BY NUMBER (requires --parcel AND --ko) → --parcel 3086 --ko 1725 2. LOCATION SEARCH (requires --lat AND --lon, or --location) → --lat 46.058 --lon 14.501 --radius 100 → --location "Tivoli Park Ljubljana" --radius 200 3. BUILDING BY NUMBER (requires --building, optionally --ko) → --building 1234 --ko 1728 4. COMMUNITY SEARCH (requires at least --community or --size) → --community LJUBLJANA --size 500 --buildable COMMON KO IDs: 1725 = Ljubljana center 1728 = Ljubljana Šiška 1740 = Ljubljana Bežigrad 2131 = Maribor NOTE: This tool makes multiple WFS calls per result and can be slow (10-30s). Use --limit to keep response times reasonable.
    ConnectorNo auth
  • 빌라·오피스텔·단독주택·토지의 매매 실거래가를 조회한다(아파트는 이 도구가 아니다). **아파트는 이 도구가 아니다.** 빌라(다세대·연립)·오피스텔·단독주택·토지 **전용** 실거래 **매매가** 조회다 — 응답 = 최근 거래(recent) + 집계(stats: 표본 수·가격·상위 구성). 질문에 '아파트'가 있으면 여기서 멈추고 아파트 축으로 가라 — 지역·법정동 월별 추이는 realty_region_price_stats, 단지·평형별 시세는 realty_search_complexes, 단지 평형의 건별 내역(계약일·층·가격)은 realty_complex_pyeong_price다. **셋 다 region에 '강남구 대치동'처럼 법정동을 그대로 받는다** — 동 단위로 좁히려고 이 도구로 오지 마라. property_type 네 값 중 아파트에 가까운 것은 없고, 아무거나 고르면 **응답은 200이고 행도 채워져 나오므로 틀린 줄 모른다**(2026-08-23 PlayMCP QA 실측: '강남구 대치동 아파트 최근 실거래가'에 villa 5건이 아파트로 답해졌다). **매매 데이터만 있다** — 전월세를 물으면 이 축엔 데이터가 없다고 답하라(추정 금지). **도시형생활주택은 property_type에 없고 가를 수도 없다** — 원천에 유형 코드가 없어 아파트·연립다세대·오피스텔 신고에 섞여 있다. villa/officetel 값을 도시형생활주택 시세로 부르지 말고 섞여 있다고 밝혀라(응답 urban_housing_notice). 면적 기준: villa/officetel은 전용면적(area_m2·area_pyeong), house는 대지(land_*)와 건물(building_*) 분리, land는 계약면적·지목(land_category)·용도지역(zoning)이 온다. land의 share_type='지분' 행은 필지 일부 거래라 면적당 가격 비교에 쓰지 말 것(집계는 지분·해제 제외 — 응답 note 참조). 경매에 나온 빌라·다세대(지분 물건 포함)의 입찰가를 정할 때 **견줄 실거래 시세**도 여기서 잡는다.
    ConnectorNo auth
  • Trace how two named things in the planning record connect, and report how specific that connection is. Give `from` and `to` for the shortest route between them; give `from` alone to rank what one actor connects to; give neither to rank the corpus's most specific connections. Endpoints are entity, meeting, or named-pattern slugs; list_entities, list_meetings and list_patterns discover them. Routes run over the three layers where a shared node is a specific claim: meeting attendance transcribed from agendas and minutes (249 references across 78 meeting records; a meeting record holds a median of 3 entities and at most 12), peer claims authored on an entity dossier (162 links, 44 of them stated on both dossiers), and shared named patterns (58 references across 15 patterns; a pattern holds a median of 2 entities and at most 10). That substrate is 161 nodes and 469 links over 68 entities, in one connected component. Place, corridor, brief and watch links serve here as filters and citations rather than as routes: the us-27-south-lake node alone carries 117 links, so a route through it would hold for nearly every pair in the corpus. Hop count is a result here rather than an input. Across the full frontmatter graph, 94.5% of entity pairs already sit within two steps and a three-step expansion reaches a median of 235 of 243 nodes, so depth returns the corpus rather than an answer. What discriminates is the degree of the WIDEST node a route passes through, and the ranking leads on it: a route is only as specific as its least specific waypoint. Two more measured properties travel with every row: how many equally-short routes exist (uniqueness runs 65% at two hops, 40% at three, 14% at four), and whether the two endpoints are minuted in disjoint jurisdictions, which 15 of 68 entities are positioned to be. `interior_degrees` carries every degree on the chain so you can re-rank on any of them, and `provenance` says whether the whole join rests on the meeting record, on a curator’s hand, or on both. Filter with `evidence` to choose which layers may carry a hop, `crossing` to keep only pairs minuted in different jurisdictions, and `exclude_published` to keep only pairs the observatory’s own briefs have not already put together. Every response reports how many of the 2,278 possible entity pairs the filters matched, splits them by provenance, and accounts for the rest, so a query that discriminated nothing says so in its own output. Note one interaction the response also states: two entities minuted in one room share that room’s jurisdiction, so `crossing: "jurisdiction"` holds no two-hop minuted route, and the minuted routes that satisfy it run three hops or more. What it leaves undetermined, stated on every call: vote outcomes and dispositions, which live in meeting prose and item tables; direction and sequence, since a route is co-occurrence in a record; and the 347 of 425 meeting records not yet linked to an entity, where what the tool covers is what has been curated. In from and sweep modes, rows that share a chain of intermediaries collapse to one finding, which names the rest of its roster in `route_also_joins`. Pair with describe_entity for a node’s full dossier, describe_meeting for the room itself, and semantic_search for prose.
    ConnectorNo auth
  • Anything about a city council, mayor, ordinance, zoning case, development permit, meeting agenda, or municipal budget. Combined keyword search across public city-government meeting transcripts AND meeting documents (agendas, minutes, packets, ordinances). Returns results with opaque ids — pass an id to the fetch tool for the full transcript or document text. OpenCity URLs in the query are understood as scope, not text: a city site (taylorsville.openutah.org) narrows to that city, a state site (utahrecord.org, myopentexas.org) narrows to that state, and a full meeting URL resolves to that exact meeting. A bare URL with no other words returns that scope's most recent activity. WHEN: General civic questions ('what has the city said about X?') from clients that auto-route through search/fetch (e.g. ChatGPT connectors), and whenever the user pastes an opencity/openutah/opentexas-style URL. WHEN NOT: If search_meetings / search_documents / list_officials are available to you, prefer them — they take filters (city, meeting type, doc type) and return structured fields this tool flattens away. EXAMPLES: { "query": "short-term rental ordinance" } { "query": "parking taylorsville.openutah.org" } — 'parking', scoped to Taylorsville { "query": "utahrecord.org" } — recent activity across Utah cities Empty results mean no records matched the query — never interpret them as missing access or permissions; retry with broader keywords instead.
    ConnectorAPI key
  • How a local issue developed over time — a zoning change, a housing or density fight, a tax or fee, a road, park, or police matter. Returns the chronological lifecycle of the issue across meetings (raised → discussed → voted), oldest first, each entry linking to the meeting. WHEN: 'How has the short-term-rental issue progressed?', 'When was X first discussed and what happened since?'. WHEN NOT: For what a specific *person* said, use search_by_official; for how they voted, use track_position. For a one-off keyword search, use search_meetings. Pass `city` whenever you pass `q`. The same phrase names a different fight in every city, and without a city the match is ambiguous — you will get `issue: null` plus a `candidates` list to choose from rather than a confident answer about the wrong city. Check `candidates` even on a resolved issue: 'short-term rentals' matches both a citywide ordinance and one subdivision's area-plan amendment. EXAMPLES: { "q": "short-term rentals", "city": "lehi-ut" } — ALWAYS pass city with q { "issue_id": "<uuid>" }
    ConnectorAPI key
  • Find Malaysian land lots (JUPEM cadastre) by UPI, lot number or location. query takes a UPI (e.g. 1601400113193; dots, dashes and spaces allowed), a lot number ('Lot 3193', 'PT 1234') with negeri and optionally daerah, mukim and seksyen codes to narrow it, or coordinates as 'latitude, longitude' (e.g. 2.9264, 101.6964). With coordinates it returns the lots containing the point (distance 0), then the nearest within `radius` metres, closest first. To search an address, geocode it first; a radius of 25–100 m helps with geocoded points. Lots are only loaded for some states so far, so no result may just mean the state isn't loaded. Each lot has id (the UPI), negeri and negeriName, daerah, mukim (and mukimName where known), seksyen, lot, keluasan (m²) and bbox. Use MY_lot_get with an id for zoning and the boundary.
    ConnectorOAuth
  • Get the public parcel (property) record for one US parcel, located by exactly one of: lat+lng, street address (matched to the parcel's situs address nearby), parcel_id from an earlier result, or apn+state. Sibling tools: parcel_search finds many parcels by criteria and returns lighter records; start_run (kind=enrich) enriches up to 1000 parcels; parcel_coverage lists covered states and their columns. Output: parcel with owner of record and mailing address (null with privacy.reason where the source or state law withholds them), situs address, land use, zoning where published, assessed/land/improvement values, last sale, year built, legal description, acres, square feet, perimeter, centroid, bounding box and shape metrics; the GeoJSON boundary with include_geometry; point_fields computed at the centroid when fields or preset are given. Columns vary by state. Cost: 5 lookups per matched parcel plus 1 per started block of 50 point fields that return data; nothing when no parcel matches. Errors: invalid_locator (none or several locators), parcel_not_found (free; also outside covered states), fields_unknown, preset_unknown. Plan limits return rate_limited (with retry_after_s), daily_cap_reached or quota_exhausted.
    ConnectorAPI key
  • Report WHERE ONE OWNER HOLDS PROPERTY (portfelj, nepremicnine lastnika), by municipality and by what the property is for. INPUT: an `owner_id` from find_owner or institutional_owners, or a maticna stevilka. Optional `area` ref to list one municipality's parcels. READ: `parcels` — WHICH parcels (katastrska obcina, parcel number, area, zoning, share), largest first, with `n_parcels_matching`. Empty with `parcels_listed: false` for owners of more than 5,000 parcels. READ: `as_of` for `gurs_valuation` — ownership is GURS's quarterly extract, not the live land register: a parcel sold since still shows the SELLER. That is how a sold plot is found from its seller's name. NEVER: read the counts as values. A forest parcel and a city office each count as one, and a fractional stake counts as a whole property. For land, `n_holdings` is about twice `n_properties` because both GURS registers file each parcel. Use it for 'where does this company own things', never for 'what is their portfolio worth'.
    ConnectorOAuth
  • 依條件搜尋地籍:段名、段碼、地號、權屬、管理機關、所有權人、面積範圍、登記日期範圍。回傳 `{ total, returned, results[] }`,每筆含 `id`、`city`、`area`、`section`、`sectcode`、`landno`(如 392-6)、`landno_code`、`area_sqm`/`area_ping`、`perimeter_m`、`owner_type`、`manager`、`owner_name`、中心點 `center`、`bbox`;預設不含邊界多邊形(`include_geom=true` 才回 `geometry`)。已知地段地號要取單筆邊界請用 `land_boundary`。臺北市的權屬與公告現值/地價在本索引是 null,請改用 `search_taipei_parcel_attrs`。 涵蓋 19 個縣市(澎湖、金門、連江尚無資料)。未涵蓋的縣市回 `results: []` 加 `coverage` 與 `note`;其餘條件查無時回一句「找不到符合條件的地籍」(不是錯誤)。 **`city` 必填** —— 段碼在不同縣市會重複(`0421` 同時是新竹縣省道段、雲林縣崙內段、臺北市長安段三小段等 10 個縣市),段名也會(「中正段一小段」同時在臺北市與基隆市)。沒有縣市就指不出是哪一個地段。 `section` 在此工具是**模糊比對**(「平林段」找得到「平林段後番子坑小段」),與 `land_boundary` 的精確比對不同。 ⚠️ 新竹市與嘉義市的地籍資料沒有行政區欄位(來源未發布,無法補)。本工具**不會**自動重試:對這兩市帶 `area` 必定 0 筆,請省略 `area`,只用 `city` + `section`,或改用 `sectcode`(4 碼段碼,可在土地謄本上找到)。 ⚠️ 使用分區(zoning)與使用地類別(land_use)不開放篩選、也不在回應裡:它們是**非都市土地**的欄位(值域是特定農業區、一般農業區、鄉村區等;住宅區全國只有 52 筆),且代碼欄與中文名欄嚴重不對齊 —— 只看中文名會漏掉 84.4% 有分區資訊的地號。臺北的都市計畫分區請用 `taipei_zoning_at_landno`。
    ConnectorOAuth
  • Whether an address or point in Flanders is protected or listed heritage, and what that means for works and permits, from the Flemish heritage agency (Onroerend Erfgoed) via the public Mercator map service. Checks every legal designation at the point: protected monument, protected town or village view, protected landscape, protected archaeological site, transition zone, UNESCO core or buffer zone, fixed inventory of built or landscape heritage, fixed archaeological zone (archaeology note needed for smaller works), heritage landscape and area where no archaeology is expected (no archaeology note needed). Each comes with its name, id, date, the official decision link and what it means. Also the scientific inventory of built heritage (no legal effect), ratified archaeology notes at the point, protected monuments within 30 m, and the municipality (NIS code). Flanders only. Starts with key_facts. Checks one point, not a whole parcel; does not replace the permit procedure or give zoning (spatial plans). Examples: Is the building on Bruges' Markt protected heritage? → {"address":"Markt 1, 8000 Brugge"}; Is Leuven station a protected monument? → {"address":"Martelarenplein 20, 3000 Leuven"}; Which heritage rules apply at this point in Antwerp? → {"latitude":51.2194,"longitude":4.4025}.
    ConnectorNo auth
  • What the spatial plans say about an address or point in Flanders, from the Department of Environment's official planning data (Digitaal Stedenbouwkundige Informatie) via Mercator. Names the land-use zone that applies: the most detailed plan in force (municipal, provincial or regional spatial implementation plan, special or general plan of development, or the regional zoning plan), with its code, category, publication date and a link to its rules, and lists the plans underneath. Also overlays, building-line and expropriation plans, municipal and provincial urban-development regulations, plans and regulations still in procedure (with participation dates), and permit applications filed through the Omgevingsloket since 2017 (type, works, status, link; applicants not named). Includes the municipality (NIS code). Flanders only. Starts with key_facts. Checks one point; it is not the official planning certificate (stedenbouwkundig uittreksel) and does not interpret the plan rules for a project. For heritage designations use heritage_at_location. Examples: What may be built at this address in Leuven? → {"address":"Tiensesteenweg 150, 3001 Leuven"}; Which plan applies at Leuven station? → {"address":"Martelarenplein 20, 3000 Leuven"}; What is the zoning at this point in Ghent? → {"latitude":51.0543,"longitude":3.7174}.
    ConnectorNo auth
  • List the municipalities ZoningVerdict covers, with each pack's version, last-reviewed date, and resolve grade. Coverage is reviewed summaries of public zoning ordinances, for information purposes only. Start here when you do not have a street address; with an address, start with check_coverage.
    ConnectorNo auth
  • Resolve a street address to its municipality and, where a validated GIS path exists, its zoning district. Check coverage first; an unreliable municipality is refused before payment. When a district is returned, pass it to get_district_rules. The response discloses how the district was identified. Parcel boundaries and zoning lines can disagree near edges; confirm with the municipality before acting.
    ConnectorNo auth
  • List every named entity in the Decoder Index, the smallest citable unit of authority in the corpus. Returns the four-class taxonomy (Person / Organization / Legislation / CreativeWork) with class-specific summary fields (jobTitle for Person; jurisdiction for Organization / Legislation / Project; legal_status for Legislation; case_number + work_status for Project) plus cross-reference counts (meetings_count, briefs_count, watches_count, patterns_count) for each entity. Filter by entity_class, place (jurisdiction), or search substring. Use as the discovery surface for the entity graph; pair with describe_entity for full structured detail. Each entity's schema_id is a stable cross-page reference (`/entities/{slug}#{class.toLowerCase()}`) that resolves to the canonical Schema.org node (Person / Organization / Legislation / CreativeWork) for AI-citation grounding.
    ConnectorNo auth
  • Return meeting readings across all cities, optionally filtered by date range or jurisdiction substring. Same response shape as meeting_index but with no required parameters. Call with no args to get the full corpus, or pass a jurisdiction substring (e.g., "minneola") to filter by city without requiring an exact match. Use when you need to enumerate the full meeting record or scan across cities by date range.
    ConnectorNo auth