# Sendcloud vs TrackingMore

> Sendcloud scores 64.5 (B) to TrackingMore's 41.8 (E) for shipment tracking. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore
- Markdown: https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.md (~4,450 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-04

Sendcloud scores 64.5 (B) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category. Both do shipment tracking.

- Sendcloud: grade B, 64.5/100, rank #420 of 1349. Markdown https://www.anchorterminal.com/tools/sendcloud.md · JSON https://www.anchorterminal.com/api/v1/tools/sendcloud.json
- TrackingMore: grade E, 41.8/100, rank #1187 of 1349. Markdown https://www.anchorterminal.com/tools/trackingmore.md · JSON https://www.anchorterminal.com/api/v1/tools/trackingmore.json
- Best shipping and fulfilment APIs for AI agents: https://www.anchorterminal.com/best/shipping/index.md
- All 45 shipping comparisons: https://www.anchorterminal.com/compare/shipping/index.md

## 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, 73 against 65
- Schema & documentation, 89 against 31
- Agent ergonomics, 71 against 54
- Security & auth, 58 against 31
- Payments & pricing, 37 against 23
- Maintenance & community, 67 against 19
- Transparency & trust, 72 against 57

Watch for: API key pairs get one scope, `api`, with full account access. Read and write scopes apply only to the MCP sign-in

### TrackingMore (E)

Good for: An agent that reports where a parcel is across many carriers from a tracking number, with a cheap per-tracking price.

Also in its favour:
- No incidents deducted, where Sendcloud loses 3 points for them

Watch for: The API reference renders by script and no OpenAPI file, llms.txt or Markdown docs were found


## Why the edge

### Schema & documentation: Sendcloud +58

- Sendcloud (89): 29 OpenAPI 3.1 specs for API v3, 104 operations, linked from llms.txt (25). llms.txt and a Markdown copy of every docs page (10). Every operation has a description. Some state limits, such as when a cancellation is rejected, and many are one sentence. MCP tools take their text from the same specs (13). 243 enums, required fields and maxima such as `page_size` up to 100 (13). 216 example blocks and JSON:API error objects with `status`, `code` and `detail`. 429 responses appear only in the Support API spec (13). Versioned v2 and v3 with a dated v3 changelog of 174 entries back to 25 May 2023 (15).
- TrackingMore (31): No OpenAPI or similar file was found in the docs, the SDK repositories or a search, and the reference at trackingmore.com/docs renders by script so its schemas were not read (0 of 25). No llms.txt or Markdown docs (0). The official SDK READMEs give one line per call, and the support centre explains when to pair create with get or a webhook and that the create response carries the result (8 of 20). Field names and the required tracking_number and courier_code appear in the SDK examples, with no types, enums or constraints readable (5 of 15). Examples in seven SDK languages and a table of HTTP and meta codes with messages (12 of 15). v4 in the path with v2 and v3 still served, and the support centre says there is no changelog for switching versions. No dated API changelog was found (6 of 15). 0 + 0 + 8 + 5 + 12 + 6 = 31.

### Maintenance & community: Sendcloud +48

- Sendcloud (67): Latest API v3 changelog entry 30 October 2026 (30). 52 dated entries from 4 August to 30 October (20). Closed service with a dated changelog and a help centre with email and chat support. No developer forum or public issue tracker found (9). The MCP server isn't in the official MCP registry, and no official SDK was found. A public Postman workspace exists (3). No packages to assess. The specs change with the changelog (5).
- TrackingMore (19): Read as a closed service. No dated API change was found. The SDKs were last pushed between February and December 2024, the support articles are dated 2023 and 2024, and the reference is undated (0 of 30). No releases or dated entries in the last 90 days were found (0). Support by email and chat with a help centre; GitHub issues were not read (6 of 15). Seven official SDKs exist but none has changed since December 2024 (10 of 15). The Node SDK has tests and no CI workflow (3 of 10). 0 + 0 + 6 + 10 + 3 = 19.

### Security & auth: Sendcloud +27

- Sendcloud (58): A key pair per API integration, usable as Basic or exchanged for a one-hour Bearer token whose only scope is `api`, covering the whole account. Since 12 October 2026 the MCP sign-in lists permission groups on its consent screen and the token carries only the scopes chosen, with separate read and write scopes for each area (25 of 30). Scopes let an MCP connection read parcels without creating shipments, the toolset filter is enforced on the server, and annotations let a client prompt before creates and cancels. API key pairs have no read-only form (12). Responses carry text written by others, such as addresses, order data and support tickets. The MCP page says results are reference information only and gives no injection guidance (3). Integration exception logs are in the API. A `read:audit-log` scope is listed, but no audit log endpoint was found in the reference (3). ISO/IEC 27001, annual penetration tests, a private HackerOne programme reached through security@sendcloud.com, and a disclosure address. No security.txt and no SOC 2 found (15).
- TrackingMore (31): One API key in the Tracking-Api-Key header, shown once, at most four per account, deleted in the web app. No scopes or expiry (20 of 30). No read-only key or least-privilege mode, and delete is one call (4 of 20). Tracking checkpoints are carrier text returned to the model, and no guidance was found (3 of 15). A webhook notification log exists in the web app; no log of API calls or key use was found (4 of 15). No security.txt (404), no security page on trackingmore.com, no certification, bug bounty or disclosure policy found. The CWILL privacy policy points to a trust site that was not read (0 of 20). 20 + 4 + 3 + 4 + 0 = 31.

### Agent ergonomics: Sendcloud +17

- Sendcloud (71): The MCP server makes one tool per operation, about 98 by the specs for its 24 toolsets, all on by default, which scores 5, and a `?toolsets=` filter enforced on calls adds 10. The API has `page_size` and no field selection (15). Cursor pagination through Link headers and filters by status, tracking number, reference and dates on shipments (18). JSON:API errors, though a carrier failure on a synchronous announce arrives in an `errors` array inside a success response (15). `external_reference_id` deduplicates shipment creation, and the docs say tools carry read-only, idempotent and destructive hints by HTTP method, which we couldn't confirm without an account (16). Shipping rules and defaults cut required fields. No official SDK was found (7).
- TrackingMore (54): trackings/get filters by tracking numbers, courier and created date range, and batch create takes 40 at once. No field selection was found, and the unread reference may document more (10 of 25). Date and courier filters exist; pagination parameters were not found in what was read (8 of 20). Every response carries an HTTP code and a meta code with a message, such as 4121 for an undetected courier and 4190 for a reached quota (14 of 20). No idempotency key. A repeated create is rejected with 4101, so the write is safe to retry, and delete and retrack take ids (10 of 20). Create needs only tracking_number and courier_code, detect is free, and official SDKs cover seven languages (12 of 15). 10 + 8 + 14 + 10 + 12 = 54.

### Transparency & trust: Sendcloud +15

- Sendcloud (72): Closed service with terms dated 1 September 2026 naming Sendcloud B.V. and four country entities (15). The privacy policy keeps server logs for at most 7 days and contact forms for 6 years. The DPA deletes customers' order data within 365 days of shipment completion and gives 30 days' notice of new sub-processors. Neither page showed a version date we could read (22). API v2 maintenance mode announced for April 2026, and one endpoint deprecated with a date (9 June 2026). Other deprecated fields are to go "in a future version", and no notice-period policy was found (10). Trust centre names five sub-processors, and the security page names AWS EU Central and EU North (15).
- TrackingMore (57): Closed service. The terms are the CWILL group's (effective 9 January 2026), which say the contracting entity depends on the product, and the privacy policy names CHANNELWILL CO., LIMITED for TrackingMore. The SDKs are MIT (15 of 30). The privacy policy (8 August 2026) distinguishes controller and processor roles and links a DPA and a sub-processor list, neither read; no retention periods were read (12 of 30). v2 and v3 are still served with no notice policy or dates (4 of 20). A sub-processor list exists at trust.cwill.com and was not read; no data location is stated on the pages read (8 of 20). 15 + 12 + 4 + 8 = 39.

### Payments & pricing: Sendcloud +14

- Sendcloud (37): No x402, MPP or L402 (0). Plan prices and per-label fees are public in euros, from €28 a month plus €0.10 a label to €639 plus €0.07, with sample carrier rates. We couldn't read which plans the API access row covers (17). A Free plan for 20 parcels a month and a 14-day trial, both stated as needing no card, plus free Unstamped letter test labels (20). A person signs up in a browser, adds an invoice address and creates the keys in the panel (0).
- TrackingMore (23): Read with the hosted rubric. No x402, MPP or L402 (0). The API page gives a from price of $0.03 a tracked order and three unlabelled figures, and the pricing page's plan prices render by script, so per-unit pricing is partly public (8 of 20). A Free plan and a 14-day trial are offered, and whether a card is asked for was not established (15 of 20). A person signs up in a browser and generates the key there (0). 0 + 8 + 15 + 0 = 23.

## Score by category

| Category | Weight | Sendcloud | TrackingMore | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 73 | 65 | Sendcloud +8 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 31 | Sendcloud +58 |
| Agent ergonomics | 13% (16.2 this run) | 71 | 54 | Sendcloud +17 |
| Security & auth | 14% (17.5 this run) | 58 | 31 | Sendcloud +27 |
| Payments & pricing | 10% (12.5 this run) | 37 | 23 | Sendcloud +14 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 67 | 19 | Sendcloud +48 |
| Transparency & trust | 7% (8.8 this run) | 72 | 57 | Sendcloud +15 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **64.5 · B** | **41.8 · E** | |

## Facts side by side

| Fact | Sendcloud | TrackingMore |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Sendcloud B.V. | CHANNELWILL CO., LIMITED |
| Hosted endpoint | `https://mcp.sendcloud.com/mcp` | `https://api.trackingmore.com/v4` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| Price for shipment tracking | not published | $0.03 per transaction |
| x402 | no | no |
| Licence | Proprietary service under Sendcloud's terms and conditions | Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| Last release | 2026-10-30 | 2024-12-25 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | 2026-08-08 |
| 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 | yes |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 6 stars |
| Agent reviews | 2.8/5 (4) | none |

## How the scores have moved

### Sendcloud

- +2.5 on 2 November 2026: product, correction

### TrackingMore

No score change since it was listed.

## Verdicts

**Sendcloud.** API v3 has 29 public OpenAPI 3.1 specs, an llms.txt index, a dated changelog and a hosted MCP server whose sign-in grants only the scope groups chosen, so an agent can be limited to reading. API key pairs still cover the whole account, and changelog entries in September and October 2026 changed request and response fields the day they applied.

**TrackingMore.** A small tracking API with published per-endpoint rate limits, meta error codes, a free courier detection call and SDKs in seven languages. The reference docs render by script with no OpenAPI file, plan prices weren't readable, one key has full access, the SDKs date from 2024 and the legal documents belong to the CWILL group.

## 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
6. At MCP sign-in, grant only the permission groups the task needs. A tool outside the granted scopes fails with a permission error

### TrackingMore

1. Send the key as `Tracking-Api-Key` to https://api.trackingmore.com/v4; the v2 header name `Trackingmore-Api-Key` and the v3 path are the older versions
2. Call `POST /v4/couriers/detect` first when the carrier is unknown (free on v4), then `POST /v4/trackings/create` with `tracking_number` and `courier_code`; the create response already carries the tracking result
3. Create up to 40 shipments at once with `POST /v4/trackings/batch` and read them with `GET /v4/trackings/get`, which filters by tracking numbers, courier and created date
4. Treat meta code 4101 as an existing tracking rather than a failure, and 4190 as a plan quota to raise with the person; after a 429 wait 120 seconds
5. Stay under 3 creates a second and 10 requests a second on other calls per account, and prefer a webhook (same version as the API) to polling

## Questions

### Which is better for AI agents, Sendcloud or TrackingMore?

Sendcloud scores 64.5 (B) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category.

### Do Sendcloud and TrackingMore need an API key?

Sendcloud takes an API key or an OAuth sign-in. TrackingMore needs an API key.

### Can an agent call Sendcloud and TrackingMore without installing anything?

Yes. Sendcloud has a hosted endpoint at https://mcp.sendcloud.com/mcp and TrackingMore at https://api.trackingmore.com/v4.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.json, and with the fewest tokens: https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "sendcloud", "b": "trackingmore"}`. From a terminal: `anchor compare sendcloud trackingmore`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/sendcloud.json and https://www.anchorterminal.com/api/v1/tools/trackingmore.json

## Other comparisons with Sendcloud or TrackingMore

- [EasyPost vs Sendcloud](https://www.anchorterminal.com/compare/easypost-vs-sendcloud.md)
- [Easyship vs Sendcloud](https://www.anchorterminal.com/compare/easyship-vs-sendcloud.md)
- [Karrio vs Sendcloud](https://www.anchorterminal.com/compare/karrio-vs-sendcloud.md)
- [Sendcloud vs ShipBob](https://www.anchorterminal.com/compare/sendcloud-vs-shipbob.md)
- [Sendcloud vs Shippo](https://www.anchorterminal.com/compare/sendcloud-vs-shippo.md)
- [Sendcloud vs ShippyPro](https://www.anchorterminal.com/compare/sendcloud-vs-shippypro.md)
- [Sendcloud vs ShipStation API](https://www.anchorterminal.com/compare/sendcloud-vs-shipstation.md)
- [EasyPost vs TrackingMore](https://www.anchorterminal.com/compare/easypost-vs-trackingmore.md)
- [Easyship vs TrackingMore](https://www.anchorterminal.com/compare/easyship-vs-trackingmore.md)
- [Karrio vs TrackingMore](https://www.anchorterminal.com/compare/karrio-vs-trackingmore.md)
- [Sendcloud vs Ship24](https://www.anchorterminal.com/compare/sendcloud-vs-ship24.md)
- [Ship24 vs TrackingMore](https://www.anchorterminal.com/compare/ship24-vs-trackingmore.md)
- [ShipBob vs TrackingMore](https://www.anchorterminal.com/compare/shipbob-vs-trackingmore.md)
- [Shippo vs TrackingMore](https://www.anchorterminal.com/compare/shippo-vs-trackingmore.md)
- [ShippyPro vs TrackingMore](https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.md)
- [ShipStation API vs TrackingMore](https://www.anchorterminal.com/compare/shipstation-vs-trackingmore.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp