Screening sources manifest: sanctions and PEP source lists, per-source staleness (max_age_hours), attribution, and covered regimes

Source configuration and coverage manifest for the entity-screening corpus: which sanctions and PEP source lists are loaded, each list's freshness and staleness threshold (max_age_hours), per-source attribution and provenance under its public reuse terms, the covered sanctions regimes (covered_regimes), and an explicit statement of what is not covered. Use it to inspect source configuration, list freshness, and whether a regime such as US OFAC SDN (ofac_sdn) is in scope before screening. A metadata endpoint: it reports loaded state (always 200), never a screening verdict.

get/api/v1/entity/sources

Response

Successful Response

Example response

{
  "meta": {
    "endpoint": "/api/v1/fred/us/cpi",
    "data_time": "2026-04-16T14:30:00Z",
    "response_time": "2026-04-16T14:30:12Z",
    "provider": "Sugra API v1.0.1",
    "source": "sugra_crypto",
    "attribution": "Short interest and Reg SHO daily short volume data is owned by and sourced from FINRA (Financial Industry Regulatory Authority).",
    "fallback_chain": [
      "sugra_crypto",
      "sugra_finance"
    ]
  }
}

Changes

Changed in 3 of the 21 revisions of this API.314

Aug 28, 2026560e8847c7b32See the full diff
- ▲
  response property data/covered_regimes/anyOf[subschema #1]/items/ list-of-types was widened by adding types null to media type application/json of response 200
  response-property-list-of-types-widened
- ▲
  response property data/not_covered/anyOf[subschema #1]/items/ list-of-types was widened by adding types null to media type application/json of response 200
  response-property-list-of-types-widened
This revision also has 15 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 22, 2026914af3d38c7c12See the full diff
- ▲
  the response's body type/format changed from / to object/ for status 200
  response-body-type-changed
- ○
  added the required property data to the response with the 200 status
  response-required-property-added
- ○
  added the required property meta to the response with the 200 status
  response-required-property-added
Aug 8, 20264c4530760ba112See the full diff
- ○
  added the optional property code to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property code to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property code to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property hint to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property plan to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 401 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 429 status
  response-optional-property-added
- ○
  added the optional property reason to the response with the 503 status
  response-optional-property-added

Full history