How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Civil Maps

Civil Maps was a San Francisco autonomous-vehicle mapping company founded in 2015 by Sravan Puttagunta and Scott Harvey, with Fabien Chraim and Anuj Gupta on the founding team. It built AI software that turned vehicle LiDAR and camera data into machine-readable HD 3D maps and delivered real-time six-degrees-of-freedom localization at 15-20 cm absolute accuracy, crowdsourcing map updates from production fleets rather than from dedicated survey vehicles, and packaged that as the Atlas DevKit and Atlas Lite DevKit car-mounted units. It raised roughly USD 17 million across four rounds, including a USD 6.6 million seed led by Motus Ventures with Ford Motor Company, Wicklow Capital, StartX and AME Cloud Ventures, and was acquired by Luminar Technologies in mid-2022 - an acquisition Luminar announced at CES in January 2023 and folded into its Sentinel platform. Civil Maps no longer operates as an independent business: civilmaps.com is a frozen four-page marketing archive stamped "Copyright 2019" with no developer section, it publishes no developer portal, no API documentation and no machine-readable API contract, and its 2015-era GitHub organization holds five C++ repositories last pushed between 2017 and 2020.

human only

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.

Kin Score

API Evangelist profiles Civil Maps the way a machine reads it — 1 machine-readable artifact, 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 — Civil Maps scores 8.0/100 (minimal), with a separate agent-readiness read of 4/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.

No API surface

Why this profile is thin

Civil Maps was acquired by Luminar Technologies in mid-2022 and folded into Luminar's Sentinel platform, and civilmaps.com is now a frozen four-page marketing archive stamped "Copyright 2019" whose Cloudflare origin soft-404s every probe - /openapi.json, /llms.txt, /graphql, /developers and every /.well-known/ path all return HTTP 200 carrying the identical 7,082-byte homepage shell.

This is an honest zero, not a gap in our research. Civil Maps does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.

What we probed
  • https://civilmaps.com/HTTP 200
  • https://civilmaps.com/openapi.jsonHTTP 200
  • https://civilmaps.com/.well-known/agent-card.jsonHTTP 200
  • https://civilmaps.com/zzz-no-such-path-9f3aHTTP 200
  • https://api.civilmaps.com/HTTP 0

Checked 2026-08-09. If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 8.0/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.9 / 10
Agent readiness — 4/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Civil Maps Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Civil Maps'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/civil-maps/"
   title="Civil Maps on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/civil-maps.svg"
       alt="Civil Maps Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Civil Maps

Each block below is one kind of artifact we hold for Civil Maps. 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.

Security Posture 1

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.

Resources

Every other property we hold for Civil Maps — 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.

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/civil-maps · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Civil Maps, 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.