ShipMonk

ShipMonk is a Florida-headquartered third-party logistics (3PL) and ecommerce fulfillment provider operating a network of fulfillment centres across the United States, Canada, Mexico, the United Kingdom and Czechia. It runs an order management system for direct-to-consumer, retail/B2B and marketplace brands covering inbound receiving, inventory and lot control, pick-and-pack fulfillment, multi-carrier shipping and returns. Its public API is a single REST surface at api.shipmonk.com, described by a self-published OpenAPI 3.1 document covering orders, products and inventory, receivings, returns and warehouses, with four HTTP webhook events for shipment, order, return and receiving status changes and a contract-only sandbox environment with warehouse simulation endpoints.

ShipMonk publishes 8 API contracts indexed on the APIs.io network, including Webhooks, Orders API, Products API, and 5 more. Tagged areas include Logistics, Fulfillment, 3PL, E-Commerce, and Warehousing.

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

ShipMonk’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 38 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

54.4/100 strong ▬ flat Agent 36/100 agent ready Front door AI 2/6 trace saas Full breakdown ↓
scored 2026-10-23 · rubric v0.25.0 · Show this score on your site →

6 published contracts 1 MCP Servers

Logistics Fulfillment 3PL E-Commerce Warehousing Inventory Shipping Returns Supply Chain Direct to Consumer Order Management

What this lets a business do 1

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

Warehousing Operations Management

BC-2460

OrdersReceivingsReturns

POST /v1/integrations/receiving POST /v1/integrations/returns POST /v1/integrations/submit-order

Kin Score

Kin Score How this is scored →
scored 2026-10-23 · rubric v0.25.0

Composite quality — 54.4/100 · strong

Contract Quality 10.5 / 19

Developer Ergonomics 6.2 / 15

Access Clarity 9.1 / 15

Operational Transparency 5.5 / 10

Contract Governance 0.4 / 9

Discoverability 5.8 / 8

Regulatory Posture 5.3 / 15

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 36/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 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

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/shipmonk/"><img src="https://apis.io/badge/shipmonk/card.svg" alt="ShipMonk on APIs.io — Kin Score by API Evangelist"></a>

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

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/shipmonk: 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Amazon Seller Ecosystem (Selling Partner Appstore, Amazon Ads partners)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 8

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

ShipMonk Webhooks

The ShipMonk event surface: four HTTP callback events (order shipment notification, order status change, return status change, receiving status change) declared in the OpenAPI 3...

ShipMonk MCP Server

A live Model Context Protocol endpoint served from ShipMonk's own developer-docs host. tools/list responds anonymously with five spec-driven tools: four OpenAPI introspection to...

ShipMonk Orders API

The Orders API from ShipMonk — 5 operation(s) for orders.

ShipMonk Products API

The Products API from ShipMonk — 4 operation(s) for products.

ShipMonk Receivings API

The Receivings API from ShipMonk — 4 operation(s) for receivings.

ShipMonk Returns API

The Returns API from ShipMonk — 3 operation(s) for returns.

ShipMonk Warehouses API

The Warehouses API from ShipMonk — 1 operation(s) for warehouses.

ShipMonk Webhooks API

ShipMonk supports webhooks to help you stay updated in real time as key events happen in our system. Currently, we provide webhooks for the following areas: - Orders - Returns -...

Scroll for all 8

Open Collections 5

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

ShipMonk Orders API

OPEN COLLECTION

ShipMonk Products API

OPEN COLLECTION

ShipMonk Receivings API

OPEN COLLECTION

ShipMonk Returns API

OPEN COLLECTION

ShipMonk Warehouses API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

ShipMonk MCP Server

ShipMonk serves a live MCP endpoint from its own developer-docs host. tools/list responds anonymously over streamable HTTP (SSE) with five spec-driven tools. These are ReadMe's ...

MCP SERVER

Rate Limits 1

Documented rate limits and quota policies.

Shipmonk Rate Limits

2 limits

RATE LIMITS

Event Specifications 1

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

ShipMonk Webhooks

AsyncAPI 3.0 model of the ShipMonk webhook event surface, derived from the `webhooks` block of ShipMonk's own OpenAPI 3.1 document (https://apidocs.shipmonk.com/openapi/public_a...

ASYNCAPI

OpenAPI Overlays 5

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.

Shipmonk Orders Overlay

8 actions · documentation · shipmonk-orders-openapi.yml

DERIVED

Shipmonk Products Overlay

7 actions · documentation · shipmonk-products-openapi.yml

DERIVED

Shipmonk Receivings Overlay

8 actions · documentation · shipmonk-receivings-openapi.yml

DERIVED

Shipmonk Returns Overlay

7 actions · documentation · shipmonk-returns-openapi.yml

DERIVED

Shipmonk Warehouses Overlay

4 actions · documentation · shipmonk-warehouses-openapi.yml

DERIVED

Security Posture 4

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

Shipmonk Authentication

apiKey · 1 scheme

SECURITY

Shipmonk Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Shipmonk Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Shipmonk Trust Center

SOC 2 Type II

SECURITY

Agentic Access 1

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

Shipmonk Agentic Access

19 operations · 9 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 4

Reference material describing how the API behaves

Documentation

APIReference

OpenAPI

AsyncAPI

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

AgentSkill

AgenticAccess

LLMsTxt

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

Conformance

DataModel

Webhooks

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

ToolCrosswalk

ToolCrosswalk

Access & Security 7

Authentication, authorization, and security posture

Compliance

Compliance

TrustCenter

TrustCenter

Security

Security

VulnerabilityDisclosure

VulnerabilityDisclosure

SecurityTxt

SecurityTxt

DomainSecurity

DomainSecurity

Authentication

Authentication

Scroll for all 7

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

ChangeLog

ChangeLog

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

Pricing

Pricing

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

BlogRSS

BlogRSS

Website

Website

Blog

Blog

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

APICatalog

APICatalog

Source (apis.yml)

aid: shipmonk
name: ShipMonk
url: https://raw.githubusercontent.com/api-evangelist/shipmonk/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-secondary-market-listing: https://forgeglobal.com/shipmonk_stock/
description: ShipMonk is a Florida-headquartered third-party logistics (3PL) and ecommerce fulfillment provider operating
  a network of fulfillment centres across the United States, Canada, Mexico, the United Kingdom and Czechia. It runs an order
  management system for direct-to-consumer, retail/B2B and marketplace brands covering inbound receiving, inventory and lot
  control, pick-and-pack fulfillment, multi-carrier shipping and returns. Its public API is a single REST surface at api.shipmonk.com,
  described by a self-published OpenAPI 3.1 document covering orders, products and inventory, receivings, returns and warehouses,
  with four HTTP webhook events for shipment, order, return and receiving status changes and a contract-only sandbox environment
  with warehouse simulation endpoints.
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
  - rate-limits
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://files.readme.io/742121760e9d1bfa2dd7dd9dc8fb20dba2f79207e8c192facb4681cdb2bb5c23-logo.svg
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Logistics
- Fulfillment
- 3PL
- E-Commerce
- Warehousing
- Inventory
- Shipping
- Returns
- Supply Chain
- Direct to Consumer
- Order Management
tags_raw:
- Logistics
- Fulfillment
- 3PL
- Ecommerce
- Warehousing
- Inventory
- Shipping
- Returns
- Supply Chain
- Direct-to-Consumer
- Order Management
created: '2026-08-02'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: shipmonk:shipmonk-webhooks
  name: ShipMonk Webhooks
  description: 'The ShipMonk event surface: four HTTP callback events (order shipment notification, order status change, return
    status change, receiving status change) declared in the OpenAPI 3.1 webhooks block. Deliveries authenticate with HTTP
    Basic and carry an X-Sm-Signature HMAC-SHA512 integrity header, with exponential-backoff retries.'
  humanURL: https://apidocs.shipmonk.com/reference/webhooks
  baseURL: https://api.shipmonk.com
  tags:
  - Logistics
  - Fulfillment
  - Webhook
  - Event
  tags_raw:
  - Logistics
  - Fulfillment
  - Webhooks
  - Events
  properties:
  - type: AsyncAPI
    url: asyncapi/shipmonk-webhooks-asyncapi.yml
  - type: Webhooks
    url: https://apidocs.shipmonk.com/reference/webhooks
  - type: Documentation
    url: https://apidocs.shipmonk.com/reference/webhooks
- aid: shipmonk:shipmonk-mcp
  name: ShipMonk MCP Server
  description: 'A live Model Context Protocol endpoint served from ShipMonk''s own developer-docs host. tools/list responds
    anonymously with five spec-driven tools: four OpenAPI introspection tools plus execute-request, a HAR-shaped proxy that
    can invoke any of the 19 ShipMonk REST operations.'
  humanURL: https://apidocs.shipmonk.com/
  baseURL: https://apidocs.shipmonk.com/mcp
  tags:
  - MCP
  - Agents
  - Logistics
  - Fulfillment
  properties:
  - type: MCPServer
    url: mcp/shipmonk-mcp.yml
  - type: ToolCrosswalk
    url: mcp/shipmonk-tool-crosswalk.yml
- aid: shipmonk:shipmonk-orders-api
  name: ShipMonk Orders API
  description: The Orders API from ShipMonk — 5 operation(s) for orders.
  humanURL: https://apidocs.shipmonk.com/reference
  baseURL: https://api.shipmonk.com
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/shipmonk-orders-api-openapi.yml
  - type: Documentation
    url: https://apidocs.shipmonk.com/docs/intro
  - type: APIReference
    url: https://apidocs.shipmonk.com/reference
  - type: Authentication
    url: https://apidocs.shipmonk.com/docs/api-key
  - type: RateLimits
    url: rate-limits/shipmonk-rate-limits.yml
  - type: Sandbox
    url: sandbox/shipmonk-sandbox.yml
- aid: shipmonk:shipmonk-products-api
  name: ShipMonk Products API
  description: The Products API from ShipMonk — 4 operation(s) for products.
  humanURL: https://apidocs.shipmonk.com/reference
  baseURL: https://api.shipmonk.com
  tags:
  - Product
  tags_raw:
  - Products
  properties:
  - type: OpenAPI
    url: openapi/shipmonk-products-api-openapi.yml
  - type: Documentation
    url: https://apidocs.shipmonk.com/docs/intro
  - type: APIReference
    url: https://apidocs.shipmonk.com/reference
  - type: Authentication
    url: https://apidocs.shipmonk.com/docs/api-key
  - type: RateLimits
    url: rate-limits/shipmonk-rate-limits.yml
  - type: Sandbox
    url: sandbox/shipmonk-sandbox.yml
- aid: shipmonk:shipmonk-receivings-api
  name: ShipMonk Receivings API
  description: The Receivings API from ShipMonk — 4 operation(s) for receivings.
  humanURL: https://apidocs.shipmonk.com/reference
  baseURL: https://api.shipmonk.com
  tags:
  - Receivings
  properties:
  - type: OpenAPI
    url: openapi/shipmonk-receivings-api-openapi.yml
  - type: Documentation
    url: https://apidocs.shipmonk.com/docs/intro
  - type: APIReference
    url: https://apidocs.shipmonk.com/reference
  - type: Authentication
    url: https://apidocs.shipmonk.com/docs/api-key
  - type: RateLimits
    url: rate-limits/shipmonk-rate-limits.yml
  - type: Sandbox
    url: sandbox/shipmonk-sandbox.yml
- aid: shipmonk:shipmonk-returns-api
  name: ShipMonk Returns API
  description: The Returns API from ShipMonk — 3 operation(s) for returns.
  humanURL: https://apidocs.shipmonk.com/reference
  baseURL: https://api.shipmonk.com
  tags:
  - Returns
  properties:
  - type: OpenAPI
    url: openapi/shipmonk-returns-api-openapi.yml
  - type: Documentation
    url: https://apidocs.shipmonk.com/docs/intro
  - type: APIReference
    url: https://apidocs.shipmonk.com/reference
  - type: Authentication
    url: https://apidocs.shipmonk.com/docs/api-key
  - type: RateLimits
    url: rate-limits/shipmonk-rate-limits.yml
  - type: Sandbox
    url: sandbox/shipmonk-sandbox.yml
- aid: shipmonk:shipmonk-warehouses-api
  name: ShipMonk Warehouses API
  description: The Warehouses API from ShipMonk — 1 operation(s) for warehouses.
  humanURL: https://apidocs.shipmonk.com/reference
  baseURL: https://api.shipmonk.com
  tags:
  - Warehouse
  tags_raw:
  - Warehouses
  properties:
  - type: OpenAPI
    url: openapi/shipmonk-warehouses-api-openapi.yml
  - type: Documentation
    url: https://apidocs.shipmonk.com/docs/intro
  - type: APIReference
    url: https://apidocs.shipmonk.com/reference
  - type: Authentication
    url: https://apidocs.shipmonk.com/docs/api-key
  - type: RateLimits
    url: rate-limits/shipmonk-rate-limits.yml
  - type: Sandbox
    url: sandbox/shipmonk-sandbox.yml
- aid: shipmonk:shipmonk-webhooks-api
  name: ShipMonk Webhooks API
  description: 'ShipMonk supports webhooks to help you stay updated in real time as key events happen in our system. Currently,
    we provide webhooks for the following areas:

    - Orders

    - Returns

    - Receivings


    ## Webhooks Setup

    You have full flexibility in configuring which webhooks to subscribe to. You can:

    - Use a single URL to receive all events, or

    - Define separate endpoints for individual webhook types.


    Webhook setup can be done by your ShipMonk support team.


    ## Store filter

    By default, a webhook subscription delivers events for all stores in your account. If you operate multiple stores, a subscription
    can be restricted to one or more specific stores (store filter), so you only receive events for those stores.


    ## Security

    All webhooks support HTTP Basic Authentication. If you provide a username and password, ShipMonk will include these credentials
    in the webhook request. This allows you to restrict access and ensure only ShipMonk can call your endpoints.


    ## Data Integrity

    Each webhook request sent by ShipMonk includes an `X-Sm-Signature` header. This header allows you to verify that the request
    genuinely originated from ShipMonk and was not tampered with.


    To enable this verification, you must provide ShipMonk with a secret key (a random string of your choice). For every webhook,
    ShipMonk uses this secret key to generate a HMAC using the SHA-512 algorithm (HMAC-SHA512), applied to the raw payload.
    The resulting signature is included in the `X-Sm-Signature` header.


    To validate the authenticity of a webhook:

    - Retrieve the raw payload from the HTTP POST request.

    - Using the same secret key and the HMAC-SHA512 algorithm, generate a signature from the payload.

    - Compare your generated signature to the value in the X-Sm-Signature header.

    - If they match, you can safely trust the request.


    This mechanism ensures both the integrity and authenticity of the webhook payload.


    ## Accepting the webhook


    Webhook requests are sent as HTTP POST requests. To acknowledge successful processing, your endpoint must respond with
    an HTTP status code in the 2xx range.

    - If a 2xx response is returned, the webhook is considered successfully delivered.

    - For any other response, ShipMonk will retry the webhook delivery up to 8 times using an exponential backoff schedule.
    The delay starts at 30 seconds and doubles after each attempt — 30s, 1m, 2m, 4m, 8m, 16m, 32m, 60m (capped at 60 minutes)
    — spanning roughly 2 hours before delivery is abandoned.'
  humanURL: https://apidocs.shipmonk.com/reference/webhooks
  baseURL: https://api.shipmonk.com
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/shipmonk-webhooks-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- url: https://www.shipmonk.com/feed
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/shipmonk-capability-edges.yml
  name: ShipMonk Business Capability Map
- type: Overlay
  url: overlays/shipmonk-orders-overlay.yaml
- type: Website
  url: https://www.shipmonk.com/
- type: DeveloperPortal
  url: https://apidocs.shipmonk.com/
- type: Documentation
  url: https://apidocs.shipmonk.com/docs/intro
- type: APIReference
  url: https://apidocs.shipmonk.com/reference
- type: GettingStarted
  url: https://apidocs.shipmonk.com/reference/common
- type: OpenAPI
  url: https://apidocs.shipmonk.com/openapi/public_api.json
- type: Support
  url: https://support.shipmonk.com/s/
- type: Blog
  url: https://www.shipmonk.com/resources/content-hub
- type: GitHubOrganization
  url: https://github.com/shipmonk-rnd
- type: Pricing
  url: https://www.shipmonk.com/pricing/
- type: SignUp
  url: https://www.shipmonk.com/get-a-quote
- type: Login
  url: https://app.shipmonk.com/
- type: TermsOfService
  url: https://www.shipmonk.com/terms-of-service
- type: PrivacyPolicy
  url: https://www.shipmonk.com/privacy-policy
- type: StatusPage
  url: https://status.shipmonk.com
- type: ChangeLog
  url: https://apidocs.shipmonk.com/changelog
- type: ChangeLog
  url: changelog/shipmonk-changelog.yml
- type: Compliance
  url: https://www.shipmonk.com/resources/content-hub/soc-2-type-ii-compliance
- type: TrustCenter
  url: security/shipmonk-trust-center.yml
- type: Security
  url: https://app.shipmonk.com/.well-known/security.txt
- type: VulnerabilityDisclosure
  url: security/shipmonk-vulnerability-disclosure.yml
- type: SecurityTxt
  url: well-known/shipmonk-security.txt
- type: DomainSecurity
  url: security/shipmonk-domain-security.yml
- type: WellKnown
  url: well-known/shipmonk-well-known.yml
- type: APICatalog
  url: well-known/shipmonk-api-catalog.json
- type: Authentication
  url: authentication/shipmonk-authentication.yml
- type: Conventions
  url: conventions/shipmonk-conventions.yml
- type: Idempotency
  url: conventions/shipmonk-conventions.yml
- type: ErrorCatalog
  url: errors/shipmonk-problem-types.yml
- type: RateLimits
  url: rate-limits/shipmonk-rate-limits.yml
- type: Lifecycle
  url: lifecycle/shipmonk-lifecycle.yml
- type: Conformance
  url: conformance/shipmonk-conformance.yml
- type: Sandbox
  url: sandbox/shipmonk-sandbox.yml
- type: DataModel
  url: data-model/shipmonk-data-model.yml
- type: Packages
  url: packages/shipmonk-packages.yml
- type: AsyncAPI
  url: asyncapi/shipmonk-webhooks-asyncapi.yml
- type: Webhooks
  url: https://apidocs.shipmonk.com/reference/webhooks
- type: MCPServer
  url: mcp/shipmonk-mcp.yml
- type: ToolCrosswalk
  url: mcp/shipmonk-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: AgenticAccess
  url: agentic-access/shipmonk-agentic-access.yml
- type: LLMsTxt
  url: llms/shipmonk-llms.txt
x-enrichment:
  date: '2026-08-02'
  status: enriched
  artifacts_added: 34
  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/shipmonk"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/shipmonk/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.

GitHub Google LinkedIn

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