JSON endpoints
Every Phidea dataset is served both as a human-readable page and as JSON. The endpoints below are what Phidea’s own pages consume at build time; you can consume them too. No authentication, CORS open, 1-hour cache with 24-hour stale-while-revalidate.
- /api/tools.jsonTools registry
Every active US-insurance tool: slug, name, generation, stack layer, actions, ownership, signals (funding, named carriers, analyst mentions), limitations, last-verified date.
- /api/carriers.jsonCarrier footprint index
Every named carrier across the tool registry with tool count, stack layers, deployment list with source URLs, and news slugs.
- /api/ownership.jsonOwnership records
Counts by ownership type, full ownership records per tool, and the recent-moves list for 2024+ acquisitions sorted by year then deal value.
- /api/news.jsonNews items
Every Phidea news brève with event date, headline, lead, body, industries, regions, referenced tool slugs, and sources.
Usage
Every endpoint returns a top-level $schema field describing the dataset, generatedAt (ISO 8601), a count, and the records. Record URLs point to the canonical human-readable page on phidea.eu.
For carrier deployment sources, follow the source URL on each deployment for the original public citation.