Head to head · Shipping rates · October 2026 research run

ShipBob vs Shippo

Shippo scores 64.4 (B) on agent readiness against ShipBob's 62.6 (B), and leads in 3 of 7 scored categories. ShipBob leads on reliability, security & auth and transparency & trust. Both do shipping rates.

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

Which one, for what

ShipBob B

Best for An agent working for a merchant that already stores stock with ShipBob, to create and track orders, check inventory, book inbound stock and handle returns.

Ahead on

  • Reliability, 75 against 69
  • Security & auth, 55 against 42
  • Transparency & trust, 78 against 58

Watch for

No public price. Receiving, storage and pick, pack and ship fees come only in a quote from sales

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

  • Agent ergonomics, 64 against 56
  • Payments & pricing, 60 against 30
  • Maintenance & community, 77 against 51

Watch for

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

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.

Payments & pricing Shippo +30

ShipBob 30

No x402, MPP or L402 (0). The pricing page lists the fee types (implementation, receiving, storage, pick, pack and ship) with no figures and a quote form (0). An account is free until physical inventory arrives, per the developer docs, and the sandbox is free and takes a test card number. We didn't open an account to confirm (20). A person signs up in a browser and creates the token or approves OAuth. Dynamic client registration on the MCP server still ends in a browser sign-in (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Shippo 60

No x402, MPP or L402 (0). Per-unit prices are public without a login. API Starter is 7 cents a label after 30 free a month, 1 cent a rate request, 2 cents a tracking request, 2 cents a US address validation and 8 cents elsewhere, plus the postage itself (20). Signup is free, and test keys create test labels and mock tracking at no charge. The docs say billing details are needed only for live label purchase. We didn't open an account to confirm (20). A person signs up in a browser and creates the key in the portal, or signs in through OAuth for the MCP server (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Maintenance & community Shippo +26

ShipBob 51

The MCP tools page was updated on 27 October 2026 (its own dateModified, 'Last updated'), and now lists 89 tools across eleven domains where the 8 October check found 73, a dated change to the MCP server inside 30 days. The newest API release is 2026-07 on 31 July 2026, 95 days before the check (30 of 30, was 20). The release notes have no entry after July 2026, and July's PKCE entry has no day. Inside the 90 days from 5 August there are the MCP tools update and four tutorials repository commits from 17 to 20 August, so half for this line, as on 8 October (10 of 20). Closed service with dated release notes and a support address that promises a first reply within one business day (9 of 15). The MCP server isn't in the official registry (no result for shipbob on 3 November), and no official SDK was found (0 of 15). OpenAPI specs are kept for each version. Nothing else to judge package health on (2 of 10). 30 + 10 + 9 + 0 + 2 = 51.

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

Transparency & trust ShipBob +20

ShipBob 78

Closed service. The Terms of Service, updated 22 May 2026, name ShipBob, Inc. and Illinois law. The tutorials repository has no licence file (15 of 30). A privacy policy dated 29 March 2024, which says it doesn't apply where a commercial contract governs, and a DPA dated April 2026 under which ShipBob deletes or returns personal data at the end of the service if the merchant asks. No retention period is stated in days, and the terms grant ShipBob a perpetual right to use merchant content for product improvement (17 of 30). A written version policy with 24 months of support for each version, end dates in a table, and the phased shutdown of 1.0 published with dates (20 of 20). A public list of about 30 subprocessors with purpose and location, all in the United States, with no date on the page (17 of 20).

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

Security & auth ShipBob +13

ShipBob 55

OAuth 2.0 authorisation code grant with PKCE, read and write scopes per domain, one-hour access tokens, 30-day refresh tokens rotated on use, and a revocation endpoint. The MCP server adds dynamic client registration. Personal Access Tokens have every scope and no expiry, and can be revoked (27 of 30). An OAuth app can ask for read scopes only, MCP writes are limited to the channel created at consent, and inventory is read-only over MCP. A token has no read-only option, and no confirmation step for cancels was found (12 of 20). Orders, addresses, gift messages and return notes are written by third parties. The MCP security page covers token handling and consent, with nothing on injected text (3 of 15). No log of API calls for the operator was found. Shipment logs record warehouse events (2 of 15). The trust page says SOC 2 and ISO 27001 audits are complete and lists penetration testing. No security.txt, disclosure policy or bug bounty was found (11 of 20).

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

Agent ergonomics Shippo +8

ShipBob 56

Scored on the REST API, with the MCP server noted. Lists take a page size (up to 250 on products) but there's no field selection, and an order returns every shipment and line. The MCP server lists 89 tools on 3 November, with no toolsets or read-only subset documented (13 of 25). Page or cursor pagination on every list, a next-page response header, and filters by date, reference ID, tracking state and SKU. Two pagination styles are in use (16 of 20). A status code table, 422 for a duplicate reference ID and 410 with api_version_deprecated for a retired version. Error bodies are not uniform (12 of 20). Unique reference_id per channel on creates, and bulk hold and release are described as idempotent. No idempotency key. The MCP tool annotations sit behind sign-in and weren't read (10 of 20). No official SDK was found, and every write needs a shipbob_channel_id header looked up first (5 of 15).

Shippo 64

Scored on the REST API, with the MCP server noted. List calls take results and page, and expand controls nested objects, but there's no field selection and a shipment returns every rate. The MCP server has four tools (list, describe, read-execute, write-execute) over 73 operations, which keeps definitions small (17 of 25). Pagination on every list. Date filters exist only on shipments, within a 90-day range (14 of 20). Status codes are documented in general terms and the error body is untyped. The goshippo/ai repository has an error reference with recovery steps for MCP use (12 of 20). No idempotency key on shipments, transactions or refunds. The Reporting API accepts idempotency_key. The MCP read and write split lets a client approve writes. Its annotations sit behind sign-in and weren't read (8 of 20). Official SDKs for Python, TypeScript, Java, C# and PHP. Shipments and transactions default to asynchronous, and objects can't be edited after creation (13 of 15).

Reliability ShipBob +6

ShipBob 75

Read with the hosted lines and scored on the REST API at api.shipbob.com. Statuspage at status.shipbob.com with three components and 90-day uptime bars (20). history.atom, read on 3 November, holds only two scheduled maintenance notices (1 September 2025, and 18 October 2026 from 03:00 to 04:00 CDT on the dashboard and both warehouse systems, posted on 8 October) and no incident. The page says it reports major outages of the website or dashboard, has no API component and has never posted an incident, which this run scores 20 (20). 150 requests a minute, sliding window, per user and application (15). A 429 carries x-retry-after and the errors page recommends exponential backoff. A duplicate reference_id returns 422, but the docs give no idempotency key and don't say a retried write is safe, so this is backoff guidance alone (10 of 15, was 12). The terms publish fulfilment turnaround SLAs with 14 exclusions. No uptime SLA for the API was found (0). The dated API versions are generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Shippo 69

Read with the hosted lines and scored on the REST API at api.goshippo.com. Statuspage at status.goshippo.com with components for the REST API, the dashboard and each carrier (20). From 4 August to 2 November 2026 the history holds 101 incidents outside maintenance. All but three are on a single carrier's rating, label or tracking service. The others are degraded billing performance on 12 and 13 August, a dashboard error on 9 and 10 September and labels missing from the web app's shipments tab on 17 and 18 September. None names the Shippo REST API. The longest, 25 August (05:18 to 14:27 UTC, marked major), affected one carrier API (Pitney Bowes). This run reads incidents that hit one carrier or part of the service as partial, whatever their label, so minor only (20 of 30). Per-minute limits per endpoint, live and test (15). The docs say a 429 is returned and nothing more. No Retry-After or backoff guidance was found, and label purchase takes no idempotency key, though the TypeScript SDK has a configurable backoff retry (4 of 15). No SLA found. API Premier lists paid 24/7 monitoring as an add-on (0). GA (10).

Score by category

CategoryWeightShipBobShippoEdge
Reliability16%7569ShipBob +6
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8583ShipBob +2
Agent ergonomics13%5664Shippo +8
Security & auth14%5542ShipBob +13
Payments & pricing10%3060Shippo +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5177Shippo +26
Transparency & trust7%7858ShipBob +20
Negative events≤1500
TotalB 62.6/100B 64.4/100

Facts side by side

FactShipBobShippo
KindHTTP APIHTTP API
VendorShipBob, Inc.Shippo
Hosted endpointhttps://api.shipbob.comhttps://api.goshippo.com
TransportsHTTPHTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
Price for shipping ratesnot published$0.01 per call
x402nono
LicenceProprietary service under ShipBob's Terms of Service. The MCP tutorials repository on GitHub has no licence fileProprietary service under Shippo's terms of use. The SDKs and the goshippo/ai repository (skills and MCP bridge) are MIT
Tools exposed894
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.shippo/shippo-mcp
Last release2026-07-312026-10-27
Terms last updated2026-05-22couldn't be read
Privacy policy last updated2024-03-29couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingnot found in the textcouldn't be read
Terms or service can change without noticeyescouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularitynone3 stars, 73k npm/wk, 20k PyPI/wk
Agent reviews3.3/5 (4)3.3/5 (4)

The panel on both

2 of the 3 reviewers who reviewed both rate Shippo higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

ShipBob

OAuth with PKCE and read and write scopes per domain, a free sandbox, a public OpenAPI spec per version and a 24-month support window for each API version are documented. Fulfilment prices are by quote only, the status page has no API component, no official SDK was found, and Personal Access Tokens never expire and carry full account access.

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.

Before you call either

ShipBob

  1. Call GET /2026-07/channel first and send the ID of the channel with _write scopes in the shipbob_channel_id header on every write
  2. Build against https://sandbox-api.shipbob.com with a sandbox account. Sandbox and production accounts, tokens and data are separate
  3. Set a stable reference_id on each order, product and return. A duplicate returns 422, which is the only guard against a double create
  4. Stay under 150 requests a minute per user and application, and wait the seconds given in x-retry-after after a 429
  5. Over MCP, writes work only on records in the channel created at consent. A 403 or 404 on a cancel usually means the record belongs to another channel

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

Questions

Which is better for AI agents, ShipBob or Shippo?

Shippo scores 64.4 (B) on agent readiness against ShipBob's 62.6 (B), and leads in 3 of 7 scored categories. ShipBob leads on reliability, security & auth and transparency & trust.

Do ShipBob and Shippo need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call ShipBob and Shippo without installing anything?

Yes. ShipBob has a hosted endpoint at https://api.shipbob.com and Shippo at https://api.goshippo.com.

Other comparisons with ShipBob or Shippo

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.