BizzyCar

BizzyCar is a B2B SaaS platform for automotive dealerships that automates service recall management, customer outreach and mobile service. Founded in 2018 and headquartered in Saint Peters, Missouri, the company ingests VIN-level open-recall data from OEM partners, matches it against a dealer's market area and DMS records, then uses AI-driven outreach (SMS, email, voice) to book service appointments and dispatch mobile service vans. Products include Recall Outreach, Recall Scout, Recall Radar, Service Engine, Mobile Service and Fleet IQ. BizzyCar is primarily an API *consumer* rather than an API producer: it ships pre-built connectors into dealer management systems (Dealertrack, DMS Plus, Open/Mate, Asbury, PBS, Tekion, Fortellis, Reynolds & Reynolds) and service schedulers (Xtime, TCC, DealerFX, Affinitiv, Update Promise), but publishes no public developer program, API reference or machine-readable contract of its own.

BizzyCar is profiled on the APIs.io network. Tagged areas include Company, Automotive, Recall Management, Dealerships, and Mobile Service.

BizzyCar’s developer surface includes engineering blog, support, and 7 more developer resources.

🌐 Visit website 📡 Source on GitHub

13.9/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0

0 APIs

CompanyAutomotiveRecall ManagementDealershipsMobile ServiceVehicle ServiceFleet ManagementSchedulingSaaS

Kin Score

Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0

Composite quality — 13.9/100 · emerging

Contract Quality 0.0 / 25

Developer Ergonomics 1.3 / 20

Commercial Clarity 6.8 / 20

Operational Transparency 0.0 / 13

Governance 0.0 / 12

Discoverability 5.7 / 10

Agent readiness — 0/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 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/bizzycar: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Get Started 1

Portal, sign-up, and the first successful call

Login

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Source (apis.yml)

aid: bizzycar
name: BizzyCar
description: 'BizzyCar is a B2B SaaS platform for automotive dealerships that automates service recall management, customer
  outreach and mobile service. Founded in 2018 and headquartered in Saint Peters, Missouri, the company ingests VIN-level
  open-recall data from OEM partners, matches it against a dealer''s market area and DMS records, then uses AI-driven outreach
  (SMS, email, voice) to book service appointments and dispatch mobile service vans. Products include Recall Outreach, Recall
  Scout, Recall Radar, Service Engine, Mobile Service and Fleet IQ. BizzyCar is primarily an API *consumer* rather than an
  API producer: it ships pre-built connectors into dealer management systems (Dealertrack, DMS Plus, Open/Mate, Asbury, PBS,
  Tekion, Fortellis, Reynolds & Reynolds) and service schedulers (Xtime, TCC, DealerFX, Affinitiv, Update Promise), but publishes
  no public developer program, API reference or machine-readable contract of its own.'
image: https://www.bizzycar.com/hubfs/1.%201200x630.png
url: https://raw.githubusercontent.com/api-evangelist/bizzycar/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: stub
x-tier-reason: harvest
specificationVersion: '0.20'
created: '2026-08-07'
modified: '2026-08-07'
tags:
- Company
- Automotive
- Recall Management
- Dealerships
- Mobile Service
- Vehicle Service
- Fleet Management
- Scheduling
- SaaS
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/bizzycar-domain-security.yml
- type: Website
  url: https://www.bizzycar.com/
- type: Blog
  url: https://www.bizzycar.com/blog
- type: Support
  url: https://www.bizzycar.com/support
- type: Login
  url: https://www.portal.bizzycar.com/sign-in
- type: TermsOfService
  url: https://www.bizzycar.com/terms-and-conditions
- type: PrivacyPolicy
  url: https://www.bizzycar.com/privacy-policy
- type: LinkedIn
  url: https://www.linkedin.com/company/bizzycar
- type: LLMsTxt
  url: llms/bizzycar-llms.txt
x-enrichment:
  date: '2026-08-07'
  status: minimal
  artifacts_added: 3
  pass: local-v1
x-coverage:
  state: none
  reason: no-developer-program
  detail: api.bizzycar.com is live but is BizzyCar's own application backend, not a product — every contract path (/openapi.json,
    /swagger.json, /api-docs, /graphql) returns the app's Rails JSON 404 envelope, none of the 238 URLs in the sitemap is
    a developer, docs or API page, and there is no bizzycar GitHub org or package on any registry; BizzyCar sells the DMS
    connectors it consumes, not an API it exposes.
  evidence:
  - url: https://api.bizzycar.com/openapi.json
    status: 404
  - url: https://api.bizzycar.com/graphql
    status: 404
  - url: https://www.bizzycar.com/sitemap.xml
    status: 200
  - url: https://api.github.com/orgs/bizzycar
    status: 404
  checked: '2026-08-07'