Mitchell 1

Mitchell 1 is a division of Snap-on Incorporated providing repair information (ProDemand, TruckSeries) and shop management software (Manager SE, SocialCRM) to independent auto repair shops. Mitchell 1 is a legacy enterprise software provider, not an API-first company - it has no public, self-serve REST API reference. It does operate a gated Web-Intent / Data API integration program for approved third-party partners (shop management systems, CRM, parts and marketing platforms) to embed or link into ProDemand labor, parts, and maintenance data, fronted by a token-based (TAPE) auth flow and an Intent Registry discovery service. Access requires submitting an integration request, a Mitchell 1 review (roughly two weeks), and a signed partner agreement; no public API reference, OpenAPI document, or SDK is published. Note - Mitchell 1 (mitchell1.com, Snap-on) is a distinct company from Mitchell International (mitchell.com, part of Enlyte) - the two share a historical "Mitchell" lineage but are separately owned; Mitchell International's public developer.mitchell.com RepairCenter API belongs to the other company and is out of scope here.

Mitchell 1 publishes 3 APIs on the APIs.io network. Tagged areas include Automotive, Repair Information, Shop Management, Labor Guide, and VIN Decode.

Mitchell 1’s developer surface includes documentation, engineering blog, and 4 more developer resources.

🌐 Visit website 📡 Source on GitHub
15.9/100 emerging ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
AccessPaid
3 APIs
AutomotiveRepair InformationShop ManagementLabor GuideVIN DecodeSnap-onPartner APIGated

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 15.9/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 2.2 / 20
Commercial Clarity 6.3 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 7.4 / 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/mitchell1: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 3

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

Mitchell 1 Intent Registry Discovery API

Discovery endpoint (GET api/service/v1/discovery) that a partner application calls on startup to resolve the current RESTful URI patterns for the Web-Intent resources it needs, ...

Mitchell 1 Intent Resolve API

Resolve endpoint (POST api/intent/v1/resolve) used to securely look up where a specific Web-Intent should be routed, as part of the TAPE (transfer application public extension) ...

Mitchell 1 Integration Script Services API

Two GET endpoints (api/script/v1/integrationclient and api/script/v1/integrationserver) listed in the sandbox Intent Registry index with no published documentation beyond their ...

Pricing Plans 1

Published pricing tiers and plan structures.

Mitchell1 Plans Pricing

4 plans

PLANS

Security Posture 1

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

Mitchell1 Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Documentation
Documentation

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity

Commercial 1

Pricing, plans, and the legal terms of use

Plans
Plans

Company 3

The organization behind the API

LinkedIn
LinkedIn
 Website
Website
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: mitchell1
url: https://raw.githubusercontent.com/api-evangelist/mitchell1/refs/heads/main/apis.yml
name: Mitchell 1
kind: company
description: Mitchell 1 is a division of Snap-on Incorporated providing repair information (ProDemand, TruckSeries) and shop
  management software (Manager SE, SocialCRM) to independent auto repair shops. Mitchell 1 is a legacy enterprise software
  provider, not an API-first company - it has no public, self-serve REST API reference. It does operate a gated Web-Intent
  / Data API integration program for approved third-party partners (shop management systems, CRM, parts and marketing platforms)
  to embed or link into ProDemand labor, parts, and maintenance data, fronted by a token-based (TAPE) auth flow and an Intent
  Registry discovery service. Access requires submitting an integration request, a Mitchell 1 review (roughly two weeks),
  and a signed partner agreement; no public API reference, OpenAPI document, or SDK is published. Note - Mitchell 1 (mitchell1.com,
  Snap-on) is a distinct company from Mitchell International (mitchell.com, part of Enlyte) - the two share a historical "Mitchell"
  lineage but are separately owned; Mitchell International's public developer.mitchell.com RepairCenter API belongs to the
  other company and is out of scope here.
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/mitchell1.png
tags:
- Automotive
- Repair Information
- Shop Management
- Labor Guide
- VIN Decode
- Snap-on
- Partner API
- Gated
created: '2026-07-04'
modified: '2026-07-25'
specificationVersion: '0.19'
apis:
- aid: mitchell1:mitchell1-intent-registry-discovery-api
  name: Mitchell 1 Intent Registry Discovery API
  tags:
  - Discovery
  - Web-Intent
  - Integration
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://testintents.mitchell1.com/Help/Api
  baseURL: https://testintents.mitchell1.com/api
  properties:
  - url: https://mitchell1.com/resources/api-request/
    type: Documentation
  - url: https://testintents.mitchell1.com/Help/Api
    type: APIReference
  description: Discovery endpoint (GET api/service/v1/discovery) that a partner application calls on startup to resolve the
    current RESTful URI patterns for the Web-Intent resources it needs, rather than hardcoding them. Confirmed on Mitchell
    1's public sandbox API help index; production access requires an approved integration partner account.
- aid: mitchell1:mitchell1-intent-resolve-api
  name: Mitchell 1 Intent Resolve API
  tags:
  - Intents
  - Web-Intent
  - Authentication
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://testintents.mitchell1.com/Help/Api
  baseURL: https://testintents.mitchell1.com/api
  properties:
  - url: https://mitchell1.com/resources/api-request/
    type: Documentation
  - url: https://testintents.mitchell1.com/Help/Api
    type: APIReference
  description: Resolve endpoint (POST api/intent/v1/resolve) used to securely look up where a specific Web-Intent should be
    routed, as part of the TAPE (transfer application public extension) token flow that hands a partner application a token
    it presents to the Secure Intents website to consume ProDemand labor, parts, fluids, and maintenance intents.
- aid: mitchell1:mitchell1-integration-script-services-api
  name: Mitchell 1 Integration Script Services API
  tags:
  - Scripts
  - Integration Client
  - Integration Server
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://testintents.mitchell1.com/Help/Api
  baseURL: https://testintents.mitchell1.com/api
  properties:
  - url: https://testintents.mitchell1.com/Help/Api
    type: APIReference
  description: Two GET endpoints (api/script/v1/integrationclient and api/script/v1/integrationserver) listed in the sandbox
    Intent Registry index with no published documentation beyond their names; they appear to serve client- and server-side
    integration script assets for embedding Mitchell 1 Web-Intent flows inside a partner shop management system. Listed here
    for completeness, not confirmed behavior.
common:
- type: DomainSecurity
  url: security/mitchell1-domain-security.yml
- type: LinkedIn
  url: https://www.linkedin.com/company/mitchell-1/
- type: Website
  url: https://mitchell1.com/
- type: Documentation
  url: https://mitchell1.com/resources/api-request/
- type: Plans
  url: plans/mitchell1-plans-pricing.yml
- url: https://mitchell1.com/feed/
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com