Head to head · Shipping rates · October 2026 research run
Sendcloud vs ShippyPro
Sendcloud scores 62 (B) on agent readiness against ShippyPro's 48.7 (D), and leads in 5 of 7 scored categories. 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 64
- Agent ergonomics, 71 against 46
- Payments & pricing, 37 against 5
- Maintenance & community, 67 against 25
- Transparency & trust, 72 against 58
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 A European shipper or logistics platform with its own carrier contracts that already holds a ShippyPro Enterprise plan and wants rates, labels, pickups and tracking across many regional carriers through one API.
Also in its favour
- No incidents deducted, where Sendcloud loses 3 points for them
Watch for
The help centre says APIs can only be activated with an Enterprise plan, which has no public price and starts with sales
Score by category
| Category | Weight this run | Sendcloud | ShippyPro | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 70 | ShippyPro +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 64 | Sendcloud +25 |
| Agent ergonomics | 13%16.2 | 71 | 46 | Sendcloud +25 |
| Security & auth | 14%17.5 | 49 | 51 | ShippyPro +2 |
| Payments & pricing | 10%12.5 | 37 | 5 | Sendcloud +32 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 67 | 25 | Sendcloud +42 |
| Transparency & trust | 7%8.8 | 72 | 58 | Sendcloud +14 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 62 · B | 48.7 · D |
Facts side by side
| Fact | Sendcloud | ShippyPro |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Sendcloud B.V. | Italian Valley S.r.l. |
| Hosted endpoint | https://mcp.sendcloud.com/mcp | https://api.shippypro.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under Sendcloud's terms and conditions | Proprietary service under ShippyPro's Terms & Conditions. Both OpenAPI files state the licence as Proprietary |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-10-05 | none |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| 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 | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
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.
ShippyPro
Two OpenAPI 3.1 files, a published limit of 20 calls per 10 seconds and a 99.5 per cent monthly SLA with service credits are public. API access needs an Enterprise plan arranged through sales, no changelog or SDK was found, and label creation on v1 has no idempotency key.
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
ShippyPro
- Send
Authorization: Bearer <API key>and POST a JSON body withMethodandParamstohttps://api.shippypro.com/v1/<Method>. Parameter names are case-sensitive - Check
StatusandErrorMessagein everyShipresponse. HTTP 200 withStatus2 means no label was created - Before retrying a failed
Shipcall, look the order up byTransactionID. v1 has no idempotency key, and each label counts against the plan - Test with the Generic carrier.
ShipandEditcalls on a real carrier create real labels - Stay under 20 calls per 10 seconds, and use webhooks for tracking. The docs advise against
GetTrackingin bulk
Questions
Which is better for AI agents, Sendcloud or ShippyPro?
Sendcloud scores 62 (B) on agent readiness against ShippyPro's 48.7 (D), and leads in 5 of 7 scored categories.
Do Sendcloud and ShippyPro need an API key?
Sendcloud takes an API key or an OAuth sign-in. ShippyPro needs an API key.
Can an agent call Sendcloud and ShippyPro without installing anything?
Yes. Sendcloud has a hosted endpoint at https://mcp.sendcloud.com/mcp and ShippyPro at https://api.shippypro.com.
Other comparisons with Sendcloud or ShippyPro
Machine-readable
- This page as Markdown
/compare/sendcloud-vs-shippypro.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/sendcloud.json·/api/v1/tools/shippypro.json - From a terminal
anchor compare sendcloud shippypro(the CLI) - Over MCP
compare_tools {"a": "sendcloud", "b": "shippypro"}at/mcp, no key