Standardized data (LDS-1) available via REST API and MCP for those building without compromise. Readable by humans, ready for machines. The source layer of upcoming laws, members and votes.
Check how legislations, members, and votes meet in one, relational LDS-1 schema. /health is available for database completion checks without authentication.
For the rest, send access request for 7-day demo key (no card required).
(\_/) =(o.o)= (> <)
Pricing for current coverage of unified legislative data. Annual plans include 2 months free. Coverage expands constantly—new jurisdictions and data-quality improvements are added to active plans at no extra cost. Early customers lock their starting price for 12 months. Custom plans are available for individual pricing.
Active legislative intelligence for professional researchers and journalists who require data fidelity.
Data foundation for next-gen software builders scaling commercial compliance SaaS.
Dedicated sovereign data infrastructure and tailored coverage for enterprise platforms requiring custom deployment.
We created LDS-1 out of necessity—legacy systems drown in structural and technological debt. They are inauditable. Meanwhile, public data is structurally scattered, unmonitored, and lacks custody. We reduced the complex bicameral legislative systems of global democracies to their absolute core, retrieving what is universally correct and making it concise and understandable. These are the principles we stand by.
Whether you query a UK Bill, a US Resolution, or an EU Parliament Regulation, you receive structurally the exact same JSON keys. You handle a single data schema.
Procedures are assigned a predictable, collision-free subType (bill, resolution, regulation, other), subStatus (accepted, rejected, process, upcoming_session, expired) and category (with domain-oriented enums, like agriculture, education, health, etc) for instant programmatic queries.
Every legislative process is tied to votes and their participants. By selectively pre-populating critical entity relationships, each record delivers immediate context without requiring redundant lookup calls.
The API expands as official sources are validated for LDS-1 compatibility. Active plans receive new supported jurisdictions as they are added. Customers can prioritize requested jurisdictions or sources through custom onboarding.
Production rollout includes all below. This is the standard coverage for the unified LDS-1 API, not a separate paid package.
Small engineering and operations team focused on LDS-1 standardization, data quality, and customer onboarding.
Swagger is public. Live REST require an access code issued manually to qualified users. MCP offers demo access.