Fleet Commerce Extension

What Is Fleet Commerce

ACP v1.0 was designed for human-initiated consumer commerce: a person begins a conversation, an AI agent captures intent, and a lead flows to a dealership's CRM. Every object in the base spec — lead, conversation, transaction — assumes a human consumer as the initiating party.

The Fleet Commerce Extension addresses a fundamentally different commerce pattern: machine-initiated service demand. An autonomous or connected vehicle detects a maintenance condition through its onboard systems, generates a structured ACP envelope identifying the vehicle, its health state, and the work required, and transmits that envelope directly to a dealership's service system — with no human scheduler, no phone call, and no service advisor involved in the initiation.

This is the protocol seam between autonomous vehicle operations and the dealer service network. It defines how machines become first-class commerce participants in automotive retail.

When to Use Fleet Envelopes

Fleet envelopes and consumer envelopes may coexist in the same dealership system. A conformant receiver must route them independently based on the presence of fleet vs lead at the top level.

Architecture

The vehicle agent is a first-class ACP participant with its own identity, odometer state, and event stream. The protocol layer validates the envelope, enforces the fleet pricing agreement, and writes an append-only audit record before the envelope reaches dealership systems. The confirmation loop closes with an ACP delta transmitted back to the originating fleet operator.

Fleet vs Consumer Envelope Structure

A fleet envelope is detected by the receiver via the presence of fleet at the top level. Receivers must not require lead, transaction, or conversation when fleet is present. The JSON Schema enforces mutual exclusivity: fleet and lead must not coexist in the same snapshot envelope.

fleet — Fleet Identity REQUIRED in fleet envelopes NEW v1.1

Identifies the fleet operator and the specific vehicle originating this envelope. Replaces lead when the initiating party is non-human. Producers must include operator_id, vehicle, and health.

fleet.vehicle REQUIRED

fleet.health REQUIRED

Health Severity Levels

service_request — Commerce State REQUIRED in fleet envelopes NEW v1.1

Models the lifecycle of a machine-initiated service event from detection through invoice close. Replaces transaction in fleet envelopes. Producers must include id, type, stage, and initiated_by.

Service Request Stages

Stage progression is non-linear. A scheduled appointment may revert to dispatched if the dealer cancels. The closed stage is terminal — producers must create a new service request if follow-up work is required.

Service Request Types

service_request.work_items[]

service_request.appointment

service_request.invoice

New source.agent_type Values NEW v1.1

The following values are added to the source.agent_type enum in v1.1. Existing values from v1.0 remain valid.

New Standard Event Types NEW v1.1

Six new standard event types added in v1.1. All existing v1.0 event types remain valid. Receivers conformant with v1.0 must ignore these without error per forward-compatibility rules.

New Intent Types NEW v1.1

These intent types may appear in lead.intents[] when a fleet event also involves a human follow-up (e.g., a fleet manager reviewing a service request). In pure machine-initiated envelopes, the intents array is typically absent.

Full Fleet Envelope Example

A complete snapshot envelope for a predictive maintenance event on an autonomous vehicle.

{
  "acp": {
    "version": "1.1.0",
    "protocol": "acp",
    "generated_at": "2026-04-06T08:14:22Z",
    "envelope_id": "acp_1744027200_f9k3m1",
    "parent_envelope_id": null
  },

  "source": {
    "provider": "AutomotiveAI",
    "agent_type": "vehicle_agent",   // NEW in v1.1
    "channel": "telematics",
    "session_id": "vtl_waymo_vin5k2_20260406"
  },

  "dealership": {
    "id": "dealer_costa_mesa_001",
    "name": "Pacific Jaguar Land Rover",
    "dms_provider": "dealer_center",
    "timezone": "America/Los_Angeles"
  },

  "fleet": {                                 // NEW in v1.1 — replaces "lead"
    "operator_id": "waymo_fleet_west_001",
    "operator_name": "Waymo LLC",
    "contract_tier": "enterprise",
    "dispatch_priority": "normal",
    "vehicle": {
      "vin": "SALYB2EX3LA123456",
      "year": 2023,
      "make": "Jaguar",
      "model": "I-PACE",
      "odometer": 48247,
      "telematics_source": "waymo_os_v4.2",
      "autonomous_level": 4,
      "fleet_unit_id": "WM-LA-0047"
    },
    "health": {
      "severity": "predictive",
      "health_score": 71,
      "dtc_codes": [],
      "systems_flagged": ["brake_pads_rear", "cabin_air_filter"],
      "predicted_failure_window_days": 12,
      "last_service_date": "2025-10-14"
    }
  },

  "service_request": {               // NEW in v1.1 — replaces "transaction"
    "id": "sr_1744027200_k8f2",
    "type": "predictive_maintenance",
    "stage": "dispatched",
    "initiated_by": "vehicle_agent",
    "last_updated": "2026-04-06T08:14:22Z",
    "fleet_pricing_agreement_id": "fpa_waymo_socal_2026",
    "loaner_required": false,
    "estimated_downtime_hours": 3.5,
    "work_items": [
      {
        "op_code": "BRK-PAD-REAR-IPACE",
        "description": "Rear brake pad replacement",
        "labor_hours": 1.5,
        "parts_required": true,
        "warranty_eligible": false
      },
      {
        "op_code": "FILTER-CABIN-IPACE",
        "description": "Cabin air filter replacement",
        "labor_hours": 0.5,
        "parts_required": true,
        "warranty_eligible": false
      }
    ],
    "appointment": {
      "requested_window_start": "2026-04-10T07:00:00-07:00",
      "requested_window_end": "2026-04-12T17:00:00-07:00",
      "scheduled_at": null,
      "bay_assigned": null,
      "status": "pending",
      "drop_off_method": "self_driving"
    },
    "invoice": {
      "status": "not_started",
      "fleet_adjusted_total": null,
      "closed_at": null
    }
  },

  "events": [
    {
      "type": "vehicle_health_detected",    // NEW in v1.1
      "timestamp": "2026-04-06T06:01:44Z",
      "data": {
        "systems": ["brake_pads_rear", "cabin_air_filter"],
        "severity": "predictive",
        "health_score_at_detection": 71
      }
    },
    {
      "type": "service_request_initiated",   // NEW in v1.1
      "timestamp": "2026-04-06T08:14:22Z",
      "data": {
        "service_request_id": "sr_1744027200_k8f2",
        "initiated_by": "vehicle_agent"
      }
    }
  ]
}

Dealer Confirmation Delta

When the dealer schedules the appointment, they transmit an ACP delta back to the fleet operator. This closes the loop — the vehicle agent receives confirmation without any human-to-human communication.

{
  "acp": {
    "version": "1.1.0",
    "protocol": "acp",
    "generated_at": "2026-04-06T11:30:00Z",
    "envelope_id": "acp_1744038600_d2x9",
    "parent_envelope_id": "acp_1744027200_f9k3m1"
  },
  "events": [
    {
      "type": "appointment_confirmed",
      "timestamp": "2026-04-06T11:30:00Z",
      "data": {
        "service_request_id": "sr_1744027200_k8f2",
        "scheduled_at": "2026-04-11T09:00:00-07:00",
        "bay_assigned": "BAY-4",
        "ro_number": "RO-2026-04847",
        "stage": "scheduled"
      }
    },
    {
      "type": "ro_opened",                         // NEW in v1.1
      "timestamp": "2026-04-06T11:30:00Z",
      "data": {
        "ro_number": "RO-2026-04847",
        "dms_provider": "dealer_center"
      }
    }
  ]
}

Fleet Pricing Agreements

The fleet_pricing_agreement_id field references a pre-negotiated contract stored in the receiving dealer's system. When present, the dealer's enforcement layer applies fleet labor rates and parts pricing automatically — no human price negotiation occurs.

A conformant receiver receiving a fleet_pricing_agreement_id it does not recognize must respond with error code UNKNOWN_PRICING_AGREEMENT (HTTP 422) rather than falling back to retail pricing silently.

Recall Handling

When service_request.type is "recall_action", the following additional constraints apply:

Conformance

Systems implementing the Fleet Commerce Extension may claim conformance as "ACP v1.1 Fleet Producer" or "ACP v1.1 Fleet Receiver" if they meet the following requirements in addition to the base v1.0 conformance requirements.

Fleet Producer Conformance

A conformant fleet producer must:

Fleet Receiver Conformance

A conformant fleet receiver must:

Security Considerations

Additional Error Codes NEW v1.1

The following error codes are added in v1.1 for fleet-specific failure conditions.