01Service intent
A request arrives in natural language — from a customer, a booking surface, or an AI agent. JackRelay resolves it into a canonical service intent, without pretending to diagnose uncertain symptoms.
Automotive transaction infrastructure
JackRelay turns service requests into canonical offerings, pricing, quotes, availability, and appointments — one connection layer between repair shops and the software and AI agents that send them customers.
One canonical path — from a request in any language to a confirmed appointment.
Customers, apps, and AI assistants all ask for service differently. JackRelay gives them one canonical vocabulary — and executes each transaction the way your shop actually operates.
The canonical layer
From intent to appointment
Service intent
Shop discovery
Service offering
Price & quote
Availability
Appointment
A request arrives in natural language — from a customer, a booking surface, or an AI agent. JackRelay resolves it into a canonical service intent, without pretending to diagnose uncertain symptoms.
The intent is matched to shops and locations that offer the service, serve the customer’s area, and can actually work on that vehicle.
Every shop publishes its canonical offering: the service, its duration, and the vehicles it fits — versioned and shared across every demand source.
Prices stay canonical — exact, starting-at, range, or quote-required. When a job needs eyes on it first, JackRelay opens a quote request instead of guessing.
Slots come from authoritative sources only: platform-managed capacity or verified vendor availability. An empty calendar is never sold as open time.
The booking lands in the shop’s real workflow — direct confirmation where capacity exists, or a request the shop accepts. A request is never falsely confirmed.
For repair shops
The repair shop is the customer. Publish once, and every surface that sends you customers transacts against the same services, prices, and availability.
Front brake pad replacement · 75 min
“Check-engine light comes on after cold starts.”
Native JackRelay workflow
A shop can go from empty to fully bookable on JackRelay alone. Services, pricing, durations, hours, scheduling rules, and capacity are first-class platform configuration — not a fallback mode.
Native bookings are confirmed against capacity enforced by the database itself: concurrent requests cannot oversell a slot, and a crash can’t silently lose one.
Illustrative configuration — real shops configure their own rules.
Connection architecture
JackRelay routes every transaction through one canonical layer — and executes it wherever your shop actually operates.
AI assistants · apps · booking surfaces
Services, pricing, hours, and capacity configured directly in JackRelay. Implemented and tested against real PostgreSQL.
Bookings arrive as requests your shop accepts or declines. A request is never presented as confirmed.
Connect shop-management software once an official, verified integration exists. Until then, nothing is advertised as connected.
Approved external booking links where a provider contract allows — validated, never blind.
Vendor paths activate only with official contracts and a verified sandbox end-to-end. Provider state is product data — never a marketing claim.
Developers
Build against service intents, offerings, quotes, and appointments — never against vendor tenant IDs, credentials, or payload formats. Those stay behind the router.
POST /v1/service-intents
{
"service_request": { "description": "Front brake pads, 2019 Honda Accord" },
"vehicle": { "year": 2019, "make": "Honda", "model": "Accord" },
"search_area": { "postal_code": "43215", "country_code": "US" }
}
{
"id": "intent_8f2c41a9",
"status": "resolved",
"resolution": {
"service": { "code": "brake_pad_replacement", "name": "Brake Pad Replacement" },
"confidence": 0.94,
"transaction_mode": "instant_book",
"clarification_required": false
}
}
The example shows the platform’s actual wire format — snake_case throughout.
search_auto_service({
"service_request": { "description": "Battery won't hold a charge" },
"vehicle": { "year": 2020, "make": "Subaru", "model": "Outback" },
"search_area": { "city": "Columbus", "country_code": "US" }
})
search_auto_serviceResolve service intent without guessing at symptomsget_service_offeringsCanonical offerings for a resolved intentget_service_availabilitySlots with explicit source qualityrequest_service_quoteQuote request for quote-required workbook_auto_serviceThe booking the offering’s mode permitsget_appointmentRead a canonical appointmentcancel_appointmentConservative cancel with reconciliationreschedule_appointmentCapacity-safe rescheduleThe canonical MCP tool surface is implemented and tested. in progress authenticated production transport
BookMyJack
BookMyJack is where shops run on the platform: configure services and scheduling, review booking and quote requests, and follow every appointment through its state. It is a product surface of JackRelay — the same canonical data, in the shop’s hands.
Security
JackRelay is built as transaction infrastructure: authorization, isolation, and conservative semantics are part of the product, not an add-on.
Production hardening — identity provider, managed secrets, rate limits, and audit events — is in progress and will be stated here when it ships.
Configure once, publish once. Your services, prices, and availability become one canonical interface for every surface that sends you customers.
Already building? The public API begins at /v1/integration-providers.