API and MCP
The index, in your own tools.
One REST API and one MCP server, both reading the same public registry. Use them from a CRM, a spreadsheet, a script, or an AI agent.
MCP server
Eight tools, one command
Add the server to Claude Desktop, Claude Code or any MCP compatible client. Every result carries its SpecIndex ID and public source link. Parameters marked * are required; the lists below are the connector's own schema.
claude mcp add -s user --transport http specindex https://specindex-api-gmm6irqe4q-uc.a.run.app/mcp
find_brand_positions
For a brand, return every specification section that names it, as basis of design or approved equal, with the division, the sentence that names it and the source page.
announced_within_days, bid_due_within_days, brand*, county, division, include, limit, offset, openness, role, state, still_open
project_positions
Every brand position on one project, grouped by CSI division and role, with the document and page for each.
project_id*
find_displacement
Projects where a brand may substitute into a section whose basis of design belongs to a rival, both positions cited to the same document.
announced_within_days, bid_due_within_days, brand*, county, division, limit, offset, openness, rival_brands, role, state, still_open
search_projects
Find commercial construction projects by state, county, city, metro code (CBSA), status, project type, announcement window and minimum value, or look up one project by name, address, postal code, parcel ID or source record ID. A county requires its state.
address, announced_within_days, cbsa_code, city, county, has_address, limit, min_value_usd, offset, parcel_id, postal_code, project_type, query, skip_total, slim, source_record_id, state, status
compare_brands
Two or more manufacturers head to head in one CSI division and territory: basis of design, approved equal, and sections named.
brands*, county, division, state
coverage_report
How many public bid documents SpecIndex has searched for a state or county, and how many projects have at least one. It takes a state and a county only, and answers what the index covers, not what exists.
county, state
get_project
One complete project record by project ID: location, scope, parties, source links, documents held and dated stage evidence.
project_id*
match_projects
Batch coverage check: for up to 50 projects you already know about, say which ones SpecIndex holds and with what evidence.
include, max_candidates, projects*
REST API
Resources
Bearer token auth. JSON responses. Rate limits and pagination follow the conventions page in the docs.
| Resource | What it does | License |
|---|---|---|
| /projects | Search and fetch projects, by ID or by filter | Free, rate limited |
| /brands | Brand positions, competitor comparison | Brand or Territory |
| /coverage | Coverage by state, metro and source | Free |
| /alerts | Create and manage territory and division digests | Territory |
Building an agent on construction data?
Tell us what you are wiring up and we will get you a key.