MVMNT
MVMNT is a freight-brokerage transportation management system (TMS) for midmarket and small freight brokers and shippers. Its REST API (OpenAPI 3.1) and real-time webhooks let teams automate freight workflows end to end: managing customers, carriers, companies, loads, shipments, and quotes, and running accounts-receivable/accounts-payable finance (invoices, bills, payments, credit memos) so the MVMNT TMS stays in sync with internal systems. The API uses OAuth 2.0 client-credentials auth, cursor pagination, PATCH partial updates, soft deletes, and a webhook event catalog covering entity, shipment, and financial events.
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 MVMNT the way a machine reads it — 33 machine-readable artifacts across 27 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 — MVMNT scores 58.7/100 (developing), with a separate agent-readiness read of 57/100 (agent ready). 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 MVMNT
Each block below is one kind of artifact we hold for MVMNT. 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 27
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.
MVMNT Bill Payments API
AP bill payment management operations. Bill payments record payments made to carriers and vendors.
MVMNT Bills API
AP bill management operations. Bills represent carrier and vendor invoices to be paid.
MVMNT Carrier Contacts API
Carrier contact management operations
MVMNT Carrier Factors API
Carrier factor (factoring company) management operations
MVMNT Carrier Payment Methods API
Carrier payment method management operations
MVMNT Carriers API
Carrier management operations
MVMNT Companies API
Company management operations
MVMNT Credit Memos API
AR credit memo management operations. Credit memos represent customer credits that can be applied to invoices.
MVMNT Customer Contacts API
Customer contact management operations
MVMNT Customers API
Customer management operations
MVMNT Documents API
Document management operations. Documents are files (PDFs, images) that can be attached to orders, loads, or services.
MVMNT Invoices API
AR invoice management operations. Invoices represent customer billing for shipment services.
MVMNT Loads API
Load management operations. Loads represent carrier execution - which carrier is moving the freight.
MVMNT Location Contacts API
Location contact management operations
MVMNT Locations API
Location management operations
MVMNT Payment Terms API
Payment term management operations
MVMNT Payments API
AR payment management operations. Payments represent received customer payments applied to invoices.
MVMNT Quotes API
Quote management operations. Quotes are pricing requests/responses that can be converted to shipments.
MVMNT Saved Searches API
Saved search management operations
MVMNT Search API
Global search operations
MVMNT Services API
Service (vended service) management operations. Services represent non-carrier vendor work (drayage, customs, warehousing).
MVMNT Shipments API
Shipment tracking and management operations. Shipments contain orders, loads, and services.
MVMNT Teams API
Team management operations
MVMNT Users API
User management operations
MVMNT Vendor Contacts API
Vendor contact management operations
MVMNT Vendor Payment Methods API
Vendor payment method management operations
MVMNT Vendors API
Vendor management operations
Scroll within the panel for all 27 ·
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.
mvmnt-mcp.yml
MCP SERVEREvent Specifications 2
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
MVMNT Webhooks
AsyncAPI description of MVMNT's outbound webhook surface, generated by API Evangelist from the real webhook definition and event enum in the MVMNT OpenAPI 3.1 description. MVMNT...
ASYNCAPIMvmnt Webhooks
ASYNCAPISecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for MVMNT — 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 4
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
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/mvmnt · machine-readable index on apis.io