How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Nash website screenshot

Nash

Nash is an AI-powered last-mile delivery orchestration platform that lets retailers, restaurants, grocers, pharmacies, and logistics teams quote, dispatch, and track deliveries across a network of third-party couriers and their own internal fleets from a single API. The Nash Platform API covers orders, jobs (deliveries), quoting, dispatch strategies, route optimization, delivery windows, zones, store locations, shifts, store catalog, notifications, and signed webhooks, alongside a Fleet API for owned-fleet delivery reporting and a Nash Agent copilot exposed over a Model Context Protocol (MCP) server for agent-driven delivery operations. Backed by a16z.

agent native

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Nash the way a machine reads it — 70 machine-readable artifacts across 1 API, 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 — Nash scores 60.2/100 (strong), with a separate agent-readiness read of 39/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Composite quality — 60.2/100 · strong
Contract Quality 15.6 / 25
Access Clarity 12.1 / 20
Discoverability 7.6 / 10
Agent readiness — 39/100 · agent native
Agentic Access Contract derived 2.5 / 10
Documented Reversibility documented 2.4 / 6
MCP Server documented 4.8 / 12
Machine-Readable Auth bearer 3.5 / 10
Idempotency documented 4.5 / 9
Stable Error Semantics documented 4.0 / 8
Request/Response Examples partial 3.5 / 7
Rate-Limit Signaling documented 3.5 / 7
Agent Skills derived 1.3 / 5
Nash Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Nash's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/nash/"
   title="Nash on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/nash.svg"
       alt="Nash Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Nash

Each block below is one kind of artifact we hold for Nash. 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 30

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.

Nash AI Functions API

LLM-backed domain tools

Nash Contracts API

Provider contract pricing and version listings

Nash Delivery Windows API

Delivery Windows

Nash Dispatch Strategies API

Dispatch Strategies

Nash Fleet API

Inbound endpoints fleets call to update in-flight deliveries.

Nash Miscellaneous API

Miscellaneous

Nash Notifications API

Notifications

Nash Optimization Strategies API

Create, read, update, and delete route optimization strategies.

Nash Organizations API

Organizations

Nash Route Restrictions API

Org-scoped geographic areas the route optimizer must avoid traversing.

Nash Shipping API

Shipping operations

Nash Store Catalog API

Store Catalog

Nash Store Locations API

Store Locations

Nash Users API

User, role, and organization-membership management.

Nash Webhooks API

Webhook delivery inspection

Nash Workflow API

Workflow automation management

Nash Workflow Execution API

Workflow execution history and monitoring

Scroll within the panel for all 30 ·

Open Collections 31

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

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

Scroll within the panel for all 31 ·

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.

Nash MCP Server

MCP SERVER

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Nash Rate Limits

0 limits

RATE LIMITS

Event 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.

Nash Webhooks

Real-time delivery events Nash pushes to subscriber endpoints over HTTP, delivered and signed via Svix. Each message carries `type`, `event`, and `data`. Endpoints are registere...

ASYNCAPI

Nash Webhooks

ASYNCAPI

Security Posture 4

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.

Nash Authentication

http · 1 scheme

SECURITY

Nash Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Nash Vulnerability Disclosure

Hackerone · contact published

SECURITY

Nash Trust Center

SOC 2

SECURITY

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.

Nash Agentic Access

173 operations · 118 acting · 16 human-in-the-loop

173 operations · 118 acting

AGENTIC

Resources

Every other property we hold for Nash — 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.

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Commercial 3

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

← All providers · Data indexed from github.com/api-evangelist/nash · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Nash, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.