ToolMint Code Violations

City code-enforcement cases for a street address as clean agent JSON: open/closed status, case type, dates, result, coordinates and a link to the city record. Each city's dataset license is recorded and returned.

Routes and prices

Route	Price	What it does	Parameters (* required)
`GET /violations`	$0.01	Code-enforcement cases at an address in Austin, New Orleans, Seattle or Cincinnati	`city`, `address`, `status`, `since`, `limit`

Free routes: /, /health, /openapi.json, /.well-known/x402, /cities.

Try it

Live. Call it with no payment and you get 402 with a base64 PAYMENT-REQUIRED header carrying the exact price from the table; repeat with a PAYMENT-SIGNATURE header from any x402 client.

curl -i "https://toolmint-code-violations.toolmint.workers.dev/violations?city=austin&address=1904%20E%2022nd%20St"

Output (200)

violations[]: city, caseId, address, zip, status (open / closed / unknown), statusRaw, caseType, description, openedDate, closedDate, lastActivityDate, result, latitude/longitude, recordUrl.
Also returned: count, openCount, closedCount, truncated and summary (headline, latest opened date, distinct addresses).
provenance: dataset name and URL, the exact SODA apiUrl, license (name, URL, when and where it was checked), attribution, fetchedAt and contentSha256 of the raw upstream body.
disclaimer: public records, can lag, not an inspection or title report; property records, not consumer reports — do not use them for FCRA-covered decisions about individuals (tenant, credit, employment or insurance screening).

Errors are not charged

Payment settles only on a successful answer. These responses are never settled:

Status	Meaning (from the OpenAPI)	Charged?
`400`	Bad parameters (not charged)	No
`404`	No matching records (not charged)	No
`502`	City portal error (not charged)	No