Head to head · Shipping tracking · October 2026 research run
Sendcloud vs Ship24
Sendcloud scores 62 (B) on agent readiness against Ship24's 55 (C), and leads in 6 of 7 scored categories. Ship24 leads on maintenance & community. Both do shipping tracking.
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
- Reliability, 68 against 45
- Schema & documentation, 89 against 81
- Security & auth, 49 against 37
- Payments & pricing, 37 against 30
- Transparency & trust, 72 against 52
Watch for
One OAuth scope, api, and key pairs with full account access. No read-only credential was found in the reviewed documentation
Ship24 C
Good for An agent that only needs tracking events across many couriers, by webhook or by lookup, from a tracking number alone.
Ahead on
- Maintenance & community, 80 against 67
Also in its favour
- No incidents deducted, where Sendcloud loses 3 points for them
Watch for
No status page was found. status.ship24.com doesn't resolve, and neither the site nor the docs link to one
Score by category
| Category | Weight this run | Sendcloud | Ship24 | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 45 | Sendcloud +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 81 | Sendcloud +8 |
| Agent ergonomics | 13%16.2 | 71 | 68 | Sendcloud +3 |
| Security & auth | 14%17.5 | 49 | 37 | Sendcloud +12 |
| Payments & pricing | 10%12.5 | 37 | 30 | Sendcloud +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 67 | 80 | Ship24 +13 |
| Transparency & trust | 7%8.8 | 72 | 52 | Sendcloud +20 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 62 · B | 55 · C |
Facts side by side
| Fact | Sendcloud | Ship24 |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Sendcloud B.V. | Ship24 Limited |
| Hosted endpoint | https://mcp.sendcloud.com/mcp | https://api.ship24.com/public/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for shipping tracking | not published | $0.045 per transaction |
| x402 | no | no |
| Licence | Proprietary service under Sendcloud's terms and conditions | Proprietary service under Ship24's Terms and Conditions. The Node SDK and the AI plugin on GitHub are MIT |
| Tools exposed | none | 12 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| MCP registry | not listed | com.ship24/tracking-mcp |
| Last release | 2026-10-05 | 2026-10-06 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-08-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 0 stars, 79 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.
Ship24
The REST API and the hosted MCP server share one public OpenAPI 3.1 spec, numbered rate limits with Retry-After, and tracker creation that is idempotent by payload. No status page, SLA or security certification was found, API keys carry no scopes, and the API agreement and data processing agreement named in the terms aren't published.
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
Ship24
- Send
Authorization: Bearer apik_...tohttps://api.ship24.com/public/v1. The same key works on the MCP server, which lists tools without a key but answers 401 on calls - Store the
trackerIdor set a uniqueclientTrackerId. Tracking numbers aren't unique, and any changed field on a repeatPOST /trackerscreates a second tracker that uses quota - Allow up to 60 seconds for the first
POST /trackers/trackorPOST /tracking/searchcall, since results are fetched from the courier synchronously - Cache
GET /couriers. It is limited to one request a second and returns the whole courier list, and courier auto-detection usually makescourierCodeunnecessary - Check for
quota_limit_reachedandno_active_subscription.POST /tracking/searchneeds a separate per-call plan, and the free plan blocks at 10 shipments a month
Questions
Which is better for AI agents, Sendcloud or Ship24?
Sendcloud scores 62 (B) on agent readiness against Ship24's 55 (C), and leads in 6 of 7 scored categories. Ship24 leads on maintenance & community.
Do Sendcloud and Ship24 need an API key?
Sendcloud takes an API key or an OAuth sign-in. Ship24 needs an API key.
Can an agent call Sendcloud and Ship24 without installing anything?
Yes. Sendcloud has a hosted endpoint at https://mcp.sendcloud.com/mcp and Ship24 at https://api.ship24.com/public/v1.
Other comparisons with Sendcloud or Ship24
Machine-readable
- This page as Markdown
/compare/sendcloud-vs-ship24.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/sendcloud.json·/api/v1/tools/ship24.json - From a terminal
anchor compare sendcloud ship24(the CLI) - Over MCP
compare_tools {"a": "sendcloud", "b": "ship24"}at/mcp, no key