Getaround
Getaround is a peer-to-peer car-sharing marketplace and connected-car technology company founded in 2009 and headquartered in San Francisco, California, with significant European operations across France, Germany, Spain, Belgium, Norway, and the United Kingdom. The platform pairs private and professional vehicle owners with renters who book cars by the hour or day, unlocking and starting vehicles from a mobile app rather than meeting the owner to exchange keys. The keyless experience is enabled by Getaround Connect, a proprietary in-car telematics device that the company designs and installs in shared vehicles to handle remote lock/unlock, ignition, GPS tracking, mileage reporting, fuel level monitoring, and trip event recording. Getaround acquired Drivy in 2019 to consolidate the European car-sharing market and acquired the HyreCar rideshare-driver rental marketplace in 2022. The company went public on the NYSE via a SPAC merger in December 2022 at a valuation of roughly $1.2 billion, was delisted from the NYSE in July 2024 and transferred to OTC Pink under the ticker GETR after its market capitalization collapsed to roughly $24 million. On February 11, 2025, Getaround announced it was ceasing all United States operations — including HyreCar — while preserving its European business, which continues to operate in major EU cities under the same Getaround Connect platform. Getaround has never published a public developer API, OpenAPI specification, SDK, or developer portal; partner integrations with insurers, fleet operators, and automotive OEMs have historically been delivered through private, contract-bound APIs rather than a self-service developer surface. The company's GitHub organization hosts primarily forks of generic open-source libraries (Braintree SDKs, iOS testing frameworks, logging libraries) rather than first-party API artifacts.
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 Getaround the way a machine reads it — 2 machine-readable artifacts, 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 — Getaround scores 8.7/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 Getaround
Each block below is one kind of artifact we hold for Getaround. 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 2
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 Getaround — 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 9
The organization behind the API
Scroll within the panel for all 9 ·
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/getaround-com · machine-readable index on apis.io