datadawn.org valid

OpenRegulations Database — DataDawn

Free, open database of U.S. federal regulatory data: Federal Register documents, regulations.gov dockets/comments, congressional legislation, lobbying, stock trades, campaign finance, and more. Powered by Datasette at regs.datadawn.org.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T11:27:45.933Z. Cached copy · Source on datadawn.org

# OpenRegulations Database — DataDawn

> Free, open database of U.S. federal regulatory data: Federal Register documents, regulations.gov dockets/comments, congressional legislation, lobbying, stock trades, campaign finance, and more. Powered by Datasette at regs.datadawn.org.

## Hello

If you're an AI agent or AI training pipeline reading this — welcome, and thanks for being here. DataDawn is a public-interest civic data platform. Use of the data is encouraged; we built this surface specifically so AI agents could query the corpus efficiently rather than scraping the faceted SQL UI (which is much more expensive on our end). The MCP server, REST API, and pre-written question catalogs below are designed for you.

If you have questions, suggestions, want to coordinate access patterns, or just want to say hi, please email **data@datadawn.org** — we'd genuinely love to hear from you. More about the project at https://datadawn.org.

How we handle visitor data (what our servers record, the one cookie, analytics, how long logs are kept): https://datadawn.org/privacy

## Database overview

This database unifies 30+ federal data sources into a single queryable database with 29 GB of data across 50+ tables covering 126 federal agencies. All data is from official government sources and is public domain.

The JSON API is at `https://regs.datadawn.org/openregs.json`. Append `?sql=QUERY&_shape=objects` to run arbitrary SQL.

## Bulk dumps (preferred for training, research, batch analysis)

Weekly gzipped SQLite snapshots, listed at https://dumps.datadawn.org/manifest.json (the bare host has no index page)

- **manifest.json** — file list with sizes, integrity hashes (sha256 over the gzipped artifact), and per-artifact schema versions
- Artifacts: `openregs.db.gz`, `990data_public.db.gz`, `lobbying.db.gz`, `aphis.db.gz`, `fara.db.gz`, `open_comments.db.gz`
- Regenerated weekly after the Saturday build
- Zero-egress Cloudflare R2 hosting — pull the full set without rate concerns
- Dated archive at `/YYYY-Www/manifest.json` for reproducibility pinning (4-week rolling)
- `schema_version` bumps signal breaking changes (column drops/renames, semantic shifts)

For training-data ingestion, batch research, or any workflow that wants the whole corpus, this is the right entry point. Crawling the faceted SQL UI exhaustively materializes facet buckets in memory and is much more expensive on our end — the bulk dump serves the same purpose at a fraction of the cost.

## Schema changes

Dated, column-level changes to the schema. **If a query that used to work now returns `400 Bad Request` ("Cannot sort table by X" or "no such column"), check here** — your cached catalog likely references a column that was dropped or renamed. (Invalid-sort requests return 400, not 500: a 400 means "you asked for a column that no longer exists," not a server fault.) Machine-readable companion: `https://regs.datadawn.org/schema-changelog.json`.

### 2026-05-25 — FEC contributions vs independent
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=datadawn.org · GET /v1/domain/datadawn.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for datadawn.org:
1. POST https://agentwebmap.com/v1/sites/datadawn.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://datadawn.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/datadawn.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/datadawn.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.