Spiral gives your agent every tool with one account. Browse the tools →

Grok · Listings

How to Use Cincinnati code enforcement cases in Grok

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 Grok

Copy an example into Grok, or ask in your own words.

Use Cincinnati code enforcement cases to summarize zoning cases entered in Over-the-Rhine during 2025. Separate complaints from violations in your explanation.

Cincinnati code enforcement casesGrok
Try asking
  • 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 Grok

Pick the way that suits you. Each takes about two minutes.

Use the Grok connector

  1. Add a custom connector

    In Grok open Settings › Connect Apps, then Add a custom connector. Name it Spiral, paste this URL, leave Headers empty and click Add MCP.

    https://api.spiral.ai/mcp
  2. Sign in to Spiral and approve

    Grok opens Spiral: sign in, pick the organization and click Authorize. Spiral gives the connection its own API key; Grok never sees it, and you can remove the connection under Settings › Connected apps.

  3. Check that it is connected

    Connect Apps › Custom shows Spiral as Connected. It works in every Grok chat and Grok bot.

Use the Spiral skill

  1. Send Grok this message

    Your agent reads Spiral's skill and sets itself up.

    set up https://spiral.ai/SKILL.md
  2. Sign in or paste a key

    Approve Spiral in the browser, or give the agent a key from the console.

Use the Spiral CLI

  1. 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

  1. Create an API key

    In the console, under API keys.

  2. 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: Grok 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.

AlexandriaListings

Settings you can ask for

Ask Grok for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Sortentered_desc or updated_desc

Order, newest first, missing values last. Defaults to entered_desc, or updated_desc when only updated_since is given.

Limit1 to 10025

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 Grok?

Prepare a Cincinnati construction brief with specific projects, contractor activity, and enforcement context. Ask follow-up questions about a permit's work items or distinguish complaints from recorded violations.

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.

Questions about Cincinnati code enforcement cases in Grok

Can Grok use Cincinnati code enforcement cases?

Yes. Add Spiral to Grok as an MCP server, and Grok can find and run Cincinnati code enforcement cases like any built-in tool.

How much does Cincinnati code enforcement cases cost in Grok?

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Grok plan is separate.

Do I need an Alexandria account to use Cincinnati code enforcement cases in Grok?

No. Spiral runs Cincinnati code enforcement cases on its own Alexandria account. You sign in to Spiral once and never paste a key.

How long does it take to set up Cincinnati code enforcement cases in Grok?

About two minutes: add a custom connector, then sign in to Spiral and approve, then check that it is connected.

Does Grok wait while Cincinnati code enforcement cases runs?

Cincinnati code enforcement cases runs in the background. Grok 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.

Get started

Start using Cincinnati code enforcement cases in Grok

One Spiral account for every tool your agent needs. No subscription; you pay per run.

Paste this into Grok:

Set up Grok

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options