LawLinter Developer API

API direction

The current protected API is mounted at /api/legislative and is treated as a development compatibility surface while the product stabilizes.

Production customer documentation should move toward versioned /api/v1 routes once endpoint names, subscription scopes, pagination, and response envelopes are finalized.

• Congress.gov-derived records: bills, laws, lawmakers, committees, amendments, text versions, deterministic analysis, and related records.
• House vote records: vote details, member positions, rollups, and filters.
• FEC/OpenFEC context: candidate and committee finance totals connected to lawmakers and bill participants through conservative source-attributed bridges.

Launch access and metering

API access is key-based and currently available for launch-period testing and early integrations where an account has an active API plan.

Launch access is metered. Monthly request limits, burst limits, scopes, and usage logs are used for quota enforcement, reliability, abuse prevention, and future plan design.

Public pages remain crawlable, while protected API access can be tiered by feature area, volume, and premium data depth.

Limits, scopes, pricing, endpoint availability, and subscription requirements may change as paid API tiers are introduced.