Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Coyote Logistics website screenshot

Coyote Logistics

Coyote Logistics is a global third-party logistics (3PL) provider and freight brokerage platform, now part of RXO, offering REST APIs for truckload capacity, less-than-truckload (LTL) shipping, freight quoting, shipment tracking, load management, customs brokerage, and supply chain visibility. Originally founded in 2006 and acquired by UPS in 2015, Coyote was subsequently acquired by RXO in 2024. The CoyoteGO API platform serves both shippers and carriers, providing real-time freight quotes, live tracking updates, and load booking capabilities. The API uses OAuth 2.0 client credentials flow and is backed by a network of 100,000 carriers serving 15,000 customers. Integration is available at no additional cost for shippers and carriers working with Coyote, with native connectors to leading TMS, WMS, and ERP systems.

agent aware

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Coyote Logistics the way a machine reads it — 136 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Coyote Logistics scores 51.8/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 51.8/100 · developing
Contract Quality 13.9 / 25
Developer Ergonomics 2.2 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 6.8 / 13
Governance 8.8 / 12
Discoverability 10.0 / 10
Agent readiness — 39/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
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 0 / 4
Consent & Bot Identity 0 / 3

How we profile Coyote Logistics

Each block below is one kind of artifact we hold for Coyote Logistics. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 9

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

CoyoteGO API

The primary REST API for Coyote Logistics enabling shippers and carriers to integrate freight operations directly into their TMS, WMS, ERP, or accounting systems. Provides real-...

Coyote Logistics Associated Entities API API

The Associated Entities API API from Coyote Logistics — 1 operation(s) for associated entities api.

Coyote Logistics Carrier - Available Load APIs API

The Carrier - Available Load APIs API from Coyote Logistics — 2 operation(s) for carrier - available load apis.

Coyote Logistics Carrier - Booking APIs API

The Carrier - Booking APIs API from Coyote Logistics — 2 operation(s) for carrier - booking apis.

Coyote Logistics Carrier - Offer APIs API

The Carrier - Offer APIs API from Coyote Logistics — 4 operation(s) for carrier - offer apis.

Coyote Logistics Document APIs API

The Document APIs API from Coyote Logistics — 2 operation(s) for document apis.

Coyote Logistics Shipper - Quoting APIs API

The Shipper - Quoting APIs API from Coyote Logistics — 2 operation(s) for shipper - quoting apis.

Coyote Logistics Shipper - Shipment APIs API

The Shipper - Shipment APIs API from Coyote Logistics — 4 operation(s) for shipper - shipment apis.

Coyote Logistics Shipper - Tracking APIs API

The Shipper - Tracking APIs API from Coyote Logistics — 4 operation(s) for shipper - tracking apis.

Scroll within the panel for all 9 ·

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Coyote Plans Pricing

3 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Coyote Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Apis Context

0 classes · 0 properties

JSON-LD

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Coyote Logistics API Rules

5 rules · 3 warnings

SPECTRAL

JSON Schema 96

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

Accessorial

2 properties

JSON SCHEMA

Address

6 properties

JSON SCHEMA

Appointment

4 properties

JSON SCHEMA

AppointmentDate

2 properties

JSON SCHEMA

AssociatedEntity

2 properties

JSON SCHEMA

AvailableLoad

4 properties

JSON SCHEMA

AvailableLoadsFilterMode

0 properties

JSON SCHEMA

AvailableLoadsRequest

4 properties

JSON SCHEMA

BookingConflict

4 properties

JSON SCHEMA

BookingRequest

2 properties

JSON SCHEMA

BookingRequestStatus

4 properties

JSON SCHEMA

BookingStatus

0 properties

JSON SCHEMA

CarrierQuote

12 properties

JSON SCHEMA

Commodity

11 properties

JSON SCHEMA

Contact

5 properties

JSON SCHEMA

CurrencyType

0 properties

JSON SCHEMA

Customer

2 properties

JSON SCHEMA

DestinationRequirements

8 properties

JSON SCHEMA

Dimension

2 properties

JSON SCHEMA

Distance

2 properties

JSON SCHEMA

DocumentRequest

4 properties

JSON SCHEMA

DriverWorkType

0 properties

JSON SCHEMA

Enums_Currency

0 properties

JSON SCHEMA

Enums_CurrencyType

0 properties

JSON SCHEMA

Enums_DimensionUnit

0 properties

JSON SCHEMA

Enums_DistanceUnit

0 properties

JSON SCHEMA

Enums_DocumentExtensionType

0 properties

JSON SCHEMA

Enums_DocumentType

0 properties

JSON SCHEMA

Enums_EquipmentType

0 properties

JSON SCHEMA

Enums_FreightClass

0 properties

JSON SCHEMA

Enums_LengthUnitType

0 properties

JSON SCHEMA

Enums_LimitedAccessType

0 properties

JSON SCHEMA

Enums_MultipleNumberType

0 properties

JSON SCHEMA

Enums_WeightType

0 properties

JSON SCHEMA

Enums_WeightUnitType

0 properties

JSON SCHEMA

EquipmentAttributes

33 properties

JSON SCHEMA

EquipmentDetails

6 properties

JSON SCHEMA

EquipmentType

0 properties

JSON SCHEMA

Facility

3 properties

JSON SCHEMA

GenericAttributeItem

2 properties

JSON SCHEMA

GeoCoordinates

2 properties

JSON SCHEMA

GeoLocation

2 properties

JSON SCHEMA

HazMatClass

0 properties

JSON SCHEMA

HazMatProperties

3 properties

JSON SCHEMA

Load

2 properties

JSON SCHEMA

LoadAttributes

49 properties

JSON SCHEMA

LoadBuildStatus

0 properties

JSON SCHEMA

LoadCommodity

24 properties

JSON SCHEMA

LoadDetail

8 properties

JSON SCHEMA

LoadDetails

8 properties

JSON SCHEMA

LoadEquipmentRequirement

2 properties

JSON SCHEMA

LoadEquipmentRequirementType

0 properties

JSON SCHEMA

LoadRequestStatus

4 properties

JSON SCHEMA

LoadRequirement

2 properties

JSON SCHEMA

LoadRequirementType

0 properties

JSON SCHEMA

LoadSearchResult

4 properties

JSON SCHEMA

LoadStop

4 properties

JSON SCHEMA

LoadStopAttributes

86 properties

JSON SCHEMA

LoadStopLocationInfo

3 properties

JSON SCHEMA

LoadStopProgress

5 properties

JSON SCHEMA

LoadStopRequirement

2 properties

JSON SCHEMA

LoadStopRequirementType

0 properties

JSON SCHEMA

Location

3 properties

JSON SCHEMA

LocationData

4 properties

JSON SCHEMA

LocationStatus

4 properties

JSON SCHEMA

LtlLocationData

4 properties

JSON SCHEMA

LTLSpotQuote

2 properties

JSON SCHEMA

LTLSpotQuoteRequest

9 properties

JSON SCHEMA

Milestone

5 properties

JSON SCHEMA

Mode

0 properties

JSON SCHEMA

OfferDetails

5 properties

JSON SCHEMA

OfferRequest

4 properties

JSON SCHEMA

OfferStatus

0 properties

JSON SCHEMA

OriginRequirements

6 properties

JSON SCHEMA

PackagingType

0 properties

JSON SCHEMA

PagedAvailableLoads

2 properties

JSON SCHEMA

Pagination

3 properties

JSON SCHEMA

Radius

2 properties

JSON SCHEMA

Rate

2 properties

JSON SCHEMA

RateCode

0 properties

JSON SCHEMA

RateItem

6 properties

JSON SCHEMA

ReferenceNumber

2 properties

JSON SCHEMA

SpotQuote

9 properties

JSON SCHEMA

SpotQuoteRequest

12 properties

JSON SCHEMA

StopDetail

2 properties

JSON SCHEMA

StopDetails

5 properties

JSON SCHEMA

StopType

0 properties

JSON SCHEMA

Summary

5 properties

JSON SCHEMA

Temperature

2 properties

JSON SCHEMA

TemperatureSettings

3 properties

JSON SCHEMA

TemperatureSettingType

0 properties

JSON SCHEMA

TemperatureUnit

0 properties

JSON SCHEMA

TimeSpan

11 properties

JSON SCHEMA

TrackingAddress

7 properties

JSON SCHEMA

Unit

0 properties

JSON SCHEMA

Weight

2 properties

JSON SCHEMA

Scroll within the panel for all 96 ·

Examples 24

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Scroll within the panel for all 24 ·

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Coyote Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Coyote Agentic Access

22 operations · 11 acting

22 operations · 11 acting

AGENTIC

Resources

Every other property we hold for Coyote Logistics — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/coyote · machine-readable index on apis.io