PartsTech
PartsTech is a web-based automotive parts and tire procurement platform for repair shops, tire shops and dealers, connecting more than 30,000 shops to 300+ aftermarket parts and tire suppliers across 30,000+ distribution locations through a single search, quote and ordering workflow. Founded by Greg Kirber and Erik St. Pierre and acquired by OEConnection (OEC) in 2025, PartsTech pairs its shop-facing web application with a partner-facing REST API — the PartsTech External API — used by 35+ shop management systems (SMS), point-of-sale and estimating vendors to embed parts search, VIN and license plate decoding, ACES/PCdb/VCdb taxonomy lookups, live wholesale pricing and availability, punchout carts, quoting, tire search, MOTOR and Mitchell 1 labor/maintenance content, order history and local inventory into their own software.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles PartsTech the way a machine reads it — 39 machine-readable artifacts across 2 APIs, 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 — PartsTech scores 53.4/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). 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.
Put this on your own site. The badge is drawn live from PartsTech'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/partstech/"
title="PartsTech on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/partstech.svg"
alt="PartsTech Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/partstech/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/partstech/"
title="PartsTech on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/partstech/card.svg"
alt="PartsTech 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 PartsTech
Each block below is one kind of artifact we hold for PartsTech. 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.
APIs 33
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
PartsTech Auth API
A valid JSON Web Token (JWT) is required to access API methods. A JWT access token must be included in the authorization header of each request in the following Bearer schema: `...
PartsTech Auto Connect API
Easy Registration & Auto-Connect API
PartsTech Brands API
Brands
PartsTech Callback Cart API
Callback
PartsTech Custom Cart API
Custom Cart
PartsTech Ex Permissions API
EX Permissions
PartsTech Local Inventory API
Local inventory
PartsTech Mitchell1 API
Vehicles
PartsTech Motor Maintenance Schedules API
Maintenance Schedules
PartsTech Motor Specifications API
Specifications
PartsTech Orders API
Orders
PartsTech Partner Orders API
Orders methods
PartsTech Parts API
Parts
PartsTech Pcdb API
Product Characteristics Database
PartsTech Punchout Cart API
Cart with Punchout
PartsTech Punchout Orders API
Punchout Orders
PartsTech Punchout Quote API
Quote Methods
PartsTech Quoting API
Quoting
PartsTech Search API
Search
PartsTech Session Cart API
Cart by Session
PartsTech Shops API
Shop methods
PartsTech Supplier Preferences API
Supplier Preferences
PartsTech Suppliers API
Supplier methods
PartsTech Tires API
Tires
PartsTech User API
User Methods
PartsTech Users API
Users methods
PartsTech Vcdb API
Vehicle Configuration Database
PartsTech Vin API
VIN Methods
Scroll within the panel for all 33 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
PartsTech MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Partstech Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Partstech Webhooks
ASYNCAPISecurity 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 PartsTech — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/partstech · machine-readable index on apis.io
This is an independent, third-party profile of PartsTech, 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.