Build on the same election intelligence layer used across Akashic Edge.
Ask a question. Explore the map. Analyze a place. Build on the data. Build is the operational route for teams that need docs, keys, embeds, and structured election access without switching into a separate brand or a separate product story.
Build is a peer route, not an afterthought. It should read as workflow, trust, and operational readiness.
Docs, pricing, dashboard, and embeds need to use the same naming and hierarchy as the rest of the product.
Trust-heavy surfaces can go light, but the product model and typography stay consistent.
The Build route is for teams that need production access, not a feature tour.
Newsrooms and publishers
Power explainers, election desk utilities, embed rollouts, and shareable county or state context without hand-building every chart.
Researchers and analysts
Move from a place question to reproducible queries, structured exports, and provenance-aware data access without rebuilding the base dataset.
Product and platform teams
Use one source of truth for applications, internal tooling, and public-facing data products instead of stitching together partial vendors.
What Build has to communicate immediately
One clean schema
{
"data": [
{ "fips": "55025", "county": "Dane County", "margin": 39.51 },
{ "fips": "55079", "county": "Milwaukee County", "margin": 30.36 },
{ "fips": "55133", "county": "Waukesha County", "margin": -18.55 }
],
"meta": { "queryTimeMs": 18, "rowCount": 72, "apiVersion": "v1" },
"rateLimit": { "limit": 60, "remaining": 59 }
}Use a small, readable endpoint slice to orient people fast.
| Method | Route | What it is for |
|---|---|---|
| GET | /api/v1/elections | List election years and office availability. |
| GET | /api/v1/elections/2024/president | Return structured election results by office and cycle. |
| GET | /api/v1/elections/timeseries | Fetch time-series margin history for a place or comparison set. |
| GET | /api/v1/counties/17031 | Return county profile, demographics, and election context. |
| GET | /api/v1/compare | Compare places or elections on one shared schema. |
| POST | /api/v1/historian/query | Access the Historian programmatically on eligible tiers. |
Separate evaluation, production use, and institutional rollout.
Evaluate
Read the docs, inspect the schema, and review the developer dashboard flow before you commit.
Edge Insider
Use the paid individual build tier when you need repeatable developer access, Historian API workflows, and clean embeds.
Institutional rollout
Use the institutional path when the actual buyer is a newsroom, classroom, lab, or organization.