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. API and MCP access are part of Pierre Review Enterprise.
The REST API and the MCP server both authenticate with an API key that belongs to your organization. Admins of an Enterprise organization create and revoke keys under Workspace → Settings, and an organization can hold up to 10 active keys, for example one per tool or team. A key is shown once, when it's created. We store only a hash of it, so a lost key can't be recovered: revoke it and create another. Send the key with every request:
Authorization: Bearer pr_live_YOUR_KEYA mistyped or revoked key gets HTTP 401, as does any MCP request without a key. A revoked key stops working on its next request. When an organization leaves Enterprise, all of its keys are revoked, and they stay revoked if it returns, so it creates new ones. Not on Enterprise yet? Talk to us.
Versioned JSON API at https://pierrereview.com/api/v1, refreshed by the data pipeline throughout the day. Requests with your API key are rate-limited per key to 600 requests/minute and 20,000/hour, with HTTP 429 and Retry-After past that. Responses are cacheable JSON with CORS enabled. These endpoints also serve pierrereview.com's own pages and mobile app, under a much lower per-IP limit that isn't meant for integrations.
curl -H "Authorization: Bearer $PIERRE_API_KEY" \
"https://pierrereview.com/api/v1/2026/bills?stage=floor&chamber=House"Workspace data (paid plans) is read as a signed-in member, not with an API key: request a one-time code by email, verify it, then send the session token it returns as Authorization: Bearer <token>. This is the sign-in the Pierre Review mobile app uses. Tokens are revocable server-side and renew with use.
Claude Code, Claude Desktop, Cursor and other clients that speak the Model Context Protocol can query live South Dakota legislative data (bills, votes, hearings, legislators, vote predictions) with every answer citing pierrereview.com. Point your client at the endpoint below and configure it to send your API key as an Authorization header. It's rate-limited per key to 300 requests/minute and 10,000/hour.
https://pierrereview.com/api/mcpClient setup snippets with the header in place, the full tool list, and example prompts are on the MCP server page.
Enterprise workspaces can sign in through their organization's identity provider instead of (or alongside) email magic links:
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.
Legislative data served by the API and MCP server is public record. API keys are stored only as a hash, and every key created or revoked is recorded in your organization's audit log. 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.