oneNav
oneNav is a fabless GNSS (Global Navigation Satellite System) semiconductor company building the next generation of mobile positioning. Its L5-direct receiver acquires and tracks on the modern L5 satellite band without legacy L1 aiding, delivering higher location accuracy in urban canyons and far greater resilience to GPS jamming and spoofing, in half the RF size, power and cost of hybrid L1+L5 solutions. Founded in 2019 (Steve Poizner, Paul McBurney) with offices in Sunnyvale, CA and Tampere, Finland, oneNav targets smartphones, wearables, IoT trackers, defense and emergency services. It is backed by GV, Norwest Venture Partners and GSR Ventures. oneNav is a hardware/silicon company and does not publish a public developer API, OpenAPI, or developer portal.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
oneNav is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — oneNav scores 12.3/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
Resources
Every other property we hold for oneNav — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
oneNav is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/onenav · machine-readable index on apis.io