use cases · readiness by segment
Buyer workflows mapped to fields, sources, and API surfaces
Apex is sold as a data product, so use cases need a concrete contract: the buyer, the field bundle, the segment readiness, the API path, and the caveat to keep visible during evaluation.
workflow lanes
Readiness is measured against the fields each workflow needs
Percentages are model-level readiness by era and powertrain segment. They describe the current dated snapshot and are also available in the coverage documentation and buyer exports.
Marketplaces, lenders, insurers
Engine and drivetrain specs
Resolve comparable trims and powertrain specs across markets.
Displacement, cylinders, power, and torque on at least one variant of the model
Required fields
Best segment
84% - ICE 2010-2014
Highest readiness among the currently published era and powertrain segments.
API surface
https://api.apex-db.org/v1/apex?make=Toyota&model=RAV4&year=2024Engine and drivetrain values can vary by market, model year, and homologation family. Use the provenance payload before collapsing variants.
Banks, lessors, financed-emissions teams
PCAF financed-emissions
Calculate vehicle-loan emissions using regulator-primary CO2 and fuel-consumption inputs.
CO₂, fuel consumption, and fuel type on at least one variant of the model
Required fields
Best segment
65% - ICE 2020-2024
Highest readiness among the currently published era and powertrain segments.
API surface
https://mcp.apex-db.org/mcp · apex_lookup_by_portfolioPCAF-ready inputs are strongest where regulators publish CO2 and fuel consumption by variant. Sparse records should fall back to documented estimation tiers.
EV apps, fleet procurement, TCO teams
BEV/PHEV battery and charging
Compare battery capacity, WLTP range, and DC charging readiness by model line.
Battery capacity, WLTP range, and DC max kW on at least one variant
Required fields
Best segment
68% - BEV 2020-2024
Highest readiness among the currently published era and powertrain segments.
API surface
https://api.apex-db.org/v1/apex?powertrain=BEV&min_year=2020Battery and charging specs are source-dependent. Apex keeps peak, usable, and cycle-specific values separate where the source distinguishes them.
Insurance, risk, compliance, fleet safety
Safety and body analytics
Join body class, recall history, and safety-test context into one variant record.
Body class and recall history on at least one variant of the model
Required fields
Best segment
30% - HEV 2015-2024
Highest readiness among the currently published era and powertrain segments.
API surface
https://api.apex-db.org/v1/apex?body_class=SUV%2FCrossoverSafety ratings are representative tests, not every trim. Recall and rating source restrictions can affect redistribution in buyer snapshots.
matrix
Segment readiness table
Compare workflow fit here, then open the coverage documentation for the full per-field matrix.
| use case · % of models in segment | ICE 2010-2014 | ICE 2015-2019 | ICE 2020-2024 | HEV 2015-2024 | PHEV 2020-2024 | BEV 2020-2024 |
|---|---|---|---|---|---|---|
Engine and drivetrain specs Displacement, cylinders, power, and torque on at least one variant of the model | 84% | 78% | 68% | 63% | 59% | — |
PCAF financed-emissions CO₂, fuel consumption, and fuel type on at least one variant of the model | 44% | 42% | 65% | 63% | 27% | — |
BEV/PHEV battery and charging Battery capacity, WLTP range, and DC max kW on at least one variant | — | — | — | — | 0% | 68% |
Safety and body analytics Body class and recall history on at least one variant of the model | 10% | 10% | 8% | 30% | 9% | 5% |
evaluation path
Prove the workflow against the sample first
Start with the sample bundle, inspect the field provenance, then move the same query to the snapshot, REST API, or MCP endpoint.