Nexar
Nexar is a physical-AI infrastructure company that operates one of the largest real-world video driving datasets — over 1.2 billion miles of driving captured each year by more than 350,000 connected dashcams — and turns it into training data, collision-prediction models and real-time road intelligence for autonomous-vehicle, ADAS, mapping and smart-city programs. Its developer-facing surface is the CityStream™ family of REST APIs, published as four OpenAPI 3.0.1 contracts on the Nexar Developers Portal: VirtualCam (anonymized road frames), Live Feed (real-time detections), Work Zones (curated construction-zone detections, served as WZDx and GeoJSON) and Road Inventory (curated traffic-sign and road-asset detections). All four run on a single gRPC-gateway backed host and are authorized with a bearer access token minted through Nexar's Okta authorization server. Nexar also publishes the open-source BADAS collision-prediction model on PyPI and the `nap` platform CLI through its own Homebrew tap.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Nexar the way a machine reads it — 14 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
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 — Nexar scores 36.2/100 (thin), with a separate agent-readiness read of 44/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Nexar's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nexar/"
title="Nexar on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nexar.svg"
alt="Nexar Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/nexar/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nexar/"
title="Nexar on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/nexar/card.svg"
alt="Nexar Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Nexar
Each block below is one kind of artifact we hold for Nexar. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Nexar CityStream™ Live Feed API V4 API
The CityStream™ Live Feed API V4 API from Nexar — 1 operation(s) for citystream™ live feed api v4.
Nexar Get a collection of road signs API
The Get a collection of road signs API from Nexar — 1 operation(s) for get a collection of road signs.
Nexar Get a collection of work zones API
The Get a collection of work zones API from Nexar — 1 operation(s) for get a collection of work zones.
Nexar Get a specific work zone API
The Get a specific work zone API from Nexar — 1 operation(s) for get a specific work zone.
Nexar Get the details of a specific road sign API
The Get the details of a specific road sign API from Nexar — 1 operation(s) for get the details of a specific road sign.
Nexar VirtualCam API
The VirtualCam API API from Nexar — 3 operation(s) for virtualcam api.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
Nexar MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Nexar Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Nexar Rate Limits
RATE LIMITSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Nexar — 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.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/nexar · machine-readable index on apis.io
This is an independent, third-party profile of Nexar, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.