[Integrations](https://spiral.ai/integrations) › [Cursor](https://spiral.ai/integrations/cursor) › [San José contractor permit activity](https://spiral.ai/integrations/cursor/san-jos-contractor-permit-activity)

# How to Use San José contractor permit activity in Cursor

Returns contractors ranked by permit count or total permit valuation in San José's published records. Use it to compare firms' recorded activity before examining their individual projects.

|  |  |
| --- | --- |
| Model | San José contractor permit activity |
| 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 San José contractor permit activity in Cursor

- Use San José contractor permit activity to compare Devcon's recorded permits issued in 2026 and add a table of permit counts and valuations to the report.
- Use San José contractor permit activity to compare solar contractors in ZIP code 95131 for permits issued in 2026 and add the results to the market analysis.
- Use San José contractor permit activity to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from San José contractor permit activity and tell me what changed since last week.
- Check San José contractor permit activity and summarize what you find in three bullet points.

## How to set up San José contractor permit activity in Cursor

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

### Use Spiral's MCP server

1. **Add the hosted server**: Use Add to Cursor on the console's Agents & MCP page, or add this to `.cursor/mcp.json` (one project) or `~/.cursor/mcp.json` (every project):

```json
{
  "mcpServers": {
    "spiral": { "url": "https://api.spiral.ai/mcp" }
  }
}
```

2. **Sign in**: Open Cursor Settings › MCP, click Connect next to spiral, sign in to Spiral and click Authorize. No API key. Spiral then shows as connected, with its tools listed.

### Use the Spiral skill

1. **Send Cursor 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 San José contractor permit activity**: 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-sanjoseca-gov/building-permits/contractor_activity",
    "input": {
      "issued_since": "<issued_since>"
    }
  }'
```

Then paste one of the prompts above: Cursor finds San José contractor permit activity on Spiral, shows the price and runs it.

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

## San José contractor permit activity tools and prices

- [San José Open Data: building and planning permits (data.sanjoseca.gov) · Contractor activity](https://spiral.ai/tools/alexandria/data-sanjoseca-gov/building-permits/contractor_activity) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| zip |  | — | 5-digit ZIP code (95131). Pattern: ^[0-9]{5}$. |
| sort | permits_desc, valuation_desc | permits_desc | permits_desc: most permits first; valuation_desc: largest total declared valuation first. |
| 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 | any, active, under_inspection, expired, issued_last_30_days | any | Which published list to read. any (default): Active, Expired and permits issued in the last 30 days, each permit once, in one request. active: issued and not finaled or expired (includes under inspection); under_inspection: active permits with inspections under way; expired; issued_last_30_days: every permit issued in the last 30 days whatever its state, the list to poll for new permits. Finaled permits older than 30 days are not published. |
| contractor |  | — | Case-insensitive substring of the contractor as published, to size one firm (Devcon, Sunrun). |

## What can you do with San José contractor permit activity in Cursor?

Build a San José construction report that connects contractor totals to individual permit records. A coding agent can add those results to project files while labeling the gaps in completed permit history.

### Compare commercial contractors

Rank firms by recorded permit activity, identify their commercial projects, and examine selected permits. Keep the comparison limited to work present in the published lists.

### Research solar installation activity

Compare solar contractors' recorded activity, find the underlying permits, and review individual records for projects of interest.

### Assess tenant improvement demand

Find tenant improvement permits, compare the contractors associated with that work, and inspect selected commercial project records for a market brief.

### Review expired commercial permits

Compare firms' recorded expired permit activity, locate the commercial projects behind the totals, and examine individual records before requesting clarification from the city.

## Overview

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

## San José contractor permit activity in other agents

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

## More Cursor guides

- [San José building permit search](https://spiral.ai/integrations/cursor/san-jos-building-permit-search)
- [San José planning permit search](https://spiral.ai/integrations/cursor/san-jos-planning-permit-search)
- [San José building permit details](https://spiral.ai/integrations/cursor/san-jos-building-permit-details)
- [StreetEasy building details](https://spiral.ai/integrations/cursor/streeteasy-building-details)
- [San Francisco contractor permit activity](https://spiral.ai/integrations/cursor/san-francisco-contractor-permit-activity)
- [StreetEasy rental details](https://spiral.ai/integrations/cursor/streeteasy-rental-details)

## Questions about San José contractor permit activity in Cursor

**Can Cursor use San José contractor permit activity?**

Yes. Add Spiral to Cursor as an MCP server, and Cursor can find and run San José contractor permit activity like any built-in tool.

**How much does San José contractor permit activity cost in Cursor?**

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

**Do I need an Alexandria account to use San José contractor permit activity in Cursor?**

No. Spiral runs San José contractor permit activity on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up San José contractor permit activity in Cursor?**

About two minutes: add the hosted server, then sign in.

**Does Cursor wait while San José contractor permit activity runs?**

San José contractor permit activity runs in the background. Cursor starts the run, checks on it and gives you the json when it's ready.

**Does this cover all of Santa Clara County?**

The source covers City of San José permits. It does not provide a countywide inventory of permits from other jurisdictions.

**How often does the permit data change?**

The building permit files update daily. Searches and contractor totals reflect those daily snapshots rather than a continuous record of changes.

**Can I get a complete historical permit record?**

Completed building permits issued more than 30 days ago are not published in these lists. Historical searches and contractor totals therefore omit completed work outside that window.

**Can these records tell me how long permit approval took?**

The building permit files have no application date. They cannot establish the elapsed time between application and issuance.

**Can I reuse the published permit data commercially?**

The building permit datasets are published under CCZero. CC0 allows copying, modification and distribution, including commercial reuse, without requesting permission.

