FlightCar
FlightCar was a United States peer-to-peer car-rental marketplace built around airport travel, surfaced into the API Evangelist network as an a16z portfolio lead. Enrichment probing on 2026-07-20 found no operating company behind the name and no API surface of any kind. The domain flightcar.com is registered but publishes no A, AAAA or MX records, resolves to no host, and sits on Njalla privacy nameservers with a SOA serial dated 2026-07-18; the api, developer and docs subdomains do not resolve; there is no GitHub organisation at github.com/flightcar; and no first-party client library exists on npm or PyPI. The Internet Archive shows the consumer site returning 200 through May 2016 and an Internal Server Error by July 2017, with no successful captures in 2017 or 2018. FlightCar is therefore carried in the network as a defunct company retained for portfolio-graph and historical continuity rather than as an active API provider, and should not be re-queued for artifact enrichment.
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.
API Evangelist profiles FlightCar 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 — FlightCar scores 6.8/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
How we profile FlightCar
Each block below is one kind of artifact we hold for FlightCar. 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 FlightCar — 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.
Access & Security 1
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/flightcar · machine-readable index on apis.io