Relm API + MCP.

Explore

The public record, read at the source.

Relm Data is a library of 10,500+ municipal, county and state open-data sources across 48 Northeast, Southwest, Southeast, Northwest, South, Great Lakes and Midwest states — permits, certificates of occupancy, fire, violations, inspections, complaints and zoning. Ask about an address and Relm queries every source that covers it, keeps the raw records, and answers from those records only, with a citation on each one.

Key Capabilities

10,500+ address-queryable sources from 2237 government publishers
48 states, 974 municipalities and counties
Permits, certificates of occupancy, fire, violations, inspections, complaints, zoning
Every record kept raw, hashed and cited back to the portal that published it
Runs inside every Intel Report as the public-records step
Same records by REST API, by MCP for AI agents, or one source at a time
Coverage

Where the library reaches today

Every figure here is generated from the source catalog and the latest live sweep, dated 2026-10-29. Counts are sources, not records — one source can hold millions of rows. Full regional coverage overview.

10,525
sources queryable by address
15,196
sources catalogued
2,237
government publishers
48
states
974
municipalities & counties
97%
of queried sources answered in the last sweep
  • California3,307
  • New York1,428
  • Texas1,304
  • Washington1,125
  • Maryland733
  • Virginia703
  • Illinois653
  • Florida543
  • Arizona473
  • Minnesota344
  • Pennsylvania343
  • Massachusetts333
  • Oregon304
  • Georgia292
  • Louisiana276
  • Ohio223
  • Indiana217
  • Missouri216
  • Michigan204
  • Wisconsin194
  • North Carolina174
  • Connecticut172
  • Tennessee168
  • Hawaii153
  • New Jersey107
  • Utah103
  • South Carolina95
  • Iowa85
  • Delaware77
  • Vermont71
  • Montana69
  • Kansas66
  • New Mexico66
  • Rhode Island66
  • Alabama61
  • Idaho51
  • Oklahoma47
  • Nebraska46
  • Kentucky41
  • New Hampshire40
  • Alaska36
  • West Virginia33
  • North Dakota30
  • Maine29
  • Arkansas26
  • South Dakota24
  • Wyoming24
  • Mississippi21
Alaska: 36 sources from 16 publishersAK36Maine: 29 sources from 13 publishersME29Vermont: 71 sources from 10 publishersVT71New Hampshire: 40 sources from 15 publishersNH40Washington: 1,125 sources from 92 publishersWA1,125Idaho: 51 sources from 33 publishersID51Montana: 69 sources from 19 publishersMT69North Dakota: 30 sources from 12 publishersND30Minnesota: 344 sources from 63 publishersMN344Illinois: 653 sources from 92 publishersIL653Wisconsin: 194 sources from 74 publishersWI194Michigan: 204 sources from 44 publishersMI204New York: 1,428 sources from 81 publishersNY1,428Rhode Island: 66 sources from 19 publishersRI66Massachusetts: 333 sources from 63 publishersMA333Oregon: 304 sources from 40 publishersOR304Nevada · Southwest region · not yet coveredNVWyoming: 24 sources from 15 publishersWY24South Dakota: 24 sources from 12 publishersSD24Iowa: 85 sources from 35 publishersIA85Indiana: 217 sources from 51 publishersIN217Ohio: 223 sources from 82 publishersOH223Pennsylvania: 343 sources from 67 publishersPA343New Jersey: 107 sources from 43 publishersNJ107Connecticut: 172 sources from 24 publishersCT172California: 3,307 sources from 334 publishersCA3,307Utah: 103 sources from 46 publishersUT103Colorado · Midwest region · not yet coveredCONebraska: 46 sources from 20 publishersNE46Missouri: 216 sources from 38 publishersMO216Kentucky: 41 sources from 19 publishersKY41West Virginia: 33 sources from 9 publishersWV33Virginia: 703 sources from 93 publishersVA703Maryland: 733 sources from 59 publishersMD733Delaware: 77 sources from 8 publishersDE77Arizona: 473 sources from 47 publishersAZ473New Mexico: 66 sources from 24 publishersNM66Kansas: 66 sources from 35 publishersKS66Arkansas: 26 sources from 20 publishersAR26Tennessee: 168 sources from 34 publishersTN168North Carolina: 174 sources from 57 publishersNC174South Carolina: 95 sources from 40 publishersSC95Oklahoma: 47 sources from 25 publishersOK47Louisiana: 276 sources from 17 publishersLA276Mississippi: 21 sources from 10 publishersMS21Alabama: 61 sources from 26 publishersAL61Georgia: 292 sources from 81 publishersGA292Hawaii: 153 sources from 23 publishersHI153Texas: 1,304 sources from 188 publishersTX1,304Florida: 543 sources from 115 publishersFL543
under 100100 – 299300 – 9991,000+sources per statenot yet covered

By region

  • NortheastLive · 11 states
    ME · NH · VT · MA · RI · CT · NY · PA · NJ · DE · MD
  • SouthwestLive in 6 of 7 states
    CA · NV · UT · AZ · NM · AK · HI
  • SoutheastLive · 10 states
    KY · TN · MS · AL · GA · FL · SC · NC · VA · WV
  • NorthwestLive · 5 states
    WA · OR · ID · MT · WY
  • SouthLive · 4 states
    TX · OK · AR · LA
  • Great LakesLive · 5 states
    WI · MI · IL · IN · OH
  • MidwestLive in 7 of 8 states
    ND · SD · NE · KS · MN · IA · MO · CO
Categories

What an ask reads, and what else is on the shelf

Seven topics are asked by default — the ones that decide whether a building is what the listing says it is. The rest of the catalog is browsable and queryable one source at a time.

Asked by default

  • Building permits1,387 sources
  • Certificates of occupancy30 sources
  • Fire incidents & inspections871 sources
  • Code violations522 sources
  • Inspections397 sources
  • 311 & complaints282 sources
  • Zoning & land use934 sources

Also in the library

  • Assessments1,158
  • Housing & rent registration936
  • Transportation639
  • Crime & public safety636
  • Parcels574
  • Flood zones507
  • Environmental420
  • Licenses357
  • Health315
  • Utilities298
  • Energy & benchmarking247
  • Property tax247
  • Evictions221
  • Procurement notices (RFPs, bids, awards)115
  • Other municipal datasets4,103
A few of the sources

Read from the portal that publishes it

A handful of the sources behind the numbers. Each one is queried on the publisher's own open-data portal, and every record Relm returns links back to it.

Access

In the app, by API, or by an agent

The same library behind every Intel Report is exposed as eight REST endpoints and eight MCP tools. Both are read-scope operations. Browsing the library is free; pulling records costs 2 credits per call (per source answered in a batch) and an ask 20.

MCP — for AI agents
Tools on https://api.relm.ai/mcp/
// Any MCP client connected to https://api.relm.ai/mcp/
resolve_public_record_sources({
  "address": "350 5th Ave, New York, NY 10118",
  "topics": "permits,violations"
})
// → sources covering the address, ranked city > county > state

ask_public_records({
  "question": "Any open permits or violations?",
  "address": "350 5th Ave, New York, NY 10118"
})
// → answer + raw records + one citation per record + coverage
REST — resolve, then call one source
GET https://api.relm.ai/v1/data/library/…
# Which sources cover the address (nothing fetched)
curl "https://api.relm.ai/v1/data/library/resolve?address=350+5th+Ave,+New+York,+NY+10118" \
  -H "Authorization: Bearer relm_sk_..."

# Raw records from ONE source, with citations
curl "https://api.relm.ai/v1/data/library/f16b07e62fe12d3a?address=350+5th+Ave,+New+York,+NY+10118&limit=25" \
  -H "Authorization: Bearer relm_sk_..."

The eight operations: browse the library, read a source’s catalog entry, resolve which sources cover an address, pull raw records from one source or up to ten at once, ask a question across every matching source, ask about a whole city or county, and search records already fetched. Full reference in the API docs and the MCP server guide.

How an ask works.

Give Relm an address and a question. Four things happen, in order:

  • Resolve: the address is geocoded and matched to the sources whose publisher covers it — city first, then county, then state — for the topics you asked about
  • Fetch: each source is queried directly on its own portal, by point-and-radius where the dataset has a location, by street address where it does not; personal fields are dropped before anything is stored
  • Cache: the rows land in a shared record cache with a per-topic freshness window, so the next ask about the same address is answered from records already fetched
  • Answer: the data agent writes its answer from the fetched records only and may cite nothing that is not in them; the raw records, a hash over them and a coverage report travel with every answer

A source that could not be reached is reported as exactly that — never as "nothing found".

Inside every Intel Report.

Relm Data is the public-records step of an Intel Report. When the agents brief a property, this step asks the library about open permits, certificates of occupancy, code violations, fire incidents, inspections, complaints and zoning for the address, and the findings land in the report with the same citations you would get calling the library yourself. Teams can add their own notes and corrections on top of the records; the raw rows stay untouched underneath, with version history.

Built for agents as much as for people.

Every library capability is available three ways. In the app, through an Intel Report. Over the REST API, as the /v1/data/library endpoints. And over the Relm MCP server, as five tools an AI agent can call directly: browse the library, resolve which sources cover an address, pull raw records from one source, ask a question across all of them, or search records already fetched. The REST and MCP surfaces share one implementation and one set of docs, so what an agent sees is exactly what the API returns.

Honest about coverage.

The library is swept against sample addresses in every state, and the sweep is what keeps it honest: a source whose endpoint has gone dark is marked unreachable and skipped, a portal that changed shape fails a scheduled check rather than silently returning nothing, and the coverage figures on this page are generated from the catalog and the latest sweep rather than typed by hand. Today the library covers the Northeast, Southwest, Southeast, Northwest, South, Great Lakes and Midwest; coverage grows one publisher at a time, and each one is verified live before it is added.

Related Features

See Relm Data in Action

Start your first property analysis and experience how Relm Pro transforms underwriting.