Head to head · Shipping rates · October 2026 research run

Shippo vs ShipStation API

Shippo scores 64.4 (B) on agent readiness against ShipStation API's 53.5 (D), and leads in 2 of 7 scored categories. ShipStation API leads on transparency & trust. Both do shipping rates.

Best shipping and fulfilment APIs for AI agents · All 66 shipping comparisons

Which one, for what

Shippo B

Best for An agent that quotes and buys parcel labels across USPS, UPS, FedEx and DHL Express for a small or mid-size shipper, with a free test mode and public unit prices.

Ahead on

  • Security & auth, 42 against 32
  • Maintenance & community, 77 against 33

Also in its favour

  • No incidents deducted, where ShipStation API loses 6 points for them

Watch for

No idempotency key on label purchase or other writes. Only the Reporting API accepts one

ShipStation API D

Best for An agent working inside a merchant's existing ShipStation account (orders, batches, inventory, labels), or a developer who wants a free sandbox through the ShipStation API plans.

Ahead on

  • Transparency & trust, 64 against 58

Watch for

One API key with full account access. No scopes, read-only keys or approval step before a label is bought

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community Shippo +44

Shippo 77

The API release notes were last updated on 20 October 2026, and the shippo npm SDK 2.19.1 was tagged on 27 October 2026 (30). Six dated entries from 4 August, the latest on 1, 8, 14 and 20 October, plus TypeScript SDK 2.19.0 and 2.19.1 (20). Closed service with dated release notes and a support portal. Open issue counts weren't re-read (9 of 15). The MCP server is in the official registry as com.shippo/shippo-mcp, verified by DNS. Official SDKs exist in five languages. The TypeScript SDK was regenerated in October, while the Python SDK's latest stable tag is 3.9.0 from 26 November 2024, with 5.0.0 in beta since 22 October 2026 (12 of 15). SDKs are generated and validated by CI workflows, and goshippo/ai has test and validation workflows, last tagged 23 July (6 of 10).

ShipStation API 33

Release notes on docs.shipstation.com are dated by month only, with entries for August, September and October 2026 on the 7 October reading, so they don't set recency. The newest dated change from ShipStation's own sources is the shipengine-openapi repository commit of 11 June 2026, after .NET SDK v3.2.1 on 27 May and Python 2.1.1 on 6 May (146 days, 10). No dated release in the 90 days from 6 August. Month-dated entries counted at half come to fewer than three, and commits on 27 October in the JavaScript and .NET SDK repositories are in no release (0). Closed service with monthly release notes, an API support address (apisupport@shipstation.com) and a community forum. We couldn't measure reply times (10). Official SDKs exist in six languages, and all call the v1 ShipEngine host. JavaScript's newest tag is v1.0.7 of 31 January 2024 (8). SDK repositories have CI workflows, and the JavaScript SDK's CI was rebuilt on 27 October. The OpenAPI repository was last changed on 11 June 2026 (5).

Security & auth Shippo +10

Shippo 42

Self-serve API keys, live and test kept apart, shown once, deletable in the portal, with no scopes and no documented expiry. The OAuth flow for platforms has one scope, "*". JWTs for client-side use last 12 hours (20 of 30). A webhook can carry a self-made token in its URL query string. That is the receiver's secret, not the API credential, so we noted it without the deduction. No read-only key. Test keys can't spend money, and the MCP server separates reads from writes and its docs say writes ask for confirmation (9 of 20). Tracking events, metadata and address text come from carriers and other parties. The AI repository's security policy puts prompt injection in scope for reports, with no guidance in the API docs (5 of 15). The API portal is described as showing usage. No audit log was found in the docs (3 of 15). The AI repository's security policy gives security@goshippo.com and names goshippo.com/security as the disclosure page, which returns 404, as does security.txt. The trust centre at trust.goshippo.com, where the 7 October check read SOC 2 Type II, PCI DSS, a penetration test and a bug bounty, now refuses our crawler, so those readings are set aside and unscored (5 of 20).

ShipStation API 32

One secret in an API-Key header. The docs say the key gives full access. Platform accounts hold one active v2 key that can be regenerated, and ShipStation API accounts have separate TEST_ sandbox keys (17). No scopes, read-only keys or confirmation before a label purchase. The sandbox key is the only lower-risk mode (5). Responses carry order text, addresses and carrier messages written by others, with no injection guidance (3). A request_id on every response. No per-key audit log found in the docs (3). TLS 1.2 or higher required, HSTS on the API host and RSA-SHA256 signed webhooks with a JWKS. security.txt returns 404 on three hosts, and no certification, bug bounty or disclosure policy was found on the pages we read (4). Docs, pricing and legal pages per the 7 October check, not re-read on 4 November.

Transparency & trust ShipStation API +6

Shippo 58

Closed service. The terms of use sit in a privacy centre that loads only with JavaScript, so we couldn't read them or confirm the contracting entity. SDKs and the goshippo/ai repository are MIT (12 of 30). The privacy notice has the same problem. The release notes say shipments and rates are retrievable for 390 days. The trust centre's DPA link and encryption statements, read on 7 October, are set aside because the host now refuses our crawler, and no retention periods were read (4 of 30). The versioning page says accounts are never forced onto a new API version, and notices carry dates, such as the 1 and 14 October 2026 notices of the EU product identifier requirement from 1 November. Carrier removals are announced on the day (12 of 20). Webhook addresses are published for US and EU regions. The trust centre's hosting and third-party statements are set aside, and no subprocessor list was found (3 of 20).

ShipStation API 64

Closed service under terms of service effective 16 July 2026 that name Auctane LLC d/b/a ShipStation. The v2 OpenAPI file is marked MIT and the SDKs are Apache 2.0 (16). The privacy policy, effective 18 March 2026, is Auctane, Inc.'s for all its brands. It keeps data "as long as necessary" with no periods, and says third parties may not train AI models on personal information. No public DPA was found (12). The legacy V1 API is described as deprecated with removal "in the future" and no date, and the terms let ShipStation withdraw API access at its discretion (6). US persons' data stays in the United States and EEA and UK data may move there under the Data Privacy Framework. Service providers are named by type, with no subprocessor list (8). Docs, pricing and legal pages per the 7 October check, not re-read on 4 November.

Score by category

CategoryWeightShippoShipStation APIEdge
Reliability16%6970ShipStation API +1
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8383even
Agent ergonomics13%6464even
Security & auth14%4232Shippo +10
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7733Shippo +44
Transparency & trust7%5864ShipStation API +6
Negative events≤150-6
TotalB 64.4/100D 53.5/100

Facts side by side

FactShippoShipStation API
KindHTTP APIHTTP API
VendorShippoAuctane LLC d/b/a ShipStation
Hosted endpointhttps://api.goshippo.comhttps://api.shipstation.com/v2
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for shipping rates$0.01 per callnot published
x402nono
LicenceProprietary service under Shippo's terms of use. The SDKs and the goshippo/ai repository (skills and MCP bridge) are MITProprietary service under ShipStation's terms of service. The v2 OpenAPI file is marked MIT and the SDKs on GitHub are Apache 2.0
Tools exposed4none
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.shippo/shippo-mcpnot listed
Last release2026-10-272026-10-01
Terms last updatedcouldn't be readno date given
Privacy policy last updatedcouldn't be read2026-03-18
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readyes
Popularity3 stars, 73k npm/wk, 20k PyPI/wk6.8k npm/wk
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Shippo

Per-label and per-call prices are public, test keys are self-serve, and the OpenAPI spec, llms.txt and Markdown docs are open to a fetch. Label purchase has no idempotency key, API keys carry no scopes, and the status page logged carrier-side incidents on most days from August to October 2026.

ShipStation API

A public OpenAPI 3.1 contract with 173 operations, Markdown docs for agents and a free ShipStation API plan with a sandbox make a first rate quote or test label reachable without a contract. One API key carries full account access, with no scopes or idempotency keys on label purchases, and API release notes carry month-only dates.

Before you call either

Shippo

  1. Build and test with a shippo_test_ key. Test and live object IDs are separate, and the hosted MCP server has no test mode
  2. Send Authorization: ShippoToken <key>, not Bearer, and pin Shippo-API-Version: 2018-02-08
  3. Before retrying a failed POST /transactions, list recent transactions. There is no idempotency key, and a second purchase is a second charge
  4. Pass async: false on shipments and transactions, or poll the object until its status leaves QUEUED
  5. Set results on list calls (under 200). Defaults vary by resource, and list calls are limited to 50 a minute on live keys

ShipStation API

  1. Send the key in an API-Key header to https://api.shipstation.com/v2. A key that starts TEST_ runs in the sandbox on the same host
  2. Call GET /v2/carriers first. Rate and label calls need carrier_ids or a carrier_id and a service_code from that account
  3. Don't blindly retry POST /v2/labels after a timeout. List labels first, then void a duplicate with PUT /v2/labels/{label_id}/void
  4. Check the errors array on 2XX responses too, and read error_source to tell a carrier fault from a ShipStation one
  5. On a platform (Standard or Premium) key every label is real and charged. Ask the owner before buying, and void test labels at once

Questions

Which is better for AI agents, Shippo or ShipStation API?

Shippo scores 64.4 (B) on agent readiness against ShipStation API's 53.5 (D), and leads in 2 of 7 scored categories. ShipStation API leads on transparency & trust.

Do Shippo and ShipStation API need an API key?

Shippo takes an API key or an OAuth sign-in. ShipStation API needs an API key.

Can an agent call Shippo and ShipStation API without installing anything?

Yes. Shippo has a hosted endpoint at https://api.goshippo.com and ShipStation API at https://api.shipstation.com/v2.

Other comparisons with Shippo or ShipStation API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.