50+
Active integrations
EusoTrip is the platform.
Plug in.
EusoTrip is the operating system for freight. Fifty-plus partner systems integrate with it through one open API — rate providers, fuel indices, safety registries, customs gateways, payment networks, identity, and the fleet-ops tools you already run. Authenticate with OAuth, push or subscribe via REST, tRPC, and signed webhooks, and EusoTrip composes the answer.
Integration footprint
12
Rate providers
10
Integration categories
3
API protocols
OAuth
2.0 authentication
±5%
Rate accuracy bar
Rate providers that pipe in.
These rate providers integrate with EusoTrip's quote engine via API. EusoTrip blends them on the way out — DAT at 0.50, SONAR at 0.25, HaulPay partner telemetry at 0.15, macro indices at 0.10 — and returns a single citation-backed quote with a confidence score. If the spread falls outside ±5% of DAT, the quote is flagged before it reaches your customer. If your data improves the blend, plug it in.
Industry ground truth.
Two DAT surfaces, pulled in parallel. Trendlines is the 15-day rolling spot benchmark; RateView is the contract-rate counterpart that tells us where shippers are signing paper. Together they're the primary base rate across all 12 rate providers — every other source is measured against them and shown with a ±5% confidence band. Delivered via ScrapingBee.
The leading signal.
National Truckload Index — the forward-looking daily benchmark that moves before the spot market does. We pull SONAR via ScrapingBee and index NTI shifts against DAT to catch inflection points before a shipper can.
Executed lanes, every day.
HaulPay is a third-party factoring partner that integrates with Eusorone. Every lane they settle posts back as a typed telemetry event — actual rates paid, actual days-to-pay, actual accessorial drift. That's the 0.15 weight in the blend, sourced from real money moved, not modeled estimates.
Context that holds the rest.
FRED producer prices (PCU484121), FRED transportation CPI (CPITRNS), BTS TSI, and the CASS Freight Index roll up into the structural layer of every quote. When the macro shifts, the blend shifts. When the macro is quiet, the blend defers to the real-time sources above.
We used to rely on Greenscreens and Uber Freight.
Both have been removed from the active blend. Greenscreens' coverage collapsed on cross-border lanes; Uber Freight's public rate endpoint was deprecated. We keep the adapters wired for regression testing and may re-enable them if their coverage returns. Replay logs before March 2026 still resolve those sources.
Macro indices, integrated.
Government and industry indices integrate with EusoTrip via direct API or signed pull. They become the long-horizon context that calibrates every quote — the structural layer short-term rate feeds miss.
General Freight Trucking PPI.
The Federal Reserve's producer price index for long-distance general-freight trucking. Monthly cadence. Pulled directly from the FRED API and indexed against the DAT base to produce a macro-adjusted rate delta.
Transportation CPI.
Consumer Price Index for transportation — the demand-side counterpart to PCU484121. Tells RIOS whether shippers are absorbing or passing through carrier price movements.
Transportation Services Index.
The U.S. Bureau of Transportation Statistics' monthly index of freight and passenger movement. A leading indicator on volume — RIOS uses it to detect early signs of a market expansion or contraction before spot rates catch up.
Shipments & expenditures.
CASS Information Systems' monthly read on freight volume and total spend. Provides the expenditure-side mirror to BTS volumes and calibrates the macro blend weight in each quote.
Fuel data, plugged into FSC.
These fuel-price providers integrate with EusoTrip's FSC schedule. Every surcharge that lands on a rate confirmation traces back to a primary government or retail index — no estimates, no stale numbers, every number cited.
U.S. Energy Information Administration.
National on-highway diesel weekly average plus all five PADD regions (East Coast, Midwest, Gulf Coast, Rocky Mountain, West Coast). Direct API pull, cached hourly, surfaced inside every FSC schedule.
50-state retail scrape.
AAA's state-level retail averages for regular, mid, premium, and diesel — scraped nightly across all fifty states. Used where a driver-side fuel card transaction needs a corroborating retail average.
Station-level prices (beta).
Station-level retail for our EusoFuel routing suggestions. Private beta — contact the partners team for access. Ships with the same cache-on-hour contract as AAA.
USDA AMS, integrated for produce.
The specialty-freight feed nobody else exposes. EusoTrip integrates the USDA truck-rate report on release and surfaces it inside the produce-lane rate model.
The specialty freight source of record.
The USDA Agricultural Marketing Service publishes a weekly truck rate report for produce lanes — reefer-sensitive commodity movements that DAT and SONAR under-sample. RIOS parses the PDF on release, normalizes by origin, destination, and commodity, and feeds it into the produce-lane rate model. This is the only marketing platform we know of that does this.
Compliance APIs, integrated.
Federal registries, customs gateways, and compliance standards integrate with EusoTrip's policy engine. Every carrier and load gets cross-checked before dispatch — HOS, safety, customs, NOM, FSMA, hazmat, trusted-trader status — and policy violations are surfaced upstream, not exported as reports.
Carrier safety, by DOT#.
Federal Motor Carrier Safety Administration SAFER system — DOT# lookup for authority, insurance, safety rating, and crash history. RIOS calls SAFER on every booking and refuses to dispatch to carriers whose authority has lapsed.
Hours of service, enforced at plan time.
Eusorone reads ELD records as source of truth. A load that would require a violation to deliver on time is never proposed — HOS conflicts are surfaced before dispatch, not discovered after.
Mexico customs, pre-validated.
Direct integration with Mexico's Ventanilla Única de Comercio Exterior. Pedimentos, certificates of origin, and USMCA preference claims are validated before the trailer crosses, not after.
Mexican Official Standards.
NOM labeling, commercial info, packaging, and transport compliance — checked automatically for every Mexico-bound load. Violations produce a replayable rejection, not a phone call from a broker.
California disclosure.
Commodity-based Prop 65 flagging for any load destined for California. The trigger list is versioned, replayable, and cites source.
Hazardous materials, truck and sea.
European ADR and IMO's International Maritime Dangerous Goods code for ocean containers. UN numbers, packing groups, and placarding rules encoded as first-class RIOS primitives.
Food Safety Modernization Act.
Sanitary transport rules for human and animal food. RIOS blocks reefer assignments that violate pre-cool or washout requirements.
CTPAT, FAST, OEA.
Trusted-trader program status validated per carrier and per driver. If a load requires FAST for a time-sensitive crossing, RIOS will not propose a carrier without it.
HaulPay. Factoring, integrated.
HaulPay is a third-party factoring partner that plugs straight into Eusorone. Credit checks, POD verification, QuickPay, NOA routing, reconciliation, and chargeback defense all run inside the same workspace your dispatcher already lives in. No exports, no portals, no ticket queue.
Credit check
Broker and shipper credit scored against the internal ledger plus external bureaus before the load is accepted. Credit failures block the book.
POD verification
Proof-of-delivery images captured in-app, OCR'd, and matched against the booking. A missing signature or a mismatched BOL blocks settlement.
QuickPay
Same-day funding on verified POD at a transparent discount. The rate is calculated per-carrier from payment-history telemetry, not a blanket number.
NOA routing
Notice-of-Assignment handled automatically for factored loads. Broker gets a single remittance address, carrier gets funded, no phone tag.
Reconciliation
Every deposit is matched to an invoice, every chargeback is tied to the event that triggered it, every accessorial is reconciled against the rate confirmation.
Chargeback defense
The disputes flow assembles an evidence bundle — POD, rate con, accessorial approvals, timestamps — and files on the carrier's behalf within the deadline window.
Card-present and ACH settlement.
Stripe v19.3.1 for card and bank-transfer rails where HaulPay isn't the counterparty. We don't touch raw PAN data — Stripe is the PCI boundary and everything upstream of it is tokenized.
Banking that integrates as native.
EusoBank plugs in alongside OTR Capital, Triumph, RTS, and Apex — pick the one you already use or switch to EusoBank for factoring, fuel advances, and settlement on the same ledger as the rest of the platform. One statement, one API, one source of truth.
Bring your stack. Or plug into ours.
Maintenance, banking, ELD, fuel cards, tracking, comms — whatever you run today plugs into Eusorone with a typed contract and a replayable event log. Or pick a partner from our network and skip the integration project entirely. Either way, the same ledger, the same audit log, the same policy engine.
Photo-driven maintenance, integrated.
Zeun plugs into Eusorone as the maintenance layer. Drivers upload a photo of a wheel, tire, or engine bay; Viga Photo AI classifies the component, Gemini diagnoses condition and recommends action, and the resulting work order posts to your dispatch board with no copy-paste between systems.
Banking that snaps in.
Plugs in alongside OTR Capital, Triumph, RTS, and Apex — keep your existing factoring relationship or switch to EusoBank for factoring advances, fuel advances, settlement, and statements on the same ledger. Regulated counterparty in the U.S. and Mexico.
The ELD with a brain.
Plugs in next to Geotab, Samsara, KeepTruckin, Motive, and Omnitracs — Eusorone reads from whichever you run. EusoELD itself ships FMCSA-compliant HOS with the policy engine on the device, so violations are prevented at the wheel rather than reported from the office.
Fuel cards that integrate.
Slots in alongside Comdata, EFS, WEX, and FleetOne, or run on EusoFuel directly — card-in-driver-pocket with real-time station routing, EIA- and GasBuddy-aware price targets, and the same authorization rules the dispatcher set in the app.
Visibility, plugged in.
Asset tracking across trucks, trailers, and containers. Reads from EusoELD and any carrier ELD API, then pushes clean data automatically into your customers' visibility platforms — project44, FourKites, MacroPoint — without a middleman.
Driver comms, routed.
SMS and voice for dispatcher-to-driver comms, integrated as a tenant-owned channel — solves the personal-phone problem with audit trails that live in the same evidence bundle as the load.
Built for integrations that don't drop messages.
Every integration on EusoTrip rides the same delivery contract — exactly-once semantics, signed payloads, replayable events. If your integration depends on it, the API guarantees it.
Signed event delivery.
HMAC-SHA256 signatures on every payload, exponential-backoff retries, and a circuit breaker that quarantines a failing endpoint without losing the queue position. Subscribe per event type, per tenant.
Re-fetch any event.
Every event has a permanent ID. POST it back to the replay endpoint and EusoTrip re-emits the original payload — same shape, same signature, same source citations — so your integration can recover from any outage.
Safe to retry.
Required on every mutating request. EusoTrip dedupes against the key for 24 hours so a network blip doesn't double-book a load or double-pay an invoice.
Per-token, per-tenant.
Limits scoped to the OAuth token and the tenant behind it. The X-RateLimit headers tell you exactly how much room is left, and we'll raise the ceiling on request.
Every call, timestamped.
Every API call is recorded with method, path, source IP, OAuth client, and outcome. Pull the log via API or stream it into your SIEM through the OpenTelemetry exporter.
Stable v1, telegraphed deprecations.
v1 is the contract you build against. Breaking changes ship as v2 and run in parallel; deprecations are announced 90 days before the lights go out.
Bring your IdP. Stream your events.
Authentication, geocoding, weather, and telemetry — integrations both inbound (your identity provider, your SIEM) and outbound (the geospatial and weather APIs EusoTrip enriches your data with).
Enterprise SSO.
Full OAuth 2.0 / OpenID Connect support. Bring your Okta, Entra, Auth0, or Google Workspace and federate. Tokens flow into the EusoTrip API with the tenant, role, and scope already attached.
Stream events to your SIEM.
EusoTrip exports traces, metrics, and audit logs via OTLP/HTTP. Point it at Datadog, New Relic, Honeycomb, or Grafana Cloud and your SIEM gets the same telemetry our oncall does — no Eusorone-side reconfiguration.
Geocoding, routing, distance.
EusoTrip integrates Google Maps for addresses, polylines, and drive-time matrices. Bring your own Maps key for cost passthrough or use ours. Cached aggressively so the same lane isn't re-queried on every reprice.
Weather-aware dispatch.
Current conditions and forecast along every plotted lane. Winter-storm and heat-advisory overlays feed into HOS risk scoring and appointment risk inside EusoTrip.
REST. tRPC. Webhooks. One spec.
Every integration on this page rides the same surface. REST for partners with HTTP clients in any language, tRPC for EusoTrip-native frontends and TypeScript partners, and signed webhooks for event subscribers. The whole thing is described by an OpenAPI document you can codegen against.
REST
Versioned, JSON-shaped HTTP. The default path for partners with off-the-shelf HTTP clients in any language.
tRPC
End-to-end typed RPC. Schema changes propagate as type errors before they ship — the path of choice for TypeScript integrations.
Webhooks
Signed event delivery for subscribers. Subscribe per event type per tenant; payloads are HMAC-SHA256 signed and replayable from the events endpoint.
OpenAPI
The whole REST surface is described by an OpenAPI document. Drop it into your codegen pipeline and you have a typed client in minutes.
OAuth 2.0
Authorization Code with PKCE for user-context flows, Client Credentials for server-to-server. Tokens are short-lived and scoped to tenant + role.
Sandbox
A non-production environment seeded with realistic loads, carriers, and lanes. Build the whole integration without touching live money.
SDKs
First-party TypeScript and Python SDKs generated directly from the OpenAPI spec. They stay in sync with every API release.
Status
Public uptime and incident history. Subscribe via webhook to be paged when EusoTrip is — your customers shouldn't find out from your support inbox.
One call. Every source.
A partner POSTs a lane to the rate-quote endpoint. EusoTrip composes the answer from every integration on this page — DAT, SONAR, HaulPay, macro indices, EIA fuel, FMCSA safety, VUCEM customs — and returns a single cited, replayable response.
// Request POST https://api.eusotrip.com/v1/rate-quote Authorization: Bearer <oauth_token> Idempotency-Key: "qt_partner_2026-04-14_4e7" { "lane": { "origin": "DAL", "destination": "MTY" }, "equipment": "DRY_VAN_53", "pickup": "2026-04-15T08:00:00Z" } // 200 OK — every source cited inline { "quote_id": "qt_01HZX...", "rate_per_mi": 2.414, "confidence": 0.91, "blend": [ { "src": "DAT Trendlines", "w": 0.50, "val": 2.42 }, { "src": "SONAR NTI", "w": 0.25, "val": 2.38 }, { "src": "HaulPay (partner)", "w": 0.15, "val": 2.45 }, { "src": "FRED + BTS + CASS", "w": 0.10, "val": 2.40 } ], "fuel": { "src": "EIA PADD 3", "per_gal": 3.71 }, "safety": { "src": "FMCSA SAFER", "rating": "Satisfactory" }, "customs": { "src": "VUCEM", "usmca": true }, "valid_until": "2026-04-15T20:00:00Z" }
Build with EusoTrip
Plug your system in.
Whether you're a data provider, a fleet-ops tool, a payment network, or an identity vendor — if it's cited, typed, and replayable, EusoTrip wants to integrate it. OpenAPI spec, sandbox keys, and a partner engineer are one email away.