Integrations

Three ways to connect your organization's systems to Pierre Review: a REST API for dashboards and internal tools, an MCP server for AI assistants, and single sign-on through your identity provider.

REST API

Versioned JSON API at https://pierrereview.com/api/v1. Public legislative data requires no key and is rate-limited to 60 requests/minute and 1,000/hour per IP. Responses are cacheable JSON with CORS enabled, refreshed by the data pipeline throughout the day.

# Public data — no key required
curl "https://pierrereview.com/api/v1/2026/bills?stage=floor&chamber=House"

# Workspace data — bearer token from the auth flow
curl -H "Authorization: Bearer <token>" "https://pierrereview.com/api/v1/workspace"

Public data endpoints

GET /api/v1/sessions

Legislative sessions the API can serve

GET /api/v1/{year}/bills?stage=&chamber=&issue=&q=&page=&per_page=

Bill list with filters and pagination

GET /api/v1/{year}/bills/{bill}

One bill: status, stage, sponsors, actions, AI summary

GET /api/v1/{year}/bills/{bill}/votes

Recorded votes on a bill

GET /api/v1/{year}/bills/{bill}/whip

Floor-vote prediction (whip count)

GET /api/v1/{year}/legislators?chamber=&party=

Legislator directory

GET /api/v1/{year}/legislators/{id}

One legislator: profile, committees, stats

GET /api/v1/{year}/legislators/{id}/votes

A legislator’s vote history

GET /api/v1/{year}/legislators/{id}/bills

Bills a legislator sponsors

GET /api/v1/{year}/search?q=&limit=

Full-text search across bills and legislators

GET /api/v1/{year}/activity?limit=&since=

Recent legislative activity feed

GET /api/v1/{year}/hearings/today

Today’s committee hearings

GET /api/v1/{year}/stats

Session-level statistics

Authenticated endpoints

Workspace data (paid plans) uses a bearer session token: request a one-time code by email, verify it, then send Authorization: Bearer <token> on subsequent calls. Tokens are revocable server-side and renew with use.

POST /api/v1/auth/request

Email a one-time sign-in code ({ "email": "..." })

POST /api/v1/auth/verify

Exchange the code for a bearer session token

DELETE /api/v1/auth/session

Revoke the current token (sign out)

GET /api/v1/workspace

Your org’s watchlists, tracked bills, and alert subscriptions

MCP server (AI assistants)

Claude, ChatGPT, Cursor, and any other client that speaks the Model Context Protocol can query live South Dakota legislative data — bills, votes, hearings, legislators, vote predictions — with every answer citing pierrereview.com. The endpoint is public and free:

https://pierrereview.com/api/mcp

Client setup snippets, the full tool list, and example prompts are on the MCP server page.

Single sign-on (enterprise)

Enterprise workspaces can sign in through their organization's identity provider instead of (or alongside) email magic links:

Microsoft Entra ID (Azure AD) — OpenID Connect. If your tenant enforces Duo MFA through Conditional Access, that policy applies automatically.
Duo SSO — direct OpenID Connect integration for organizations using Duo as their primary identity provider.

Accounts are matched by your organization-verified email address, so existing invited members keep their workspace, role, and history. To enable SSO for your workspace, contact [email protected] — setup on your side is a standard app registration; we'll send your IT team a one-page guide with the redirect URI and required claims.

Data practices

Legislative data served by the API and MCP server is public record. Workspace data (watchlists, notes, positions) is tenant-isolated with database row-level security and never appears on unauthenticated surfaces. See our privacy policy for details.