Head to head · Shipping rates · October 2026 research run
Sendcloud vs ShipStation API
Sendcloud scores 62 (B) on agent readiness against ShipStation API's 59.3 (C), and leads in 5 of 7 scored categories. ShipStation API leads on maintenance & community. Both do shipping rates.
Which one, for what
Good 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
- Schema & documentation, 89 against 83
- Agent ergonomics, 71 against 64
- Security & auth, 49 against 32
- Transparency & trust, 72 against 64
Watch for
One OAuth scope, api, and key pairs with full account access. No read-only credential was found in the reviewed documentation
Good 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
- Maintenance & community, 73 against 67
Also in its favour
- No incidents deducted, where Sendcloud loses 3 points for them
Watch for
One API key with full account access. No scopes, read-only keys or approval step before a label is bought
Score by category
| Category | Weight this run | Sendcloud | ShipStation API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 64 | Sendcloud +4 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 83 | Sendcloud +6 |
| Agent ergonomics | 13%16.2 | 71 | 64 | Sendcloud +7 |
| Security & auth | 14%17.5 | 49 | 32 | Sendcloud +17 |
| Payments & pricing | 10%12.5 | 37 | 40 | ShipStation API +3 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 67 | 73 | ShipStation API +6 |
| Transparency & trust | 7%8.8 | 72 | 64 | Sendcloud +8 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 62 · B | 59.3 · C |
Facts side by side
| Fact | Sendcloud | ShipStation API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Sendcloud B.V. | Auctane LLC d/b/a ShipStation |
| Hosted endpoint | https://mcp.sendcloud.com/mcp | https://api.shipstation.com/v2 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Sendcloud's terms and conditions | Proprietary service under ShipStation's terms of service. The v2 OpenAPI file is marked MIT and the SDKs on GitHub are Apache 2.0 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-10-01 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-03-18 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 6.8k npm/wk |
Verdicts
Sendcloud
API v3 has 29 public OpenAPI 3.1 specs, an llms.txt index, a dated changelog and a hosted MCP server with toolset filtering. OAuth has one scope, api, so a credential can't be limited to reading. The changelog records response fields removed from tracking events on 25 September 2026 with no earlier deprecation entry.
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, read-only mode or idempotency keys on label purchases.
Before you call either
Sendcloud
- Use API v3 at https://panel.sendcloud.sc/api/v3. The v2 create-parcel endpoint is closed to accounts created from April 2026
- Test with
shipping_option_codesendcloud:letter(returns usesendcloud:letterreturn). Any other label is billed unless cancelled within the carrier's deadline - Set
external_reference_idon every shipment so a retry returns the existing shipment (409) instead of a second label - Read the
errorsarray on synchronous announce responses. A carrier failure can arrive inside a success status - Connect MCP with
?toolsets=shipments,shipping-options,parcel-tracking,returnsto keep the tool list short. Create and cancel tools act on the live account
ShipStation API
- Send the key in an
API-Keyheader to https://api.shipstation.com/v2. A key that startsTEST_runs in the sandbox on the same host - Call GET /v2/carriers first. Rate and label calls need
carrier_idsor acarrier_idand aservice_codefrom that account - Don't blindly retry POST /v2/labels after a timeout. List labels first, then void a duplicate with PUT /v2/labels/{label_id}/void
- Check the
errorsarray on 2XX responses too, and readerror_sourceto tell a carrier fault from a ShipStation one - 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, Sendcloud or ShipStation API?
Sendcloud scores 62 (B) on agent readiness against ShipStation API's 59.3 (C), and leads in 5 of 7 scored categories. ShipStation API leads on maintenance & community.
Do Sendcloud and ShipStation API need an API key?
Sendcloud takes an API key or an OAuth sign-in. ShipStation API needs an API key.
Can an agent call Sendcloud and ShipStation API without installing anything?
Yes. Sendcloud has a hosted endpoint at https://mcp.sendcloud.com/mcp and ShipStation API at https://api.shipstation.com/v2.
Other comparisons with Sendcloud or ShipStation API
Machine-readable
- This page as Markdown
/compare/sendcloud-vs-shipstation.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/sendcloud.json·/api/v1/tools/shipstation.json - From a terminal
anchor compare sendcloud shipstation(the CLI) - Over MCP
compare_tools {"a": "sendcloud", "b": "shipstation"}at/mcp, no key