FRAYT

FRAYT (Frayt Technologies, Inc., Cincinnati, Ohio) operates an on-demand and scheduled middle-mile and last-mile delivery marketplace that connects shippers to a vetted nationwide network of owner-operator drivers running everything from cars and midsize vehicles to pickups, cargo vans and box trucks. The FRAYT Client API is a versioned REST API (v2.2) over JSON, secured with OAuth 2.0 client-credentials bearer tokens, that lets a TMS, ERP or storefront price a delivery as an "estimate", authorize it into a "match", track it through the driver lifecycle, tip a driver and cancel it — with webhook callbacks defined in the OpenAPI itself for real-time match and driver-location updates. A full sandbox environment mirrors production.

FRAYT publishes 3 API contracts indexed on the APIs.io network: match estimates API, Matches API, and OAUTH API. Tagged areas include Company, Last Mile Delivery, Logistics, Couriers, and On-Demand Delivery.

The FRAYT catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

FRAYT’s developer surface includes documentation, engineering blog, support, signup flow, and 26 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

49.5/100 developing ▬ flat Agent 36/100 agent ready Front door AI 1/6 silent Heartbeat 24/100 slowing saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

4 published contracts 3 Agent Skills

Company Last Mile Delivery Logistics Couriers On-Demand Delivery Shipping Freight Supply Chain Transportation Third Party Logistics Delivery Tracking Webhook

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Supply Chain Management

BC-520

Matches

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 49.5/100 · developing

Contract Quality 13.4 / 19

Developer Ergonomics 11.0 / 15

Access Clarity 3.2 / 15

Operational Transparency 1.0 / 10

Contract Governance 2.0 / 9

Discoverability 6.0 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 36/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/frayt/"><img src="https://apis.io/badge/frayt/card.svg" alt="FRAYT on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Protected Resource Metadata +5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified)

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Operational Transparency scores 10.5 — up to +11.6 composite points
Contract Governance scores 22.0 — up to +9.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/frayt/apis.yml: open an issue on github.com/api-evangelist/frayt to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

FRAYT match estimates API

The match estimates API from FRAYT — 2 operation(s) for match estimates.

FRAYT Matches API

The matches API from FRAYT — 3 operation(s) for matches.

FRAYT OAUTH API

The oauth API from FRAYT — 1 operation(s) for oauth.

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

frayt-amend-or-cancel-delivery

AGENT SKILL

frayt-quote-and-book-delivery

AGENT SKILL

frayt-track-delivery-lifecycle

AGENT SKILL

FRAYT API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Frayt Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Frayt Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Frayt Finops

FINOPS

Event Specifications 1

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

Frayt Match Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Frayt Context

33 classes · 144 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

FRAYT API Rules

14 rules · 12 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Frayt Matches Overlay

6 actions · servers · frayt-matches-openapi.yml

DERIVED

JSON Schema 9

Standalone JSON Schema definitions for this provider's data models.

CancelMatchRequest

1 properties

JSON SCHEMA

MatchRequest

26 properties

JSON SCHEMA

MatchResponse

1 properties

JSON SCHEMA

MatchStopResponse

37 properties

JSON SCHEMA

Oauth Request

3 properties

JSON SCHEMA

Oauth Response

1 properties

JSON SCHEMA

RestrictedUpdateMatchRequest

22 properties

JSON SCHEMA

UpdateDriverTip

1 properties

JSON SCHEMA

UpdateEstimateRequest

26 properties

JSON SCHEMA

Scroll for all 9

Security Posture 2

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

Frayt Authentication

http · 1 scheme

SECURITY

Frayt Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Agentic Access 1

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

Frayt Agentic Access

8 operations · 7 acting · 7 human-in-the-loop

8 operations · 7 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

AgenticAccess

LLMsTxt

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Lifecycle

Conformance

Build 4

SDKs, sample code, and the tooling you integrate with

IntegrationEdges

IntegrationEdges

SDKs

SDKs

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 3

The organization behind the API

Newsroom

Newsroom

Website

Website

Blog

Blog

Other 5

Properties that don't map to a standard resource type

CapabilityMap

Hosts

Vendors

Leadership

Overlay

Source (apis.yml)

aid: frayt
name: FRAYT
description: FRAYT (Frayt Technologies, Inc., Cincinnati, Ohio) operates an on-demand and scheduled middle-mile and last-mile
  delivery marketplace that connects shippers to a vetted nationwide network of owner-operator drivers running everything
  from cars and midsize vehicles to pickups, cargo vans and box trucks. The FRAYT Client API is a versioned REST API (v2.2)
  over JSON, secured with OAuth 2.0 client-credentials bearer tokens, that lets a TMS, ERP or storefront price a delivery
  as an "estimate", authorize it into a "match", track it through the driver lifecycle, tip a driver and cancel it — with
  webhook callbacks defined in the OpenAPI itself for real-time match and driver-location updates. A full sandbox environment
  mirrors production.
url: https://raw.githubusercontent.com/api-evangelist/frayt/refs/heads/main/apis.yml
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
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-productions2.s3.amazonaws.com/apis-json/apis-json-logo.jpg
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-16'
modified: '2026-08-16'
tags:
- Company
- Last Mile Delivery
- Logistics
- Couriers
- On-Demand Delivery
- Shipping
- Freight
- Supply Chain
- Transportation
- Third Party Logistics
- Delivery Tracking
- Webhook
tags_raw:
- Company
- Last Mile Delivery
- Logistics
- Courier
- On Demand Delivery
- Shipping
- Freight
- Supply Chain
- Transportation
- Third Party Logistics
- Delivery Tracking
- Webhooks
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/frayt-capability-edges.yml
  name: FRAYT Business Capability Map
- type: Documentation
  url: https://dev.frayt.com/
- type: Spectral
  url: rules/frayt-rules.yml
- type: JSONLD
  url: json-ld/frayt-context.jsonld
- type: Vocabulary
  url: vocabulary/frayt-vocabulary.yml
- type: WellKnown
  url: well-known/frayt-well-known.yml
- type: Hosts
  url: hosts/frayt-hosts.yml
- type: IntegrationEdges
  url: integrations/frayt-integration-edges.yml
- type: Vendors
  url: vendors/frayt-vendors.yml
- type: SDKs
  url: packages/frayt-packages.yml
- type: Newsroom
  url: https://www.frayt.com/resources/news
- type: Leadership
  url: https://www.frayt.com/leadership
- type: DeveloperPortal
  url: https://dev.frayt.com
- type: Overlay
  url: overlays/frayt-matches-overlay.yaml
- type: AgenticAccess
  url: agentic-access/frayt-agentic-access.yml
- type: DomainSecurity
  url: security/frayt-domain-security.yml
- type: Website
  url: https://www.frayt.com/
- type: Blog
  url: https://www.frayt.com/resources/blog
- type: Support
  url: https://www.frayt.com/contact
- type: HelpCenter
  url: https://www.frayt.com/platform/faqs
- type: GitHubOrganization
  url: https://github.com/Frayt-Technologies
- type: TermsOfService
  url: https://www.frayt.com/eula
- type: PrivacyPolicy
  url: https://www.frayt.com/privacy-policy
- type: SignUp
  url: https://www.frayt.app/
- type: LLMsTxt
  url: llms/frayt-llms.txt
- type: Packages
  url: packages/frayt-packages.yml
- type: Lifecycle
  url: lifecycle/frayt-lifecycle.yml
- type: Conformance
  url: conformance/frayt-conformance.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Plans
  url: plans/frayt-plans-pricing.yml
apis:
- aid: frayt:frayt-match-estimates-api
  name: FRAYT match estimates API
  description: The match estimates API from FRAYT — 2 operation(s) for match estimates.
  humanURL: https://www.frayt.com/frayt-api
  baseURL: https://api.frayt.com/api/v2.2/
  tags:
  - match estimates
  properties:
  - type: OpenAPI
    url: openapi/frayt-match-estimates-api-openapi.yml
  - type: Documentation
    url: https://api.frayt.com/docs/api/v2.2
  - type: APIReference
    url: https://api.frayt.com/docs/api/v2.2
  - type: GettingStarted
    url: https://www.frayt.com/frayt-api
  - type: DeveloperPortal
    url: https://www.frayt.com/3pl/api
  - type: Authentication
    url: authentication/frayt-authentication.yml
  - type: Conventions
    url: conventions/frayt-conventions.yml
  - type: ErrorCatalog
    url: errors/frayt-problem-types.yml
  - type: DataModel
    url: data-model/frayt-data-model.yml
  - type: Webhooks
    url: asyncapi/frayt-match-webhooks.yml
  - type: Sandbox
    url: sandbox/frayt-sandbox.yml
  - type: JSONSchema
    url: json-schema/frayt-match-request-schema.json
  - type: JSONSchema
    url: json-schema/frayt-update-estimate-request-schema.json
  - type: JSONSchema
    url: json-schema/frayt-match-response-schema.json
- aid: frayt:frayt-matches-api
  name: FRAYT Matches API
  description: The matches API from FRAYT — 3 operation(s) for matches.
  humanURL: https://www.frayt.com/frayt-api
  baseURL: https://api.frayt.com/api/v2.2/
  tags:
  - Matches
  tags_raw:
  - matches
  properties:
  - type: OpenAPI
    url: openapi/frayt-matches-api-openapi.yml
  - type: Documentation
    url: https://api.frayt.com/docs/api/v2.2
  - type: APIReference
    url: https://api.frayt.com/docs/api/v2.2
  - type: GettingStarted
    url: https://www.frayt.com/frayt-api
  - type: DeveloperPortal
    url: https://www.frayt.com/3pl/api
  - type: Authentication
    url: authentication/frayt-authentication.yml
  - type: Conventions
    url: conventions/frayt-conventions.yml
  - type: ErrorCatalog
    url: errors/frayt-problem-types.yml
  - type: DataModel
    url: data-model/frayt-data-model.yml
  - type: Webhooks
    url: asyncapi/frayt-match-webhooks.yml
  - type: Sandbox
    url: sandbox/frayt-sandbox.yml
  - type: JSONSchema
    url: json-schema/frayt-match-stop-response-schema.json
  - type: JSONSchema
    url: json-schema/frayt-match-request-schema.json
  - type: JSONSchema
    url: json-schema/frayt-match-response-schema.json
  - type: JSONSchema
    url: json-schema/frayt-restricted-update-match-request-schema.json
  - type: JSONSchema
    url: json-schema/frayt-update-driver-tip-schema.json
  - type: JSONSchema
    url: json-schema/frayt-cancel-match-request-schema.json
- aid: frayt:frayt-oauth-api
  name: FRAYT OAUTH API
  description: The oauth API from FRAYT — 1 operation(s) for oauth.
  humanURL: https://www.frayt.com/frayt-api
  baseURL: https://api.frayt.com/api/v2.2/
  tags:
  - OAuth
  - Authentication
  tags_raw:
  - oauth
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/frayt-oauth-api-openapi.yml
  - type: Documentation
    url: https://api.frayt.com/docs/api/v2.2
  - type: APIReference
    url: https://api.frayt.com/docs/api/v2.2
  - type: GettingStarted
    url: https://www.frayt.com/frayt-api
  - type: DeveloperPortal
    url: https://www.frayt.com/3pl/api
  - type: Authentication
    url: authentication/frayt-authentication.yml
  - type: Conventions
    url: conventions/frayt-conventions.yml
  - type: ErrorCatalog
    url: errors/frayt-problem-types.yml
  - type: DataModel
    url: data-model/frayt-data-model.yml
  - type: Webhooks
    url: asyncapi/frayt-match-webhooks.yml
  - type: Sandbox
    url: sandbox/frayt-sandbox.yml
  - type: JSONSchema
    url: json-schema/frayt-oauth-request-schema.json
  - type: JSONSchema
    url: json-schema/frayt-oauth-response-schema.json
x-enrichment:
  date: '2026-10-20'
  status: enriched
  artifacts_added: 0
  pass: local-v5

FRAYT API — frequently asked questions

Does FRAYT have an API?

Yes. APIs.io lists 3 APIs from FRAYT, including FRAYT match estimates API, FRAYT Matches API and FRAYT OAUTH API.

Is there an OpenAPI specification for the FRAYT API?

Yes. APIs.io indexes 3 OpenAPI specifications for FRAYT, each linked for download from this page.

How do I authenticate with the FRAYT API?

FRAYT uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Frayt Authentication.

Is the FRAYT API ready for AI agents?

FRAYT has a Kin Score of 49.5 out of 100 (developing) and an Agent Readiness score of 36.4 (agent-ready), scored by API Evangelist on 2026-11-06.

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/frayt"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/frayt/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/frayt/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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