Calibrated marks with clear provenance
for API consumers
Every response is a read-only JSON record: latest mark, interval, source references, and a complete meta envelope so downstream systems can validate what they receive.
Why this API is different
Most valuation feeds are numbers. Spearhead provides numbers with evidence and versioned behavior.
We return both point estimate and interval so teams can decide if a mark is decision-ready for the context it is used in.
Reliability, coverage, and misses are published in scorecards. It is not a one-way signal.
The meta block on every payload includes methodology, dataset, timestamp, and backtest vs live labels. You can gate usage by those fields.
In the latest competitive sweep (18 vendors), only 0 publish walk-forward backtests and 0 publish calibration disclosure. Spearhead keeps both visible in product routes.
Start in 3 simple steps
/v1. The free tier includes the top-10 list and latest mark path.meta.data_mode and meta.provenance on each response.export SPEARHEAD_API_KEY=sph_test_example_key
curl -sS "https://api.pegasusthreesixty.com/v1/companies/coreweave?coverage=80" \
-H "X-API-Key: $SPEARHEAD_API_KEY"{
"meta": {
"data_mode": "illustrative",
"provenance": "backtest",
"methodology_version": "v0.2.0",
"dataset_version": "2026-06-14",
"as_of": "2026-06-10",
"disclaimer": "Illustrative backtest derived from public events."
},
"slug": "coreweave",
"name": "CoreWeave",
"sector": "AI Cloud Infrastructure",
"latest_mark": {
"as_of_date": "2025-03-27",
"value_usd": 22062735430,
"lower_usd": 10903281498,
"upper_usd": 44643834494,
"confidence": 0.791
}
}Endpoint overview
All endpoints are read-only and versioned under /v1.
Implementation notes
Contract stability
Contract fields under /v1 are additive. Breaking changes are reserved for explicit version increments and published migration windows.
Read the full /v1 contract, including pagination, rate limits, and error codes.