Zipcar
Zipcar is a Boston, Massachusetts-based car sharing service operating in more than 500 cities across North America and Europe, including major US metros (Boston, Chicago, Los Angeles, New York, Philadelphia, Portland, San Francisco, Seattle, Washington DC) and Canadian cities (Toronto, Hamilton, the Golden Horseshoe). Members reserve vehicles by the hour or day through the Zipcar mobile app, unlock cars with their phone, and pay per usage with gas, EV charging, standard damage protection insurance, and professional maintenance included. Zipcar serves consumer members, universities (Zipcar for Universities), and businesses (Zipcar for Business) with weekday fleet programs. Zipcar is a wholly-owned subsidiary of Avis Budget Group, Inc. (NASDAQ: CAR), which acquired the company in March 2013 for approximately $500 million. Zipcar exposes a REST-based Partner API at api.zipcar.com/partner-api, documented at owa.zipcar.com/documentation, that returns JSON for Location List and Location Detail resources (vehicles available at a lat/long); access is gated and granted on request via developerportal@zipcar.com — there is no public OpenAPI spec, SDK, or self-service developer signup. Zipcar also operates a public GitHub organization (github.com/Zipcar) hosting internal DevOps tooling (Concourse resources, Ansible helpers, BOSH helpers, monitoring agents) rather than client-facing API artifacts.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Zipcar 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 — Zipcar scores 12.2/100 (emerging), with a separate agent-readiness read of 3/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. 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-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Zipcar'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/zipcar-com/"
title="Zipcar on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zipcar-com.svg"
alt="Zipcar Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/zipcar-com/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/zipcar-com/"
title="Zipcar on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/zipcar-com/card.svg"
alt="Zipcar 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 Zipcar
Each block below is one kind of artifact we hold for Zipcar. 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 Zipcar — 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 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 10
The organization behind the API
Scroll within the panel for all 10 ·
Other 7
Properties that don't map to a standard resource type
Scroll within the panel for all 7 ·
← All providers · Data indexed from github.com/api-evangelist/zipcar-com · machine-readable index on apis.io
This is an independent, third-party profile of Zipcar, 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.