86 Repairs

86 Repairs is a restaurant equipment repair and maintenance (R&M) management platform founded in 2018 in Chicago by Daniel Estrada and Joe Gallagher. It manages the repair lifecycle for restaurant operators — 24/7 intake and troubleshooting, warranty verification, dispatch to a vetted service provider network, preventative maintenance scheduling, equipment and asset inventory, invoice assurance and R&M spend analytics — and is used by operators and franchisees of brands including McDonald's, Wendy's, Taco Bell, Jersey Mike's, Five Guys and Wingstop. The product is delivered as an end-user web portal (portal.86repairs.com) and iOS/Android mobile apps, backed by a private NestJS service at eightysix-api.86repairs.com; it is not offered as a developer platform. Parts Town, the Addison, Illinois OEM foodservice parts distributor, acquired 86 Repairs in June 2026 to connect parts availability with repair and service workflows. As of this profile 86 Repairs publishes no public API: no developer portal, no API reference, no OpenAPI/AsyncAPI/GraphQL contract, no SDK or package on any public registry, no webhook catalog, no MCP server and no A2A agent card were found on any host it controls.

86 Repairs is profiled on the APIs.io network. Tagged areas include Restaurant, Food Service, Facilities Management, Maintenance, and Field Service Management.

86 Repairs’ developer surface includes engineering blog, support, YouTube channel, and 11 more developer resources.

🌐 Visit website 📡 Source on GitHub
11.5/100 emerging ▬ flat Agent 5/100 agent aware Front door AI 3/6 light Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
0 APIs
RestaurantFood ServiceFacilities ManagementMaintenanceField Service ManagementEquipmentAsset ManagementHospitalityVendor ManagementNo Developer Program

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
Composite quality — 11.5/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 1.2 / 17
Access Clarity 4.7 / 17
Operational Transparency 0.0 / 11
Contract Governance 0.0 / 10
Discoverability 4.1 / 9
Regulatory Posture 2.1 / 15
Agent readiness — 5/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
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 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
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/86repairs: 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 →

Pricing Plans 1

Published pricing tiers and plan structures.

86Repairs Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

86Repairs Rate Limits

0 limits

RATE LIMITS

Security Posture 1

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

86Repairs Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login
Login

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Build 1

SDKs, sample code, and the tooling you integrate with

Packages
Packages

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity

Learn 1

Tutorials, courses, talks, and written guidance

YouTube
YouTube

Operate 3

Status, limits, changes, and where to get help

RateLimits
RateLimits
 Support
Support
 HelpCenter
HelpCenter

Commercial 3

Pricing, plans, and the legal terms of use

Plans
Plans
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 3

The organization behind the API

Website
Website
 Blog
Blog
 LinkedIn
LinkedIn

Source (apis.yml)

apis.yml Raw ↑ 
aid: 86repairs
name: 86 Repairs
url: https://raw.githubusercontent.com/api-evangelist/86repairs/refs/heads/main/apis.yml
type: Index
image: https://www.86repairs.com/hubfs/86%20Repairs%20for%20Facilities%20Managers%20%281200%20x%20630%20px%29%20%281%29.png
description: '86 Repairs is a restaurant equipment repair and maintenance (R&M) management platform founded in 2018 in Chicago
  by Daniel Estrada and Joe Gallagher. It manages the repair lifecycle for restaurant operators — 24/7 intake and troubleshooting,
  warranty verification, dispatch to a vetted service provider network, preventative maintenance scheduling, equipment and
  asset inventory, invoice assurance and R&M spend analytics — and is used by operators and franchisees of brands including
  McDonald''s, Wendy''s, Taco Bell, Jersey Mike''s, Five Guys and Wingstop. The product is delivered as an end-user web portal
  (portal.86repairs.com) and iOS/Android mobile apps, backed by a private NestJS service at eightysix-api.86repairs.com; it
  is not offered as a developer platform. Parts Town, the Addison, Illinois OEM foodservice parts distributor, acquired 86
  Repairs in June 2026 to connect parts availability with repair and service workflows. As of this profile 86 Repairs publishes
  no public API: no developer portal, no API reference, no OpenAPI/AsyncAPI/GraphQL contract, no SDK or package on any public
  registry, no webhook catalog, no MCP server and no A2A agent card were found on any host it controls.'
tags:
- Restaurant
- Food Service
- Facilities Management
- Maintenance
- Field Service Management
- Equipment
- Asset Management
- Hospitality
- Vendor Management
- No Developer Program
tags_raw:
- Restaurants
- Foodservice
- Facilities Management
- Maintenance
- Field Service Management
- Equipment
- Asset Management
- Hospitality
- Vendor Management
- No Developer Program
created: '2026-09-05'
modified: '2026-09-05'
specificationVersion: '0.20'
x-type: company
x-source: harvest:secondary-market
apis: []
common:
- type: DomainSecurity
  url: security/86repairs-domain-security.yml
- type: Website
  url: https://www.86repairs.com/
- type: Packages
  url: packages/86repairs-packages.yml
- type: LLMsTxt
  url: llms/86repairs-llms.txt
- type: Plans
  url: plans/86repairs-plans-pricing.yml
- type: RateLimits
  url: rate-limits/86repairs-rate-limits.yml
- type: Blog
  url: https://blog.86repairs.com/
- type: Support
  url: https://www.86repairs.com/customer-support
- type: HelpCenter
  url: https://intercom.help/86-repairs-customer-service/en/
- type: Login
  url: https://portal.86repairs.com/login
- type: TermsOfService
  url: https://www.86repairs.com/terms
- type: PrivacyPolicy
  url: https://www.86repairs.com/privacy
- type: LinkedIn
  url: https://www.linkedin.com/company/86repairs
- type: YouTube
  url: https://www.youtube.com/@86Repairs
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-tier: profiled
x-tier-reason: 'enrichment pass 2026-09-05: full STEP 0b contract discovery run against every host including the portal-derived
  API host eightysix-api.86repairs.com; no public API surface found'
x-enrichment:
  date: '2026-09-05'
  status: minimal
  artifacts_added: 6
  pass: local-v3
x-coverage:
  state: none
  reason: no-developer-program
  detail: 86 Repairs ships its repair-management product only as an end-user web portal and mobile apps — no developer subdomain
    resolves (docs., developer., developers.86repairs.com all fail DNS), the sitemap lists no API, developer or integrations
    page, and the private portal backend at eightysix-api.86repairs.com returns a real JSON 404 for /openapi.json, /swagger.json,
    /graphql and every .well-known path while serving only /health.
  evidence:
  - url: https://eightysix-api.86repairs.com/openapi.json
    status: 404
  - url: https://eightysix-api.86repairs.com/graphql
    status: 404
  - url: https://eightysix-api.86repairs.com/health
    status: 200
  - url: https://docs.86repairs.com/
    status: 0
  - url: https://developer.86repairs.com/
    status: 0
  - url: https://api.86repairs.com/
    status: 403
  - url: https://www.86repairs.com/sitemap.xml
    status: 200
  checked: '2026-09-05'

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/86repairs"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/86repairs/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/86repairs/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.

GitHub Google LinkedIn

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