How to Use Cincinnati code enforcement cases in dots
Returns Cincinnati enforcement cases, including violations, vacant building orders, zoning issues, and nuisance complaints. Use it to check recorded enforcement activity alongside a property's permit history.
Prompts to try with Cincinnati code enforcement cases in dots
Copy an example into dots, or ask in your own words.
Every Monday, use Cincinnati code enforcement cases to summarize zoning cases entered in Over-the-Rhine during the previous week. Separate the results by case category and status.
Every Monday at 9am: use Cincinnati code enforcement cases to look this up and give me the result as a table.
Pull the latest numbers from Cincinnati code enforcement cases and tell me what changed since last week.
Check Cincinnati code enforcement cases and summarize what you find in three bullet points.
Pull the newest data from Cincinnati code enforcement cases and give me the result as a table.
How to set up Cincinnati code enforcement cases in dots
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send dots this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Create an API key
In the console, open API keys and create a key for your dot. Copy it.
- Send your dot this message
Your dot reads Spiral's skill and asks for your API key.
set up https://spiral.ai/SKILL.md
- Give your dot the key
When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run Cincinnati code enforcement cases
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "data-cincinnati-oh-gov/building-permits/search_code_cases", "input": { "sort": "entered_desc" } }'
Then paste one of the prompts above: dots finds Cincinnati code enforcement cases on Spiral, shows the price and runs it.
Cincinnati code enforcement cases providers and prices
Spiral runs Cincinnati code enforcement cases through Alexandria. Open a card for today's price, with every fee included.
$0.00873 per call.
Settings you can ask for
Ask dots for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Sort | entered_desc or updated_desc | Order, newest first, missing values last. Defaults to entered_desc, or updated_desc when only updated_since is given. | |
| Limit | 1 to 100 | 25 | Records per page. |
Every API field of City of Cincinnati Open Data: building permits, contractors and code enforcement · Search code cases is on its tool page: open its card above.
What can you do with Cincinnati code enforcement cases in dots?
Maintain a recurring Cincinnati construction brief for commercial sites and business districts. Review permit and enforcement records on a schedule, then add contractor activity comparisons for the reporting period.
Prepare a commercial property brief
Find a commercial site's permits, inspect the relevant work items and contractors, and summarize recorded enforcement cases. Keep complaints and violations separate in the brief.
Write a business district construction report
Summarize permit activity in a Cincinnati business district, identify active contractor companies, and examine representative projects. Add an enforcement section that distinguishes complaints from violations.
Check a local development story
Find the permits behind a reported commercial redevelopment, inspect their work items, and check related enforcement records. Compare the contractor's recorded activity with other companies over the same period.
Maintain a commercial redevelopment watch
Review a defined set of commercial addresses on a schedule for permit and enforcement activity. Inspect relevant permits and add periodic contractor rankings to show the broader construction context.
Review a commercial site's enforcement timeline
Place recorded enforcement cases beside permit applications and issued permits for a commercial address. Read the work items before suggesting that a permit relates to a particular case.
Summarize neighborhood enforcement activity
Prepare neighborhood totals by recorded case category and status. Present complaints and violations separately so the report does not turn complaint volume into a count of confirmed violations.
More on Cincinnati code enforcement cases and dots
Overview
Cincinnati code enforcement cases in other agents
Questions about Cincinnati code enforcement cases in dots
Can dots use Cincinnati code enforcement cases?
Yes. Add Spiral to dots as an MCP server, and dots can find and run Cincinnati code enforcement cases like any built-in tool.
How much does Cincinnati code enforcement cases cost in dots?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.
Do I need an Alexandria account to use Cincinnati code enforcement cases in dots?
You need no Alexandria account. dots uses one Spiral API key for every tool, and Spiral runs Cincinnati code enforcement cases on its own Alexandria account.
How long does it take to set up Cincinnati code enforcement cases in dots?
About two minutes: create an API key, then send your dot this message, then give your dot the key.
Does dots wait while Cincinnati code enforcement cases runs?
Cincinnati code enforcement cases runs in the background. dots starts the run, checks on it and gives you the json when it's ready.
How far back does Cincinnati's online permit history go?
The city's published permit register covers applications since January 1, 2010. That date describes application history, so it should not be read as an issue-date cutoff.
How fresh are Cincinnati's permit and enforcement records?
Alexandria describes the Cincinnati data as reloaded daily. The city's enforcement catalog also specifies a daily refresh, rather than a continuous live feed.
Does code enforcement data include commercial properties?
Yes. Cincinnati explicitly includes complaints, inspections, and violations from both residential and commercial properties.
Does an enforcement complaint prove a violation occurred?
The city's inspection process is primarily complaint based, and its dataset includes complaints as well as violations. Keep those categories separate when describing a property's record.
Does contractor contact history start at the same time as permit history?
The published start dates differ: permit applications begin January 1, 2010, while the city describes contractor and subcontractor contacts as covering applications since January 2012. The contact description does not establish complete contact coverage for every permit.
Start using Cincinnati code enforcement cases in dots
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into dots:
set up https://spiral.ai/SKILL.md


