Loop website screenshot

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.

Loop publishes 14 APIs on the APIs.io network, including artifacts API, artifacts-schema-validated API, business-exceptions API, and 11 more. Tagged areas include Company, Logistics, Supply Chain, Freight, and Freight Audit.

The Loop catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Loop’s developer surface includes authentication, documentation, API reference, getting-started guide, engineering blog, signup flow, and 21 more developer resources.

47.7/100 developing ▬ flat Agent 33/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
2 APIs
CompanyLogisticsSupply ChainFreightFreight AuditPaymentsTransportationArtificial IntelligenceData Platform

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/loop: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 14

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 for all 14

Open Collections 14

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Scroll for all 14

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Loop Webhooks

ASYNCAPI

Security Posture 2

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

Loop Authentication

http · 1 scheme

SECURITY

Loop Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

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

Loop Agentic Access

41 operations · 15 acting

41 operations · 15 acting

AGENTIC

Resources

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 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 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: loop
name: Loop
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/loop/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 8vc
- fifth-wall
- index-ventures
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
image: https://cdn.prod.website-files.com/668bb14a7a97da320e5022ed/66c70f294893e981b7a38704_OG%20Image.webp
tags:
- Company
- Logistics
- Supply Chain
- Freight
- Freight Audit
- Payments
- Transportation
- Artificial Intelligence
- Data Platform
apis:
- aid: loop:loop-artifacts-api
  name: Loop artifacts API
  description: The artifacts API from Loop — 6 operation(s) for artifacts.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - Artifacts
  tags_raw:
  - artifacts
  properties:
  - type: OpenAPI
    url: openapi/loop-artifacts-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-artifacts-schema-validated-api
  name: Loop artifacts-schema-validated API
  description: The artifacts-schema-validated API from Loop — 6 operation(s) for artifacts-schema-validated.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - artifacts-schema-validated
  properties:
  - type: OpenAPI
    url: openapi/loop-artifacts-schema-validated-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-business-exceptions-api
  name: Loop business-exceptions API
  description: The business-exceptions API from Loop — 3 operation(s) for business-exceptions.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - business-exceptions
  properties:
  - type: OpenAPI
    url: openapi/loop-business-exceptions-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-factoring-relationships-api
  name: Loop factoring-relationships API
  description: The factoring-relationships API from Loop — 2 operation(s) for factoring-relationships.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - factoring-relationships
  properties:
  - type: OpenAPI
    url: openapi/loop-factoring-relationships-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-invoicing-relationships-api
  name: Loop invoicing-relationships API
  description: The invoicing-relationships API from Loop — 2 operation(s) for invoicing-relationships.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - invoicing-relationships
  properties:
  - type: OpenAPI
    url: openapi/loop-invoicing-relationships-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-onboarding-api-loop-com-api
  name: Loop onboarding.api.loop.com API
  description: The onboarding.api.loop.com API from Loop — 1 operation(s) for onboarding.api.loop.com.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - onboarding.api.loop.com
  properties:
  - type: OpenAPI
    url: openapi/loop-onboarding-api-loop-com-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-organizations-api
  name: Loop organizations API
  description: The organizations API from Loop — 3 operation(s) for organizations.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - Organization
  tags_raw:
  - organizations
  properties:
  - type: OpenAPI
    url: openapi/loop-organizations-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-payable-allocations-api
  name: Loop payable-allocations API
  description: The payable-allocations API from Loop — 2 operation(s) for payable-allocations.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - payable-allocations
  properties:
  - type: OpenAPI
    url: openapi/loop-payable-allocations-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-payable-invoice-reviews-api
  name: Loop payable-invoice-reviews API
  description: The payable-invoice-reviews API from Loop — 2 operation(s) for payable-invoice-reviews.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - payable-invoice-reviews
  properties:
  - type: OpenAPI
    url: openapi/loop-payable-invoice-reviews-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-payable-invoices-api
  name: Loop payable-invoices API
  description: The payable-invoices API from Loop — 2 operation(s) for payable-invoices.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - payable-invoices
  properties:
  - type: OpenAPI
    url: openapi/loop-payable-invoices-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-payments-api
  name: Loop payments API
  description: The payments API from Loop — 2 operation(s) for payments.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - Payments
  tags_raw:
  - payments
  properties:
  - type: OpenAPI
    url: openapi/loop-payments-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-ping-api
  name: Loop ping API
  description: The ping API from Loop — 1 operation(s) for ping.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - Ping
  tags_raw:
  - ping
  properties:
  - type: OpenAPI
    url: openapi/loop-ping-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-receivable-invoices-api
  name: Loop receivable-invoices API
  description: The receivable-invoices API from Loop — 3 operation(s) for receivable-invoices.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - receivable-invoices
  properties:
  - type: OpenAPI
    url: openapi/loop-receivable-invoices-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
- aid: loop:loop-shipment-jobs-api
  name: Loop shipment-jobs API
  description: The shipment-jobs API from Loop — 2 operation(s) for shipment-jobs.
  humanURL: https://docs.loop.com/developers/
  baseURL: https://api.loop.com
  tags:
  - shipment-jobs
  properties:
  - type: OpenAPI
    url: openapi/loop-shipment-jobs-api-openapi.yml
  - type: APIReference
    url: https://docs.loop.com/developers/api-reference
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/loop-capability-edges.yml
  name: Loop Business Capability Map
- type: DomainSecurity
  url: security/loop-domain-security.yml
- type: AgenticAccess
  url: agentic-access/loop-agentic-access.yml
- type: Authentication
  url: authentication/loop-authentication.yml
- type: Website
  url: https://loop.com
- type: DeveloperPortal
  url: https://docs.loop.com
- type: Documentation
  url: https://docs.loop.com
- type: APIReference
  url: https://docs.loop.com/developers/api-reference
- type: GettingStarted
  url: https://docs.loop.com/integration/
- type: Blog
  url: https://loop.com/engineering-blog
- type: SignUp
  url: https://app.loop.com
- type: Login
  url: https://app.loop.com
- type: StatusPage
  url: https://status.loop.com
- type: TermsOfService
  url: https://loop.com/legal/terms-and-conditions
- type: PrivacyPolicy
  url: https://loop.com/legal/privacy-policy
- type: TrustCenter
  url: https://trust.loop.com
- type: X-MCPServerCandidate
  url: mcp/loop-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/loop-llms.txt
- type: Overlay
  url: overlays/loop-openapi-overlay.yaml
- type: Conformance
  url: conformance/loop-conformance.yml
- type: ErrorCatalog
  url: errors/loop-problem-types.yml
- type: Lifecycle
  url: lifecycle/loop-lifecycle.yml
- type: Conventions
  url: conventions/loop-conventions.yml
- type: Idempotency
  url: conventions/loop-conventions.yml
- type: DataModel
  url: data-model/loop-data-model.yml
- type: Webhooks
  url: asyncapi/loop-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 20
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/loop"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/loop/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/loop/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.