How to get property tax records programmatically

Resolve the property account

Start with a DC SSL or a complete street address. Quoin resolves exact identifiers and normalized addresses first. Fuzzy suggestions appear only after exact resolution fails and do not include collateral property facts.

Keep the returned account identifier with later calls. An address can describe a building while the tax system contains separate condominium, possessory-interest, or related accounts.

Request a bounded record

Use the authenticated MCP tool get_tax_and_balance_history for tax and balance fields. Use get_assessment_history for the assessment stages carried in the current official extract. The MCP is available now; API access is by request.

Treat monetary values, dates, tax years, status values, and null meanings as typed fields. Do not replace missing values with zero or combine prior, current, and proposed stages.

Retain the source evidence

Normal sourced responses include developer provenance and display-ready source routes. A client can also pass returned opaque source references to get_source_evidence for validation and expansion.

Show the official portal, SSL or address input, covered fields, and verification steps beside the answer. The live portal may be newer than the frozen release.

Minimum implementation checks

• Reject a request that does not resolve to the intended account.
• Keep the tax year and assessment stage with each value.
• Preserve source, quality, and link-scope flags.
• Handle an empty result as no linked record in the served release.
• Never present the response as legal, title, zoning, or appraisal advice.