Open public records

Public candidate API and AI access

Anyone can read public candidate records and election races without an account or an MCP connection. No API key, OAuth authorization, or residential address is required to browse and retrieve records.

Find, count, and cite records

  1. Open the candidate or race directory. The JSON response includes total and the complete list. Counts describe Voterist’s coverage, not every candidate or race nationwide.
  2. Search the returned names, offices, districts, or race titles. Use each entry’s slug to retrieve its individual record.
  3. For a candidate, use record.workspace when a published record exists; otherwise read preview. Match each position’s sourceId to the corresponding evidence entry and cite its URL.
  4. Link readers to /candidate/{slug} or /race/{slug}. These pages contain readable HTML without requiring JavaScript.
curl https://www.voterist.com/api/public/candidates
curl https://www.voterist.com/api/public/races
curl https://www.voterist.com/api/public/candidates/aaron-d-ford-nv-2026-governor

Try the Nevada governor race or its JSON record.

Public read endpoints

All endpoints below accept ordinary HTTP GET requests. Public record responses allow cross-origin browser reads without credentials.

GET /api/public/candidates
All public candidate entries. Read total for the current count and candidates for the complete directory; no pagination.
GET /api/public/races
All public races, including their candidate rosters. Read total for the race count and races for the complete directory; no pagination.
GET /api/public/candidates/{slug}
One candidate’s metadata, researched preview, and published record when available.
GET /api/public/races/{slug}
One race, its election date, and its candidate roster, under race.
GET /api/public/candidates/{slug}/source-packet
A published source packet with positions, evidence, and endorsements. Requires an available published record.

Machine-readable documentation: OpenAPI specification · AI access summary · Public page sitemap

Read the record’s status with its contents

An unclaimed candidate can still have a public roster entry and a researched preview. published: false or record: null does not mean the candidate is absent or the preview is private. Claim status describes campaign access; publication status describes an available published record.

Preserve the distinction between official filing facts, Voterist research, and campaign-managed publications. Evidence marked “Check needed” still requires review. Missing positions are not evidence of a candidate’s views. Fictional samples are excluded from the public directory and sitemap.

Race rosters and the candidate directory can have different update times for research and publication status. Use the individual candidate endpoint for the record and its supporting evidence. Verify election procedures and ballot eligibility with the responsible election authority.

If your assistant cannot retrieve a record

An assistant’s search index or web reader may not support a URL that an HTTP client can retrieve. Try the public HTML page or JSON endpoint directly. A cached “Loading election roster” page is not proof that records are unavailable. If your assistant has no browsing or HTTP tools, open these links in a browser.

A 404 on a candidate or race endpoint means no publicly available match. A 404 on a source packet means no published packet is available; check the candidate preview. A 503 means a temporary service failure: wait for the Retry-After interval and retry. It does not mean authentication is required.

Claiming or editing a candidate profile

Candidate management requires authorization. The remote MCP endpoint at https://www.voterist.com/api/mcp serves compatible, authorized candidate-management clients using Streamable HTTP POST. Connecting it is not necessary for public reading.

Candidate assistant connections