How to give an AI agent access to property records

Use a constrained interface

Quoin exposes read-only MCP tools for defined property tasks. The authenticated endpoint does not give the model arbitrary SQL or direct table access. Each tool has bounded inputs and output limits.

The public catalog includes property resolution, complete records, assessments, taxes, sales, permits, licenses, inspection and enforcement history, building and land profiles, search, and source evidence.

Resolve identity before facts

An agent should call resolve_property before making a property claim. Exact SSL and normalized address matches take priority. If resolution returns suggestions, the agent should ask the user to choose rather than attach facts to an uncertain match.

Batch resolution is limited to caller-named assets. Property search uses allowlisted filters and excludes owner-name search and mailing-address output.

Keep evidence in the answer

The agent should retain source references, dates, quality flags, and property-link scope. A visible Source or Verify action should use the human verification route instead of exposing machine or session-bound URLs.

When a record is contextual, the answer must say so. When a tool returns no linked record, the answer must not claim that the public record does not exist.

Set answer boundaries

• Do not infer title, lien priority, ownership, zoning compliance, or market value.
• Do not turn a permit into proof that work was completed.
• Do not turn a license at an address into proof of ownership or occupancy.
• State that current coverage is Washington, DC.
• Use the authenticated MCP now or request API access.