slug: qargo provider: Qargo generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Transportation & Logistics min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 3 edges: - tag: API / Resource spec_file: qargo-api-resource-api-openapi.yml capability_id: BC-2430 capability_id_l1: BC-2430 capability_name: Fleet & Mobile Asset Management confidence: 0.8 evidence: schemas TruckResourceOutput, VanResourceOutput, TrailerProperties-Output, ChassisProperties-Output, VehicleDocumentTypes, ResourceUnavailabilityOutput; ops Create Resource / List Resource Unavailabilities / List Resource Validities reason: CRUD over trucks, vans, trailers, chassis and containers with unavailability and validity windows is master management of mobile transport assets. Which sub-capability (equipment pool vs certification vs utilisation) is not clear enough, so L1 only. - tag: Use case / Fleet dispatch spec_file: qargo-use-case-fleet-dispatch-api-openapi.yml capability_id: BC-2420.10 capability_id_l1: BC-2420 capability_name: Dispatch Management confidence: 0.78 evidence: fleet-dispatch-payload Fleet Dispatch Payload; POST /v1/webhook/fleet-status-update External Status Update From A Fleet Application; schemas FleetDispatchTemplate, FleetDispatchStatusUpdate, Signature reason: Dispatch payloads are pushed to an external fleet/driver application and execution statuses, documents and signatures flow back — assignment of loads to vehicles and drivers, i.e. dispatch management. - tag: API / Trip spec_file: qargo-api-trip-api-openapi.yml capability_id: BC-2420 capability_id_l1: BC-2420 capability_name: Transport Operations Management confidence: 0.72 evidence: GET /v1/trips/trip/{trip_id} Get Trip By Id; GET /v1/trips/trip/{trip_id}/costs; schemas TripOutput, TripStatusOutput, ResourceAllocation-Output, StopDepotOutput, Incident reason: A trip with allocated resources, stops, status and incidents is the execution unit of a road transport movement, so transport operations execution. Read-only scope and the cost endpoint leave the specific sub-capability (dispatch vs line-haul) undetermined.