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

Sendcloud B

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

CategoryWeight this runSendcloudShip24Edge
Reliability16%206845Sendcloud +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28981Sendcloud +8
Agent ergonomics13%16.27168Sendcloud +3
Security & auth14%17.54937Sendcloud +12
Payments & pricing10%12.53730Sendcloud +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86780Ship24 +13
Transparency & trust7%8.87252Sendcloud +20
Negative events≤15-30
Total62 · B55 · C

Facts side by side

FactSendcloudShip24
KindHTTP APIHTTP API
VendorSendcloud B.V.Ship24 Limited
Hosted endpointhttps://mcp.sendcloud.com/mcphttps://api.ship24.com/public/v1
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
Price for shipping trackingnot published$0.045 per transaction
x402nono
LicenceProprietary service under Sendcloud's terms and conditionsProprietary service under Ship24's Terms and Conditions. The Node SDK and the AI plugin on GitHub are MIT
Tools exposednone12
Read-only variant documentedyesyes
llms.txtyesyes
MCP registrynot listedcom.ship24/tracking-mcp
Last release2026-10-052026-10-06
Terms last updatedno date givenno date given
Privacy policy last updatedno date given2026-08-01
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularitynone0 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

  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

Ship24

  1. Send Authorization: Bearer apik_... to https://api.ship24.com/public/v1. The same key works on the MCP server, which lists tools without a key but answers 401 on calls
  2. Store the trackerId or set a unique clientTrackerId. Tracking numbers aren't unique, and any changed field on a repeat POST /trackers creates a second tracker that uses quota
  3. Allow up to 60 seconds for the first POST /trackers/track or POST /tracking/search call, since results are fetched from the courier synchronously
  4. Cache GET /couriers. It is limited to one request a second and returns the whole courier list, and courier auto-detection usually makes courierCode unnecessary
  5. Check for quota_limit_reached and no_active_subscription. POST /tracking/search needs 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

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.