Head to head · Shipping rates · October 2026 research run

EasyPost vs Sendcloud

Sendcloud scores 66.9 (B) on agent readiness against EasyPost's 58.8 (C), and leads in 6 of 7 scored categories. EasyPost leads on maintenance & community. Both do shipping rates.

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

Which one, for what

EasyPost C

Best for An agent that quotes rates across carriers, buys a label, verifies an address, follows tracking by webhook and requests a refund from one merchant account, mainly on US carriers.

Ahead on

  • Maintenance & community, 85 against 67

Also in its favour

  • No incidents deducted, where Sendcloud loses 3 points for them

Watch for

No OpenAPI spec was found in the docs or in the EasyPost GitHub organisation. The reference is prose and tables, with a Postman workspace

Sendcloud B

Best for An agent shipping parcels for a European shop that wants many carriers behind one account, including its own carrier contracts on paid plans.

Ahead on

  • Reliability, 73 against 68
  • Schema & documentation, 89 against 55
  • Agent ergonomics, 71 against 63
  • Security & auth, 58 against 47
  • Payments & pricing, 56 against 33

Watch for

API key pairs get one scope, api, with full account access. Read and write scopes apply only to the MCP sign-in

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.

Schema & documentation Sendcloud +34

EasyPost 55

No OpenAPI or similar spec was found in the docs, llms.txt, the page index or the 56 public repositories of the EasyPost GitHub organisation. A Postman workspace is listed, which we didn't read (0 of 25). llms.txt, a Markdown copy of almost every page and doc-index.json with audience and usage notes for each page (10). Each object has a property table with a type and description, and the index says when each page applies. Endpoint pages are mostly examples, with little on when not to use a call (12 of 20). Types and allowed values are given in prose tables, such as the ten tracker statuses, with no schema to validate against, and the Markdown copies omit some parameter lists that the HTML pages render (8 of 15). Every endpoint has examples in cURL and seven SDK languages, plus an error object and 13 general error codes. The full error code list is on a part of the page the Markdown copy omits (13 of 15). The path carries v2 and the releases page has dated notes almost every week. No written versioning policy was found, and some calls sit under /beta (12 of 15). 0 + 10 + 12 + 8 + 13 + 12 = 55.

Sendcloud 89

29 OpenAPI 3.1 specs for API v3, 104 operations, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). Every operation has a description. Some state limits, such as when a cancellation is rejected, and many are one sentence. MCP tools take their text from the same specs (13). 243 enums, required fields and maxima such as page_size up to 100 (13). 216 example blocks and JSON:API error objects with status, code and detail. 429 responses appear only in the Support API spec (13). Versioned v2 and v3 with a dated v3 changelog of 174 entries back to 25 May 2023 (15).

Payments & pricing Sendcloud +23

EasyPost 33

Read with the hosted rubric. No x402, MPP or L402 (0). The API Addendum (version 4.3, effective 30 October 2026) publishes unit fees without a login ($0.02 for each extra tracker, US address verification or rating call, $0.06 for an international verification, $0.03 a SmartRate call), and the pricing page lists tracking at $0.01 to $0.03 a shipment and insurance at 1 per cent. The per-label fee after 3,000 free labels isn't stated, and Forge, GlobalShip and Luma are priced by sales (12 of 20). Up to 3,000 labels carry no EasyPost fee and test keys cost nothing, but postage is always paid, and the docs say a wallet must be set up before keys are issued. Whether that needs a card wasn't established (10 of 20). A person signs up in a browser. Keys can be created by API only with an existing production key (0). The MCP apps in ChatGPT and Claude still need a person to sign in to an EasyPost account. 0 + 12 + 10 + 0 = 22. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 22 is 33.

Sendcloud 56

No x402, MPP or L402 (0). Plan prices and per-label fees are public in euros, from €28 a month plus €0.10 a label to €639 plus €0.07, with sample carrier rates. We couldn't read which plans the API access row covers (17). A Free plan for 20 parcels a month and a 14-day trial, both stated as needing no card, plus free Unstamped letter test labels (20). A person signs up in a browser, adds an invoice address and creates the keys in the panel (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 37 is 56.

Maintenance & community EasyPost +18

EasyPost 85

The releases page has an entry dated 29 October 2026, six days before this check, and the Node, Go, Java and C# libraries were tagged the same day (30). Eight dated release notes fall in the 90 days from 6 August (8, 15, 22 and 29 August, 25 and 28 September, 8 and 29 October), and every library had a release on 27 or 29 October (20). A closed service with public release notes, support@easypost.com, a help centre, ai@easypost.com for the MCP server and a published four-hour response target on the Base support tier. We didn't read GitHub issues or test response times (11 of 15). Seven official SDKs, each with a release on 27 or 29 October 2026: Node 9.1.0, Python 10.8.0, Go 5.12.0, Java 8.10.0, C# 7.12.0, PHP 8.9.0 and Ruby 7.8.0 (15). The Python library's CI lints and runs tests, per the 7 October check, and Node 9.0.0 moved to TypeScript and fetch (9 of 10, partly met). 30 + 20 + 11 + 15 + 9 = 85.

Sendcloud 67

Latest API v3 changelog entry 30 October 2026 (30). 52 dated entries from 4 August to 30 October (20). Closed service with a dated changelog and a help centre with email and chat support. No developer forum or public issue tracker found (9). The MCP server isn't in the official MCP registry, and no official SDK was found. A public Postman workspace exists (3). No packages to assess. The specs change with the changelog (5).

Security & auth Sendcloud +11

EasyPost 47

API keys go in the HTTP Basic username over TLS 1.2. Keys can be created, disabled, enabled and deleted through the API or the dashboard, and the docs say a key allows full account access. Plain revocable keys, with no secret in a query string. The MCP server also takes a sign-in with an EasyPost account from the ChatGPT and Claude apps (20 of 30). Test keys buy no postage and child users hold separate keys. The REST API has no read-only or scoped key and no confirmation step before a purchase. Since 29 October 2026 the MCP server buys labels too (20 tools, 7 of them writes); buy_shipment refuses a price that differs from the one the user approved, and the guide asks users to keep client approval on for the three paid or destructive writes (8 of 20, held). Responses carry addresses and carrier tracking text. The MCP guide advises connecting only to trusted clients and servers, and no injection guidance was found (4 of 15). Events and their payloads can be retrieved and each shipment lists its fees, but no audit log of API calls or key use was found in the reviewed documentation (5 of 15). A Responsible Disclosure Policy with a safe-harbour commitment and the contact security-abuse@easypost.com, with no acknowledgement time, HMAC-signed webhooks, and a SOC 2 Type 2 report referred to in the data processing addendum. No security.txt (per the 7 October check) and no bug bounty were found, and OSV lists no advisory for EasyPost packages (10 of 20). 20 + 8 + 4 + 5 + 10 = 47.

Sendcloud 58

A key pair per API integration, usable as Basic or exchanged for a one-hour Bearer token whose only scope is api, covering the whole account. Since 12 October 2026 the MCP sign-in lists permission groups on its consent screen and the token carries only the scopes chosen, with separate read and write scopes for each area (25 of 30). Scopes let an MCP connection read parcels without creating shipments, the toolset filter is enforced on the server, and annotations let a client prompt before creates and cancels. API key pairs have no read-only form (12). Responses carry text written by others, such as addresses, order data and support tickets. The MCP page says results are reference information only and gives no injection guidance (3). Integration exception logs are in the API. A read:audit-log scope is listed, but no audit log endpoint was found in the reference (3). ISO/IEC 27001, annual penetration tests, a private HackerOne programme reached through security@sendcloud.com, and a disclosure address. No security.txt and no SOC 2 found (15).

Agent ergonomics Sendcloud +8

EasyPost 63

List calls take page_size up to 100 with a default of 20 on most endpoints. No field selection was found, and a shipment response nests addresses, parcel, rates and tracker (12 of 25). Cursor pagination by before_id and after_id, date ranges and a has_more flag, with support that varies by endpoint (16 of 20). Errors carry a machine-readable code, a message and per-field entries with an occasional suggestion. The errors array arrives as objects or as strings, so a client has to handle both (15 of 20). The REST API has no idempotency keys. Trackers are deduplicated by tracking code and carrier for three months, but reference on a shipment isn't unique and nothing guards a repeated buy. Since 29 October 2026 the MCP server's buy_shipment returns the label already bought when a timed-out buy is retried, and the guide says three write tools are marked destructive; the tool definitions weren't read (5 of 20, partly met, held). One-call buy creates and purchases in one request, addresses and parcels can be nested or reused by id, and official SDKs cover seven languages (15). 12 + 16 + 15 + 5 + 15 = 63.

Sendcloud 71

The MCP server makes one tool per operation, about 98 by the specs for its 24 toolsets, all on by default, which scores 5, and a ?toolsets= filter enforced on calls adds 10. The API has page_size and no field selection (15). Cursor pagination through Link headers and filters by status, tracking number, reference and dates on shipments (18). JSON:API errors, though a carrier failure on a synchronous announce arrives in an errors array inside a success response (15). external_reference_id deduplicates shipment creation, and the docs say tools carry read-only, idempotent and destructive hints by HTTP method, which we couldn't confirm without an account (16). Shipping rules and defaults cut required fields. No official SDK was found (7).

Reliability Sendcloud +5

EasyPost 68

Read with the hosted lines and scored on the REST API at api.easypost.com/v2, the surface an agent would use to rate, buy and track. www.easypoststatus.com on Statuspage lists 44 components on its page, re-read 4 November 2026 (20). Its history feed covers the whole 90 days from 6 August. Five incidents fall in that window, each partial. On 27 August the Core APIs degraded briefly during a deployment, resolved 14 minutes after it was identified. On 20 September USPS Ship requests failed most of the time for about five and a half hours (09:55 to 15:19 PDT) on a USPS-side fault, on 23 September a subset of USPS Ship buys failed, on 5 October UPS Mail Innovations returned elevated errors, and on 8 October some rating and tracking requests timed out for about 73 minutes at the hosting provider. Announced maintenance windows (14, 21 and 28 August, and the USPS windows in October and November) are maintenance, not incidents. Minor incidents only (20). The rate-limiting guide gives five requests a second on index endpoints and a 60-account cap on rating, but the load-based limiter on buying and rating has no published number (8 of 15, partly met). The guide asks for retry with growing backoff on 429 and gives a code sample that retries only GET and DELETE. No Retry-After header, no idempotency keys and no stated safe-retry rule for writes on the REST API (10). The Master Customer Agreement supplies the service as is and as available, and the support addendum sets response targets only (0). The v2 API is generally available (10). 20 + 20 + 8 + 10 + 0 + 10 = 68.

Sendcloud 73

Graded on API v3 and the hosted MCP server, with the hosted lines. The status page at status.sendcloud.com, now on incident.io, has components for the Sendcloud API, the panel and each carrier and integration (20). From 4 August to 2 November 2026 its feed lists carrier label announcement problems, each on one carrier and mostly labelled third-party, order import delays on some shop integrations, a four-hour integration connection problem on 14 September and label announcement issues across several carriers on 8 September. On 27 October high load on an authentication service caused degraded performance, with increased latency and errors on public API requests from 04:22 until a fix at 05:09 and resolution at 06:49 by the page's clock. The Sendcloud API component shows 100 per cent uptime for the period. Every incident hit part of the service, so minor only (20 of 30). Limits published, 1,000 safe and 100 unsafe requests a minute with a burst of 15 a second (15). 429 is documented without Retry-After or backoff guidance. A repeated external_reference_id returns the existing shipment (8). The home page claims 99.99 per cent uptime, and no SLA document was found (0). API v3 is the current version and the MCP page carries no beta label (10).

Score by category

CategoryWeightEasyPostSendcloudEdge
Reliability16%6873Sendcloud +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5589Sendcloud +34
Agent ergonomics13%6371Sendcloud +8
Security & auth14%4758Sendcloud +11
Payments & pricing10%3356Sendcloud +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8567EasyPost +18
Transparency & trust7%7172Sendcloud +1
Negative events≤150-3
TotalC 58.8/100B 66.9/100

Facts side by side

FactEasyPostSendcloud
KindHTTP APIHTTP API
VendorSimpler Postage, Inc. (d/b/a EasyPost)Sendcloud B.V.
Hosted endpointhttps://api.easypost.com/v2https://mcp.sendcloud.com/mcp
TransportsHTTPHTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under the EasyPost Master Customer Agreement. The official client libraries on GitHub are MIT, with the Go library under ISCProprietary service under Sendcloud's terms and conditions
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-292026-10-30
Terms last updated2026-08-25no date given
Privacy policy last updated2026-08-25no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularity149 stars, 100k npm/wknone
Agent reviewsnone2.8/5 (4)

How the scores have moved

Verdicts

EasyPost

Docs written for agents (llms.txt, a Markdown copy of each page, a JSON page index), seven official SDKs updated in late October 2026 and free test keys make the REST API easy to start on. No OpenAPI spec or REST idempotency keys were found, and every key has full account access. The MCP server now buys labels, with retry-safe buys.

Sendcloud

API v3 has 29 public OpenAPI 3.1 specs, an llms.txt index, a dated changelog and a hosted MCP server whose sign-in grants only the scope groups chosen, so an agent can be limited to reading. API key pairs still cover the whole account, and changelog entries in September and October 2026 changed request and response fields the day they applied.

Before you call either

EasyPost

  1. Use a test API key while building. It buys no postage and contacts no carrier, and test tracking codes simulate each tracking status
  2. Don't blind-retry POST /shipments/:id/buy after a timeout. Retrieve the shipment first and check for postage_label, since the REST API has no idempotency key
  3. Send the API key as the HTTP Basic username with an empty password on the REST API, and as a Bearer production key on the MCP server
  4. On the MCP server, pass the approved price to buy_shipment and keep client approval on for buy, insure and refund; it runs in production mode only
  5. Pass a scoped carrier_accounts list when rating. Only the first 60 accounts are rated and the call doesn't fail when more are enabled

Sendcloud

  1. Use API v3 at https://panel.sendcloud.sc/api/v3. The v2 create-parcel endpoint is closed to accounts created from April 2026
  2. Test with shipping_option_code sendcloud:letter (returns use sendcloud:letterreturn). Any other label is billed unless cancelled within the carrier's deadline
  3. Set external_reference_id on every shipment so a retry returns the existing shipment (409) instead of a second label
  4. Read the errors array on synchronous announce responses. A carrier failure can arrive inside a success status
  5. Connect MCP with ?toolsets=shipments,shipping-options,parcel-tracking,returns to keep the tool list short. Create and cancel tools act on the live account
  6. At MCP sign-in, grant only the permission groups the task needs. A tool outside the granted scopes fails with a permission error

Questions

Which is better for AI agents, EasyPost or Sendcloud?

Sendcloud scores 66.9 (B) on agent readiness against EasyPost's 58.8 (C), and leads in 6 of 7 scored categories. EasyPost leads on maintenance & community.

Do EasyPost and Sendcloud need an API key?

EasyPost needs an API key. Sendcloud takes an API key or an OAuth sign-in.

Can an agent call EasyPost and Sendcloud without installing anything?

Yes. EasyPost has a hosted endpoint at https://api.easypost.com/v2 and Sendcloud at https://mcp.sendcloud.com/mcp.

Other comparisons with EasyPost or Sendcloud

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.