Roadsync
RoadSync is a digital payments and expense-management platform for the logistics and trucking industry, enabling warehouses, repair and tow shops, brokers, and carriers to accept and disburse payments faster. RoadSync publishes a REST API surface across six services: the RoadSyncPay Public API (payees, funding sources, payables, transactions, brokers, loads for ACH/paper-check/RTP carrier disbursements), the Invoice API (create, send, void, clone, refund, and embed invoices), the Company API (locations and product catalog), the WorkOrders API (create, send, approve work orders), a Payment API for taking payments, and a legacy Client API. All APIs are HTTPS REST, authenticated with an x-api-key header, versioned in the URI path, and split into test and production hosts.
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.
API Evangelist profiles Roadsync the way a machine reads it — 22 machine-readable artifacts across 18 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 — Roadsync scores 45.7/100 (developing), with a separate agent-readiness read of 74/100 (agent native). 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Roadsync
Each block below is one kind of artifact we hold for Roadsync. 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 18
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.
Roadsync authenticated API
Authenticated operations not otherwise functionally categorized
Roadsync brokers API
The brokers API from Roadsync — 2 operation(s) for brokers.
Roadsync department API
Department operations
Roadsync directory API
The directory API from Roadsync — 1 operation(s) for directory.
Roadsync eta API
ETA (Estimated Time of Arrival) endpoints
Roadsync funding sources API
The funding sources API from Roadsync — 2 operation(s) for funding sources.
Roadsync invoice API
Invoice operations
Roadsync loads API
The loads API from Roadsync — 2 operation(s) for loads.
Roadsync location API
Company location operations
Roadsync payables API
The payables API from Roadsync — 2 operation(s) for payables.
Roadsync payees API
The payees end point
Roadsync payment API
Payment API Operations
Roadsync ping API
The ping API from Roadsync — 1 operation(s) for ping.
Roadsync product API
Product operations (company)
Roadsync shift API
Shift operations (company/ location)
Roadsync transactions API
The transactions API from Roadsync — 2 operation(s) for transactions.
Roadsync unauthenticated API
Unauthenticated operations not otherwise functionally categorized
Roadsync workorders API
The Workorders API
Scroll within the panel for all 18 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
roadsync-mcp.yml
MCP SERVERSecurity Posture 2
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.
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.
Resources
Every other property we hold for Roadsync — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/roadsync · machine-readable index on apis.io