FRED API
Create a FRED account, review its API terms and request a distinct key for the SCULTRA news system.
Register with FRED ↗Every source is registered before use. Connection does not equal permission to publish, and evidence does not become an article without verification, original writing and editorial approval.
The existing three governed connections remain unchanged. Of the 57 additional sources, 55 are now in safe qualification monitoring and two are waiting for account registration.
Registration creates credentials for source access. It does not authorize SCULTRA to copy or automatically publish source content.
Create a FRED account, review its API terms and request a distinct key for the SCULTRA news system.
Register with FRED ↗Create the free client account and obtain the API token used by the football results and fixtures adapter.
Register with football-data.org ↗A connected source can still return zero eligible records when its health, rights, correction or record-level gate fails. SCULTRA does not weaken those gates to fill a publishing schedule.
Official releases enter through the governed Dhan read-only envelope.
RSS schema, correction behavior, rate and rights use must be frozen before activation.
Requires a stable official discovery endpoint and correction mapping.
Gazette issue identifiers and amendment lineage must be mapped.
House, document and revision identifiers require normalization.
Records enter only through the governed Dhan read-only envelope and remain subject to feed health and record gates.
Official release discovery is pending a stable adapter.
Official notices require document and correction lineage.
Product announcements require independent context before publication.
A reviewed repository allowlist is required; authentication raises the rate limit.
Discovery only; original linked sources must be verified before editorial use.
The Dhan envelope remains authoritative for source health, rights and export eligibility; blocked records are rejected.
Circular, notification, speech and press-release identifiers require normalization.
Orders, circulars and press releases need separate document classes.
Exchange terms, symbols, attachments and correction events must be frozen.
Exchange terms, scrip identifiers and attachment revisions must be frozen.
Circular and press-release document classes require mapping.
Circular, order and press-release identifiers require normalization.
Circular and press-release discovery is pending schema review.
Orders and press releases require case and correction lineage.
A company and filing-form allowlist plus SEC fair-access identity is required.
Indicator and geography allowlists are required before collection.
Article and publication-series identifiers require normalization.
Requires FRED_API_KEY and a reviewed series allowlist.
Release schedules and revision series require explicit lineage.
Recommendations must remain distinct from enacted rules and notifications.
Circular, notification and amendment lineage must be retained.
Trade notices and policy amendments require document lineage.
Free-key limits, data rights and league coverage must be approved.
Requires FOOTBALL_DATA_API_KEY plus competition and rate-limit configuration.
League and season allowlists plus ODbL attribution must be configured.
Fixture, result and article usage terms require review.
Fixture, result and article usage terms require review.
Competition data and article usage terms require review.
Event data and article usage terms require review.
Advisory identifiers, updates and severity normalization are required.
A key raises rate limits; CVE update and rejection states must be retained.
Catalog revisions and remediation dates must be handled as updates, not duplicate news.
Advisory revision and product scope require normalization.
RSS schema and correction behavior require qualification.
Official release discovery is pending a stable adapter.
Mission updates require event and revision identifiers.
Per-paper licence and commercial-use terms must be retained.
Subject, type and publisher filters plus deposited-update handling are required.
NASA_API_KEY is optional for APIs; media rights must be assessed separately.
Feed schema, update behavior and WHO content terms require qualification.
NCBI_API_KEY is optional; query scope and per-article licences must be retained.
Advisories, programmes and statistical releases require separate schemas.
Research announcements and guidance revisions require mapping.
Media-release and health-alert update behavior must be qualified.
Forecasts, warnings and observed reports need expiry and correction semantics.
Bulletins and station data require provenance and late-update rules.
Notifications and press releases require amendment lineage.
RSS availability, schema and correction behavior require qualification.
News and report release types require stable identifiers.
News and report release types require stable identifiers.
Schemes, crop estimates and notices require separate document types.
Export releases and datasets require schema and rights review.
Reports, notices and statistics require release-series lineage.
Policy notices, scheme updates and statistics require separate schemas.