Head to head · Shipping rates · October 2026 research run
Sendcloud vs ShipBob
Sendcloud scores 62 (B) on agent readiness against ShipBob's 60.8 (C), and leads in 4 of 7 scored categories. ShipBob leads on reliability, security & auth and transparency & trust. 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
- Agent ergonomics, 71 against 56
- Payments & pricing, 37 against 20
- Maintenance & community, 67 against 41
Watch for
One OAuth scope, api, and key pairs with full account access. No read-only credential was found in the reviewed documentation
ShipBob C
Good for An agent working for a merchant that already stores stock with ShipBob, to create and track orders, check inventory, book inbound stock and handle returns.
Ahead on
- Reliability, 77 against 68
- Security & auth, 55 against 49
- Transparency & trust, 77 against 72
Also in its favour
- No incidents deducted, where Sendcloud loses 3 points for them
Watch for
No public price. Receiving, storage and pick, pack and ship fees come only in a quote from sales
Score by category
| Category | Weight this run | Sendcloud | ShipBob | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 68 | 77 | ShipBob +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 85 | Sendcloud +4 |
| Agent ergonomics | 13%16.2 | 71 | 56 | Sendcloud +15 |
| Security & auth | 14%17.5 | 49 | 55 | ShipBob +6 |
| Payments & pricing | 10%12.5 | 37 | 20 | Sendcloud +17 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 67 | 41 | Sendcloud +26 |
| Transparency & trust | 7%8.8 | 72 | 77 | ShipBob +5 |
| Negative events | ≤15 | -3 | 0 | |
| Total | 62 · B | 60.8 · C |
Facts side by side
| Fact | Sendcloud | ShipBob |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Sendcloud B.V. | ShipBob, Inc. |
| Hosted endpoint | https://mcp.sendcloud.com/mcp | https://api.shipbob.com |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service under Sendcloud's terms and conditions | Proprietary service under ShipBob's Terms of Service. The MCP tutorials repository on GitHub has no licence file |
| Tools exposed | none | 73 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-05 | 2026-07-31 |
| Terms last updated | no date given | 2026-05-22 |
| Privacy policy last updated | no date given | 2024-03-29 |
| 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 | 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.
ShipBob
OAuth with PKCE and read and write scopes per domain, a free sandbox, a public OpenAPI spec per version and a 24-month support window for each API version are documented. Fulfilment prices are by quote only, the status page has no API component, no official SDK was found, and Personal Access Tokens never expire and carry full account access.
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
ShipBob
- Call
GET /2026-07/channelfirst and send the ID of the channel with_writescopes in theshipbob_channel_idheader on every write - Build against
https://sandbox-api.shipbob.comwith a sandbox account. Sandbox and production accounts, tokens and data are separate - Set a stable
reference_idon each order, product and return. A duplicate returns 422, which is the only guard against a double create - Stay under 150 requests a minute per user and application, and wait the seconds given in
x-retry-afterafter a 429 - Over MCP, writes work only on records in the channel created at consent. A 403 or 404 on a cancel usually means the record belongs to another channel
Questions
Which is better for AI agents, Sendcloud or ShipBob?
Sendcloud scores 62 (B) on agent readiness against ShipBob's 60.8 (C), and leads in 4 of 7 scored categories. ShipBob leads on reliability, security & auth and transparency & trust.
Do Sendcloud and ShipBob need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Sendcloud and ShipBob without installing anything?
Yes. Sendcloud has a hosted endpoint at https://mcp.sendcloud.com/mcp and ShipBob at https://api.shipbob.com.
Other comparisons with Sendcloud or ShipBob
Machine-readable
- This page as Markdown
/compare/sendcloud-vs-shipbob.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/sendcloud.json·/api/v1/tools/shipbob.json - From a terminal
anchor compare sendcloud shipbob(the CLI) - Over MCP
compare_tools {"a": "sendcloud", "b": "shipbob"}at/mcp, no key