For AI agents & fleet systems

Your agent can book us directly.

If you run fleet ops with an AI assistant — Claude, ChatGPT, a dispatch copilot, or your own automation — it can check coverage, explain how pricing works, and book a mobile diesel mechanic for your operators through our JSON API. No phone call, no web form, no CAPTCHA.

OpenAPI spec llms.txt

Endpoints

GET/api/v1/services/Service catalog (all diagnose-first pricing)
GET/api/v1/coverage/?lat=&lng=Is this location covered? Nearest market + corridors
POST/api/v1/quote/How pricing works for a service — no estimate before diagnosis
POST/api/v1/bookings/Create a booking — supports Idempotency-Key header
GET/api/v1/bookings/{id}/Live status: received → dispatched → en_route → on_site → complete
POST/api/v1/bookings/{id}/cancel/Cancel before dispatch

Connect over MCP

Remote MCP server, streamable HTTP, no auth. Eight tools: list_services, check_coverage, how_pricing_works, prepare_repair_request, dispatch_desk, book_repair, get_booking_status, cancel_booking. Bookings are accepted in the Phoenix, AZ metro only today; Chicago and Detroit are launching next. Works in Claude, ChatGPT, Cursor, Codex, or any MCP client.

// Claude Desktop / Cursor / Codex — mcp config
{
  "mcpServers": {
    "mobile-diesel-usa": {
      "url": "https://mobiledieselusa.com/api/mcp/mcp"
    }
  }
}

// Claude Code
claude mcp add --transport http mobile-diesel-usa https://mobiledieselusa.com/api/mcp/mcp

Or use the CLI

Agent-native CLIs printed with the CLI Printing Press — JSON output, --agent mode, local sync + offline search. mdusa for the national network, azmdr for AZ Mobile Diesel Repair (Phoenix). Each ships its own MCP server too.

mdusa coverage --city Phoenix --agent
mdusa quote --service-id aftertreatment-dpf --urgency emergency --agent
mdusa bookings create --service-id aftertreatment-dpf --driver-phone +1XXXXXXXXXX   --location-city Phoenix --location-notes "I-10 WB shoulder exit 143"   --symptom "derate, DPF light" --fleet-company "Acme" --po-number PO-88231 --agent
mdusa bookings get-status BOOKING_ID --agent

# source + build instructions
https://github.com/Btheriot83/mobile-diesel-usa/tree/main/cli

Book a repair in two calls (raw API)

# 1. Pricing policy (optional — there is no estimate before diagnosis)
curl -s -X POST https://mobiledieselusa.com/api/v1/quote/ \
  -H "Content-Type: application/json" \
  -d '{"service_id":"engine-diagnostics","urgency":"emergency",
       "location":{"lat":33.4484,"lng":-112.074}}'

# 2. Book it
curl -s -X POST https://mobiledieselusa.com/api/v1/bookings/ \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: your-unique-key-123" \
  -d '{"service_id":"engine-diagnostics",
       "symptom":"Check engine light, derate, low power on I-10",
       "urgency":"emergency",
       "location":{"lat":33.4484,"lng":-112.074,"notes":"Westbound shoulder near exit 143"},
       "truck":{"year":2020,"make":"Freightliner","model":"Cascadia","engine":"DD15"},
       "unit_number":"4412","driver_name":"J. Smith","driver_phone":"+1XXXXXXXXXX",
       "fleet_company":"Acme Logistics","po_number":"PO-88231",
       "contact_email":"ops@acmelogistics.com"}'

# 3. Poll status / give the driver the track_url from the response
curl -s https://mobiledieselusa.com/api/v1/bookings/BOOKING_ID/

No payment through the API

Bookings are created with a PO number and driver contact. Payment settles with dispatch the usual way — your agent never touches card data.

A human confirms every job

Dispatch confirms with the driver by phone/SMS before a mechanic rolls. Your agent books it; a human closes the loop with the person standing next to the truck.

Errors tell you what to do next

Every 4xx/5xx response includes a next_step field written for agents. Retries are safe with an Idempotency-Key.

Building an integration, want higher rate limits, or need fleet API keys? Email help@mobiledieselusa.com or call (602) 456-9071.