[Integrations](https://spiral.ai/integrations) › [Grok](https://spiral.ai/integrations/grok) › [Pittsburgh code violations](https://spiral.ai/integrations/grok/pittsburgh-code-violations)

# How to Use Pittsburgh code violations in Grok

Retrieve Pittsburgh enforcement records with investigation findings, cited code sections, and case status. Use this to reconstruct a case history; use Pittsburgh condemned properties for condemnation records and latest inspection results.

|  |  |
| --- | --- |
| Model | Pittsburgh code violations |
| Available through | Alexandria |
| Category | Listings |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with Pittsburgh code violations in Grok

- Use Pittsburgh code violations to find Hazelwood enforcement records and summarize the recorded findings by case.
- Use Pittsburgh code violations to review South Side Flats records and explain the recorded case statuses.
- Use Pittsburgh code violations to look this up and give me the result as a table.
- Pull the latest numbers from Pittsburgh code violations and tell me what changed since last week.
- Check Pittsburgh code violations and summarize what you find in three bullet points.

## How to set up Pittsburgh code violations 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.

```text
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.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run Pittsburgh code violations**: One request; the result comes back by polling or a webhook.

```bash
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-wprdc-org/code-enforcement/search_violations",
    "input": {
      "sort": "investigated_desc"
    }
  }'
```

Then paste one of the prompts above: Grok finds Pittsburgh code violations on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/grok

## Pittsburgh code violations tools and prices

- [WPRDC (data.wprdc.org): Pittsburgh permits, code violations, condemnations and contractor licences · Search violations](https://spiral.ai/tools/alexandria/data-wprdc-org/code-enforcement/search_violations) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| sort | investigated_desc, investigated_asc | investigated_desc | investigated_desc: newest investigation first; investigated_asc: oldest first (a case's history in order). Rows without an investigation date come last. |
| limit | 1 to 100 | 25 | Rows per page. |
| cursor |  | — | next_cursor from the previous page; repeat the same filters with it. Pattern: ^[0-9]+$. |
| status |  | — | Case-insensitive word match: every word must start a word of the column (prefix), in any order of the case status: under investigation, in violation, in court, closed. |
| address |  | — | Case-insensitive word match: every word must start a word of the column (prefix), in any order. Street line only (1815 Lowrie St, 56 South 12th Street); text after a comma is ignored and Street, Avenue, Road, Drive, North, South and similar become the city's abbreviations (ST, AVE, RD, DR, N, S). |
| outcome |  | — | Case-insensitive word match: every word must start a word of the column (prefix), in any order of the investigation outcome: violation found, no violation found, violation resolved, taking case to court. |

## What can you do with Pittsburgh code violations in Grok?

Produce a neighborhood brief with Pittsburgh property locations and recorded inspection or enforcement findings. Explain the returned records in plain English while distinguishing a latest inspection from a case history.

### Neighborhood property-condition brief

Prepare a Homewood briefing that separates condemnation records from enforcement cases and reports distinct parcels.

### Commercial site review

Check a proposed Pittsburgh business location for condemnation records and recorded enforcement activity before requesting a fuller property review.

### Community planning map

Map returned property locations for a Beltzhoover planning meeting, keeping condemnation results and enforcement cases clearly labeled.

### Public-data change digest

Compare successive neighborhood searches and summarize newly appearing records and changes to previously returned records.

### Redevelopment research shortlist

Attach condemnation and enforcement findings to a Pittsburgh redevelopment shortlist so researchers can identify parcels needing further review.

### Neighborhood reporting research

Build a source-backed reporting brief on property conditions in Hazelwood, separating inspection results from enforcement findings.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Grok guides](https://spiral.ai/integrations/grok)

## Pittsburgh code violations in other agents

- [Amp](https://spiral.ai/integrations/amp/pittsburgh-code-violations)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/pittsburgh-code-violations)
- [Claude](https://spiral.ai/integrations/claude-desktop/pittsburgh-code-violations)
- [Claude Code](https://spiral.ai/integrations/claude-code/pittsburgh-code-violations)
- [Cline](https://spiral.ai/integrations/cline/pittsburgh-code-violations)
- [Codex](https://spiral.ai/integrations/codex/pittsburgh-code-violations)
- [Cursor](https://spiral.ai/integrations/cursor/pittsburgh-code-violations)
- [Devin](https://spiral.ai/integrations/devin/pittsburgh-code-violations)
- [dots](https://spiral.ai/integrations/dots/pittsburgh-code-violations)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/pittsburgh-code-violations)
- [Gemini](https://spiral.ai/integrations/gemini/pittsburgh-code-violations)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/pittsburgh-code-violations)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/pittsburgh-code-violations)
- [goose](https://spiral.ai/integrations/goose/pittsburgh-code-violations)
- [Grok Build](https://spiral.ai/integrations/grok-build/pittsburgh-code-violations)
- [Hermes](https://spiral.ai/integrations/hermes/pittsburgh-code-violations)
- [Instinct](https://spiral.ai/integrations/instinct/pittsburgh-code-violations)
- [Manus](https://spiral.ai/integrations/manus/pittsburgh-code-violations)
- [Muse](https://spiral.ai/integrations/muse/pittsburgh-code-violations)
- [Muse Code](https://spiral.ai/integrations/muse-code/pittsburgh-code-violations)
- [n8n](https://spiral.ai/integrations/n8n/pittsburgh-code-violations)
- [Notion](https://spiral.ai/integrations/notion/pittsburgh-code-violations)
- [OpenClaw](https://spiral.ai/integrations/openclaw/pittsburgh-code-violations)
- [opencode](https://spiral.ai/integrations/opencode/pittsburgh-code-violations)
- [Perplexity](https://spiral.ai/integrations/perplexity/pittsburgh-code-violations)
- [Raycast](https://spiral.ai/integrations/raycast/pittsburgh-code-violations)
- [VS Code](https://spiral.ai/integrations/vscode/pittsburgh-code-violations)
- [Windsurf](https://spiral.ai/integrations/windsurf/pittsburgh-code-violations)
- [Zapier](https://spiral.ai/integrations/zapier/pittsburgh-code-violations)

## More Grok guides

- [Oregon contractor search](https://spiral.ai/integrations/grok/oregon-contractor-search)
- [Pittsburgh condemned properties](https://spiral.ai/integrations/grok/pittsburgh-condemned-properties)
- [Oregon contractor license details](https://spiral.ai/integrations/grok/oregon-contractor-license-details)
- [Pittsburgh contractor license details](https://spiral.ai/integrations/grok/pittsburgh-contractor-license-details)
- [OpenAddresses source status](https://spiral.ai/integrations/grok/openaddresses-source-status)
- [Pittsburgh contractor license search](https://spiral.ai/integrations/grok/pittsburgh-contractor-license-search)

## Questions about Pittsburgh code violations in Grok

**Can Grok use Pittsburgh code violations?**

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

**How much does Pittsburgh code violations 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 Pittsburgh code violations in Grok?**

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

**How long does it take to set up Pittsburgh code violations 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 Pittsburgh code violations runs?**

Pittsburgh code violations runs in the background. Grok starts the run, checks on it and gives you the json when it's ready.

**Does this cover all of Allegheny County?**

These are City of Pittsburgh condemnation and enforcement records. An Allegheny County parcel identifier in a record does not make the dataset countywide.

**How often does WPRDC publish updates?**

Both datasets list daily data changes and daily publishing. That is a publishing schedule, not a promise that every property receives a new inspection each day.

**Can I count rows to count properties?**

No. WPRDC flags duplicate parcel records in the condemnation data; enforcement records also describe case activity rather than a simple property inventory.

**Does a latest inspection result provide the whole property history?**

The condemnation data describes the latest inspection, including its pass or fail result. The violations data serves a different purpose: investigating recorded enforcement cases.

**How far back does Pittsburgh's violations data go?**

The current violations resource covers June 2020 onward. WPRDC publishes October 2015 through May 2020 separately as historical PLI data, so that older period should not be assumed to appear in a current search.

