SourceFinch Verified · Regulation & rulemaking
Code of Federal Regulations title currency status
The 50 titles of the Code of Federal Regulations as published in the eCFR, each with its name, the date of its latest amendment, the latest Federal Register issue incorporated and the date it is current through. A compact monitor of when any CFR title changes.
- Healthy · 100% of observed runs successful
- Regulation & rulemaking
- Office of the Federal Register (National Archives)
- United States (federal)
- Publisher's public API
- 6 typed fields
At a glance
- Category
- Regulation & rulemaking
- Jurisdiction
- United States (federal)
- Publisher updates
- Each federal business day as the eCFR incorporates Federal Register amendments
- SourceFinch checks
- Daily by default
- Records per run
- 50 in the latest run
- Record key
title_number- Acquired from
- Publisher's public API:
https://www.ecfr.gov/api/versioner/v1/titles.json - Recipe
- v1.0.0, approved October 12, 2026
- Verified since
- October 12, 2026
- Last green run
- October 12, 2026
What the data contains
The Electronic Code of Federal Regulations (eCFR) is the continuously updated editorial compilation of the Code of Federal Regulations maintained by the Office of the Federal Register and the Government Publishing Office. Its titles endpoint lists all 50 CFR titles with the date each was last amended, the latest Federal Register issue incorporated into it and the date it is up to date through. This source reads that one small document (about 8 KB) each run and makes one record per title keyed by the title number, so a monitor reports the day any title's latest_amended_on moves, which is the earliest structured signal that a regulation in that title changed. Title 35 is reserved and carries no dates. The eCFR is not the official legal edition of the CFR; the annual edition on govinfo.gov is. The full-text and rendering endpoints of the eCFR API are disallowed by robots.txt and are not used; only the titles summary is read. The records describe regulatory titles and contain no personal data.
Fields and types
Every record has these fields. The key field title_number identifies a record across runs, so changes are reported field by field.
| Field | Type | Description |
|---|---|---|
title_numberkey | string | CFR title number, 1 to 50, as a string. The record key. |
name | string | Title heading as published (for example Banks and Banking); Reserved for title 35. |
latest_amended_on | date, nullable | Date of the most recent amendment incorporated into the title (YYYY-MM-DD); null for the reserved title. |
latest_issue_date | date, nullable | Date of the latest Federal Register issue whose changes have been incorporated into the title (YYYY-MM-DD). |
up_to_date_as_of | date, nullable | Date through which the eCFR considers the title current (YYYY-MM-DD). |
reserved | boolean | Whether the title number is reserved and has no regulations (true only for title 35). |
Sample output
The first 5 of 50 records from SourceFinch's own run on October 12, 2026, exactly as delivered.
| Field | Record 1 | Record 2 | Record 3 | Record 4 | Record 5 |
|---|---|---|---|---|---|
title_number | 1 | 2 | 3 | 4 | 5 |
name | General Provisions | Federal Financial Assistance | The President | Accounts | Administrative Personnel |
latest_amended_on | 2022-12-29 | 2026-08-17 | 2015-03-17 | 2024-07-18 | 2026-10-05 |
latest_issue_date | 2026-08-10 | 2026-08-18 | 2024-05-17 | 2024-07-18 | 2026-10-05 |
up_to_date_as_of | 2026-10-08 | 2026-10-08 | 2026-10-08 | 2026-10-08 | 2026-10-08 |
reserved | false | false | false | false | false |
Sample as JSON
[
{
"name": "General Provisions",
"reserved": false,
"title_number": "1",
"up_to_date_as_of": "2026-10-08",
"latest_amended_on": "2022-12-29",
"latest_issue_date": "2026-08-10"
},
{
"name": "Federal Financial Assistance",
"reserved": false,
"title_number": "2",
"up_to_date_as_of": "2026-10-08",
"latest_amended_on": "2026-08-17",
"latest_issue_date": "2026-08-18"
},
{
"name": "The President",
"reserved": false,
"title_number": "3",
"up_to_date_as_of": "2026-10-08",
"latest_amended_on": "2015-03-17",
"latest_issue_date": "2024-05-17"
},
{
"name": "Accounts",
"reserved": false,
"title_number": "4",
"up_to_date_as_of": "2026-10-08",
"latest_amended_on": "2024-07-18",
"latest_issue_date": "2024-07-18"
},
{
"name": "Administrative Personnel",
"reserved": false,
"title_number": "5",
"up_to_date_as_of": "2026-10-08",
"latest_amended_on": "2026-10-05",
"latest_issue_date": "2026-10-05"
}
]Evidence behind every value
- Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash
52b783ba376191aa1a49df716665503787669300f72c6dcf7e11bb5d8375d6e0. - Every value records where it came from in that response: a JSON Pointer into the retained capture.
- Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is
730b9ac0137a142003534172fde4c31ef99b951f81678834cb64a76f88089469, timestamped October 12, 2026. - The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
- Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch:
sourcefinch verify-bundle run.wacz.
Terms posture and usage rights
- Terms
- Automated access permitted · publisher's terms
- robots.txt
- Allows this path · SHA-256
d88f2efa4f01b8ed… - AI-preference signals
- None observed at review
- Public record
- Yes. Federal Register Act, 44 U.S.C. 1510 (Code of Federal Regulations); 1 CFR part 8.
- Reviewed
- October 12, 2026; next review April 12, 2027
- Licence basis
- U.S. government work (public domain)
- Commercial use
- Allowed
- Redistribution
- Allowed
- Attribution
- Not required
The eCFR publishes a documented public REST API (versioner, search and renderer services) that needs no key or registration. The Code of Federal Regulations is a work of the U.S. government (17 U.S.C. 105). eCFR's robots.txt disallows only the full-text (/api/versioner/v1/full/) and renderer (/api/renderer/) endpoints; the titles summary endpoint used here is allowed. The eCFR is an editorial compilation and not the official legal edition. Like FederalRegister.gov, the HTML site challenges unidentified automated clients, so SourceFinch uses only the API, which answered SourceFinch's declared crawler at review.
Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.
Reliability
- Runs, last 30 days
- 1
- Green
- 100%
- Failed
- 0
- Median run time
- 0.7 s
- Latest run
- success, October 12, 2026
Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: October 12, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.
Use it
Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).
Console
Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.
Portable recipe
Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.
{
"schema": "sourcefinch/source@1",
"name": "Code of Federal Regulations title currency status",
"url": "https://www.ecfr.gov/api/versioner/v1/titles.json",
"recipe": {
"mode": "http",
"format": "json",
"items": "titles[*]",
"fields": {
"name": "name",
"reserved": "reserved",
"title_number": "number",
"up_to_date_as_of": "up_to_date_as_of",
"latest_amended_on": "latest_amended_on",
"latest_issue_date": "latest_issue_date"
},
"required": [
"title_number",
"name"
],
"types": {
"latest_amended_on": "date",
"latest_issue_date": "date",
"reserved": "boolean",
"title_number": "string",
"up_to_date_as_of": "date"
}
},
"schedule": "daily",
"key_field": "title_number"
}source.json
The request body used by the API, CLI and SDK examples.
{
"name": "Code of Federal Regulations title currency status",
"url": "https://www.ecfr.gov/api/versioner/v1/titles.json",
"recipe": {
"mode": "http",
"format": "json",
"items": "titles[*]",
"fields": {
"name": "name",
"reserved": "reserved",
"title_number": "number",
"up_to_date_as_of": "up_to_date_as_of",
"latest_amended_on": "latest_amended_on",
"latest_issue_date": "latest_issue_date"
},
"required": [
"title_number",
"name"
],
"types": {
"reserved": "boolean",
"title_number": "string",
"up_to_date_as_of": "date",
"latest_amended_on": "date",
"latest_issue_date": "date"
}
},
"key_field": "title_number",
"schedule": "daily",
"rights": true,
"catalog": {
"slug": "ecfr-title-status",
"version_id": "159ddf66-7adf-4cab-8469-51f2b7c326f6"
}
}REST API
Create an API key under Console → API keys. Reference: /docs/api.
# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/ecfr-title-status -H "Authorization: Bearer $SOURCEFINCH_API_KEY"
# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d @source.json
# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Idempotency-Key: $(uuidgen)"CLI
The sourcefinch CLI is not on npm yet; see /docs/cli.
sourcefinch login
sourcefinch catalog get ecfr-title-status --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_IDTypeScript SDK
The SDK is not on npm yet; see /docs/sdk.
import { SourceFinch } from "@sourcefinch/sdk";
const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("ecfr-title-status");
const source = await sf.sources.create({
catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
name: entry.name.slice(0, 100),
url: entry.acquisition_path.endpoint,
recipe: entry.recipe.definition,
key_field: entry.recipe.key_field,
schedule: entry.recipe.schedule,
rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);MCP
Remote MCP server with OAuth; see /docs/mcp.
claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp
# then ask your agent:
"Use SourceFinch to monitor Code of Federal Regulations title currency status: get_catalog_source ecfr-title-status,
then create_source with its create_source_args (dry run first), then run_source."Pricing
Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.
Guides using this source
Related sources
More from Office of the Federal Register (National Archives) and in regulation & rulemaking.
SourceFinch is independent and is not affiliated with or endorsed by Office of the Federal Register (National Archives). This page describes code of federal regulations title currency status as SourceFinch acquires it.