silvercar website screenshot

silvercar

Silvercar began as an Austin, Texas premium car-rental startup (all-silver Audi fleet) and was a Slow Ventures portfolio company. After Audi acquired it, the team pivoted the technology into Dealerware, a dealership fleet-management and courtesy/loaner-mobility SaaS platform. silvercar.com now 301-redirects to dealerware.com, and the company's public developer surface is the Dealerware Partner Integration API — a versioned (v4) REST API on a ReadMe developer hub at developer.dealerware.com covering contracts, reservations, customers, dealerships, fleets, vehicles, drivers, employees, payments, reporting, and webhooks. Authentication is OAuth 2.0 machine-to-machine (client_credentials) via Auth0, returning RS256-signed JWT bearer tokens.

silvercar publishes 1 API on the APIs.io network. Tagged areas include Company, Automotive, Car Rental, Fleet Management, and Mobility.

The silvercar catalog on APIs.io includes 1 event-driven AsyncAPI specification.

silvercar’s developer surface includes documentation, API reference, getting-started guide, authentication, support, and 11 more developer resources.

30.1/100 thin ▬ flat Agent 32/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
AccessSelf serve
1 APIs
CompanyAutomotiveCar RentalFleet ManagementMobilityDealershipRentalsSoftware-as-a-Service

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/silvercar: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Dealerware Partner Integration API

Versioned (mob-api-v4) REST API for Dealerware fleet-management and courtesy/loaner mobility workflows: contracts, reservations, contactless check-in, customers, drivers, employ...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Silvercar Authentication

2 schemes

SECURITY

Silvercar Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: silvercar
name: silvercar
description: Silvercar began as an Austin, Texas premium car-rental startup (all-silver Audi fleet) and was a Slow Ventures
  portfolio company. After Audi acquired it, the team pivoted the technology into Dealerware, a dealership fleet-management
  and courtesy/loaner-mobility SaaS platform. silvercar.com now 301-redirects to dealerware.com, and the company's public
  developer surface is the Dealerware Partner Integration API — a versioned (v4) REST API on a ReadMe developer hub at developer.dealerware.com
  covering contracts, reservations, customers, dealerships, fleets, vehicles, drivers, employees, payments, reporting, and
  webhooks. Authentication is OAuth 2.0 machine-to-machine (client_credentials) via Auth0, returning RS256-signed JWT bearer
  tokens.
url: https://raw.githubusercontent.com/api-evangelist/silvercar/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- slow-ventures
x-successor: dealerware
x-rebrand-note: Silvercar's product and engineering became Dealerware; silvercar.com 301s to dealerware.com. API artifacts
  below document the live Dealerware surface.
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - url: https://silvercar.com
    status: 301
    note: declared website redirects to https://www.dealerware.com/ — a different registrable domain (silvercar.com -> dealerware.com),
      possible rename or acquisition (probed 2026-09-03, roadmap#169)
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Automotive
- Car Rental
- Fleet Management
- Mobility
- Dealership
- Rentals
- Software-as-a-Service
tags_raw:
- Company
- Automotive
- Car Rental
- Fleet Management
- Mobility
- Dealership
- Rental
- SaaS
image: https://files.readme.io/ce942b596bb59005caaba879dd9e42d25b4fd618aa4444310d4148fdb273781c-small-dw_darkmode.png
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: Dealerware Partner Integration API
  description: 'Versioned (mob-api-v4) REST API for Dealerware fleet-management and courtesy/loaner mobility workflows: contracts,
    reservations, contactless check-in, customers, drivers, employees, dealerships, fleets, vehicles, availability, payments
    and billing, reporting, and webhooks. OAuth 2.0 client-credentials (Auth0) with RS256 JWT bearer tokens.'
  humanURL: https://developer.dealerware.com/reference
  baseURL: https://api.dealerware.com
  properties:
  - type: Documentation
    url: https://developer.dealerware.com/docs
  - type: APIReference
    url: https://developer.dealerware.com/reference
  - type: GettingStarted
    url: https://developer.dealerware.com/docs/quickstart-guide
  - type: Authentication
    url: authentication/silvercar-authentication.yml
  - type: Webhooks
    url: asyncapi/silvercar-webhooks.yml
common:
- type: DomainSecurity
  url: security/silvercar-domain-security.yml
- type: Website
  url: https://silvercar.com
- type: DeveloperPortal
  url: https://developer.dealerware.com
- type: Documentation
  url: https://developer.dealerware.com/docs
- type: APIReference
  url: https://developer.dealerware.com/reference
- type: GettingStarted
  url: https://developer.dealerware.com/docs/quickstart-guide
- type: Authentication
  url: authentication/silvercar-authentication.yml
- type: Deprecation
  url: https://developer.dealerware.com/docs/deprecation-1
- type: Webhooks
  url: asyncapi/silvercar-webhooks.yml
- type: Support
  url: https://developer.dealerware.com/docs/support
- type: TermsOfService
  url: https://www.dealerware.com/terms-of-use/
- type: PrivacyPolicy
  url: https://www.dealerware.com/privacy-policy/
- type: LLMsTxt
  url: llms/silvercar-llms.txt
- type: WellKnown
  url: well-known/silvercar-well-known.yml
- type: Conventions
  url: conventions/silvercar-conventions.yml
- type: Lifecycle
  url: lifecycle/silvercar-lifecycle.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 8
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/silvercar"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/silvercar/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/silvercar/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.