Free public information, with the limits visible.

Use as a keyless XML/JSON bulk mirror for GovInfo collections such as bill status, bill text, CFR, Federal Register, public laws, and statutes.

Use with a server-side api.data.gov key for GovInfo package metadata, content details, related documents, and search-service lookups.

Use with a server-side api.data.gov key for agency FOIA component metadata, request-form structures, and annual-report XML rows.

Use with a server-side api.data.gov key to discover dataset metadata published by federal, state, local, and tribal governments.

Use with a server-side Census API key for demographic, ACS, population, business, and geography rows.

Use with a server-side BLS registration key for bounded time-series requests, catalog metadata, calculations, and annual averages.

Use with a server-side FRED API key for economic time-series observations, release metadata, categories, and source notes.

Use as the official LDA record source for registrations, quarterly activity reports, and LD-203 contribution reports.

Use as the official organization-identity baseline for tax-exempt entities before matching Form 990 rows, grants, donations, or lobbying-related coverage.

Use as the official bulk filing source for recent Form 990-series XML records and annual index CSVs.

Use for current regulatory text context and historical version comparisons when available.

Use with a server-side api.data.gov key for agency dockets, rulemaking documents, and public comment metadata.

Use as official workplace-safety context for OSHA citations, inspections, enforcement actions, grants, guidance, and training announcements.

Use as official EPA facility, compliance, and enforcement context across ECHO search/report services.

Use as queryable EPA environmental data context across Envirofacts tables, not as a standalone causal health or enforcement conclusion.

Use as official consumer-protection context; FTC allegations, complaints, orders, and settlements must stay separated by legal posture.

Use with a server-side Data.gov API key as a queryable FTC source layer for public consumer-protection rows, not as a substitute for legal posture review.

Use as official consumer-finance context; keep agency policy, data releases, settlements, and consumer-remedy rows separated.

Use complaint rows as consumer-submitted public signals, not as agency findings that a company violated law.

Use as market-integrity context; separate proposed rules, charges, allegations, settlements, and final orders.

Use as an SEC civil-action source row; preserve release number, respondent names, complaint/judgment links, and legal posture.

Use as official release context only; charges, allegations, pleas, verdicts, sentences, and civil actions must stay in separate legal-posture lanes.

DOJ-hosted index of underlying court filings across multiple dockets: the SDFL Doe v. Epstein civil cases, State of Florida v. Epstein, United States v. Maxwell, and USVI v. JPMorgan Chase; distinct from the general library/disclosure landing pages already covered by doj-epstein-library.

Use Supreme Court docket rows for procedural posture, filing dates, briefs, and order status only.

Use for selected United States appellate, district, and bankruptcy court opinions hosted by GPO on behalf of the U.S. Courts.

Use as a legal-data index and verify docket-document joins against court records where possible.

Use as public-award context only; recipient awards need careful company, subsidiary, and date joins before narrative use.

Use Monthly Treasury Statement rows as official outlay and fiscal context, not as a finding that spending was improper.

Use report pages as oversight anchors and keep recommendations, questioned costs, findings, and management responses separate.

Use GAO report rows as oversight anchors; preserve report number, publication date, topics, recommendations, and source URL.

Use PRAC/Pandemic Oversight pages for official pandemic-spending context, enforcement summaries, and oversight report links.

Use after a server-side Data.gov/FAC API key is configured; preserve auditee, UEI/EIN when available, audit year, federal awards, findings, and report links.

Use only with a server-side SAM.gov key; store UEI, exclusion type, active dates, agency, and official URL before joining to awards.

Use as an exact-list-match compliance context source; preserve list name, program, entity type, aliases, addresses, and update date where available.

Use FAR and FAC text as procurement-policy context; cite exact part, subpart, clause, FAC update, and effective date when attaching it to a procurement review row.

Use for model IDs and lineup terms; do not use as a substitute for access-limit or status records.

Use launch and restoration posts as primary Anthropic records; keep marketing, access, and safety claims in separate rows.

Use for pricing and usage-cost terms only; pair with access and status sources before operational recommendations.

Use for outage and incident history; do not infer product-access policy from operational incidents alone.

Use as official national-account context for GDP, income, outlays, PCE, trade, and investment releases.

Use as official economic-indicator context; do not turn topline numbers into policy blame, motive, or market advice.

Use as official public-health context for CDC updates, advisories, outbreaks, and recommendations.

Use complaint rows as consumer-submitted public signals, not as agency findings that a company violated law.

Use as official consumer-finance context; keep agency policy, data releases, settlements, and consumer-remedy rows separated.

Use as an official risk-prioritization anchor for vulnerabilities exploited in the wild.

Use as current Fable promotional-access record; preserve exact date windows and separate Claude Code limit language.