Skip to main content
The Projects Data service exposes JSON endpoints for CORE3 project intelligence: aggregate and per-project Probability of Loss (PoL), ratings, search, and structured sections (security, financial, and related domains). Public traffic reaches it through the CORE3 API gateway, which mounts the service under the projects_data path prefix.
If you’re interested in our API, feel free to reach out via [email protected]

​
Base URL

All paths in the machine-readable specification are relative to the gateway mount: 
https://api.core3.io/projects_data
Append the versioned route from the spec (for example /v1/...). A full request for a project PoL history chart over the last 30 days looks like this: 
curl -sS "https://api.core3.io/projects_data/v1/ethereum/pol/history/chart?days=30" \
  -H "x-api-key: core3_your_key_here"
In that URL, ethereum is the {slug} path parameter for the project; the segment pol is part of the fixed route (PoL score).

​
Authentication

Every request must include a valid API key in the x-api-key header. Keys issued for this API begin with the prefix core3_. 
curl -sS "https://api.core3.io/projects_data/v1/health" \
  -H "x-api-key: core3_live_0123456789abcdef"
Do not embed keys in client-side public code. Prefer a backend or serverless proxy that adds the header.

​
Conventions

  • HTTP method: All documented operations use GET.
  • Version: Routes are under /v1.
  • {slug}: Project identifier in the path (examples in the spec use values like hacken; your integration should use the slug returned by list, ratings, or search endpoints).
  • History by range: Several PoL endpoints expect Unix timestamp bounds: required query parameters from and to (seconds, inclusive range per your integration’s contract).
  • History by chart window: Chart-oriented endpoints accept optional days (integer 1–365). Omit days for all-time history, as described in the spec.

​
Endpoint map

​
Health

MethodPathSummary
GET/v1/healthLiveness and dependency status (200 / 503).

​
PoL score

MethodPathQuery / path notes
GET/v1/polCurrent index-level PoL.
GET/v1/pol/historyfrom, to (required).
GET/v1/pol/history/chartdays optional (1–365).
GET/v1/{slug}/pol/currentProject current PoL.
GET/v1/{slug}/pol/historyfrom, to (required).
GET/v1/{slug}/pol/history/chartdays optional.
GET/v1/{slug}/pol/by_categoryBreakdown by category.
GET/v1/{slug}/pol/by_category/historyfrom, to (required).
GET/v1/{slug}/pol/by_category/history/chartdays optional.
GET/v1/{slug}/pol/by_metricBreakdown by metric.
GET/v1/{slug}/pol/by_metric/historyfrom, to (required).
GET/v1/{slug}/pol/by_metric/history/chartdays optional.

​
Projects

MethodPathQuery / path notes
GET/v1/listFull project list payload.
GET/v1/{slug}Core project record.
GET/v1/{slug}/securitySecurity section.
GET/v1/{slug}/financialFinancial section.
GET/v1/{slug}/reputationalReputational section.
GET/v1/{slug}/regulatoryRegulatory section.
GET/v1/{slug}/proof_of_voiceProof of Voice section.
GET/v1/{slug}/proof_of_voice/history/chartdays optional.
GET/v1/{slug}/operationalOperational section.
GET/v1/{slug}/financial/inflation/history/chartdays optional.

​
Ratings

MethodPathQuery notes
GET/v1/ratingsPagination: page (default 1), page_size (default 20, max 50). Filters: categories, market_cap, chains, compliance (arrays). Sort: sort_by (default rank), sort_direction (ASC / DESC, default DESC).
GET/v1/ratings/parametersAvailable sorting and filtering metadata for ratings.
MethodPathQuery notes
GET/v1/searchsearch (required)—text query.
GET/v1/search/trendingTrending projects list.

​
Errors and status codes

Follow HTTP semantics. The health endpoint documents 503 when checks fail; other routes return standard client and server errors according to gateway and service behavior. On failure, read the response body for any structured message your client already handles.

​
Next steps

  • Use GET /v1/ratings/parameters when building ratings UI so sort and filter controls match server-supported values.
  • Pair this reference with Probability of Loss (PoL) and Project PoL methodology for interpretation of PoL fields in responses.
If you’re interested in our API, feel free to reach out via [email protected]