The library behind the Public Records section is now available outside the dashboard, with the same records and the same citations whether a script or an AI agent is calling.
Five operations, twice
| What you want | REST | MCP tool |
|---|---|---|
| Browse the library by state, topic or free text | GET /v1/data/library | list_public_record_sources |
| Which sources cover an address (nothing fetched) | GET /v1/data/library/resolve | resolve_public_record_sources |
| Raw records from one source near an address | GET /v1/data/library/{source_id} | query_public_record_source |
| Ask a question; the agent reads every matching source | GET /v1/data/library/ask | ask_public_records |
| Search records the library has already fetched | GET /v1/data/library/search | search_public_records |
- Resolve first, then fetch. Resolve returns the geocode and the ranked sources an ask would read, without fetching anything, so an agent can check coverage before spending a longer call.
- One source, no model. The per-source call returns the publisher's rows exactly as returned, newest first, with one citation per record and a hash over the set.
- Ask returns the raw records, citations and coverage alongside an answer that may only cite rows that exist.
- Free while in preview. Reading the library costs no credits; normal API rate limits apply.
Keys are issued under Settings → Developer on paid plans. Reference in the API docs and the MCP guide; walkthrough in the help center at Query Relm Data by API or MCP.