Loop
Loop is a full-stack, AI-powered logistics data platform that unifies the fragmented operational and financial data of the physical economy. Founded by former Uber Freight leaders Matt McKinney and Shaosu Liu, Loop began in freight audit and payment and has expanded into an intelligence layer spanning freight audit, parcel and carrier-invoice auditing, real-time shipment visibility, parcel contract optimization, carrier payments, and autonomous exception management (DUX and the Exception Agent). The Loop developer platform exposes a REST API (api.loop.com/v1) for ingesting artifacts (invoices, shipment records, purchase orders), resolving business exceptions, managing organizations and factoring/invoicing relationships, and reading payable/receivable invoices and payments, plus a separate Onboarding API and Svix-based webhooks. Loop has raised $210M total, including a $95M Series C, from Valor Equity Partners, 8VC, Founders Fund, Index Ventures, J.P. Morgan Growth Equity, and others.
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 Loop the way a machine reads it — 19 machine-readable artifacts across 14 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 — Loop scores 52.6/100 (developing), with a separate agent-readiness read of 80/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 Loop
Each block below is one kind of artifact we hold for Loop. 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 14
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.
Loop artifacts API
The artifacts API from Loop — 6 operation(s) for artifacts.
Loop artifacts-schema-validated API
The artifacts-schema-validated API from Loop — 6 operation(s) for artifacts-schema-validated.
Loop business-exceptions API
The business-exceptions API from Loop — 3 operation(s) for business-exceptions.
Loop factoring-relationships API
The factoring-relationships API from Loop — 2 operation(s) for factoring-relationships.
Loop invoicing-relationships API
The invoicing-relationships API from Loop — 2 operation(s) for invoicing-relationships.
Loop onboarding.api.loop.com API
The onboarding.api.loop.com API from Loop — 1 operation(s) for onboarding.api.loop.com.
Loop organizations API
The organizations API from Loop — 3 operation(s) for organizations.
Loop payable-allocations API
The payable-allocations API from Loop — 2 operation(s) for payable-allocations.
Loop payable-invoice-reviews API
The payable-invoice-reviews API from Loop — 2 operation(s) for payable-invoice-reviews.
Loop payable-invoices API
The payable-invoices API from Loop — 2 operation(s) for payable-invoices.
Loop payments API
The payments API from Loop — 2 operation(s) for payments.
Loop ping API
The ping API from Loop — 1 operation(s) for ping.
Loop receivable-invoices API
The receivable-invoices API from Loop — 3 operation(s) for receivable-invoices.
Loop shipment-jobs API
The shipment-jobs API from Loop — 2 operation(s) for shipment-jobs.
Scroll within the panel for all 14 ·
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.
loop-mcp.yml
MCP SERVEREvent Specifications 1
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.
Loop 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.
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 Loop — 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 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 1
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/loop · machine-readable index on apis.io