{ "data": { "a": { "slug": "sendcloud", "name": "Sendcloud", "vendor": "Sendcloud B.V.", "vendorUrl": "https://www.sendcloud.com", "kind": "http-api", "category": "shipping", "summary": "Shipping platform for European online shops from Sendcloud B.V. in Eindhoven. Its API v3 and hosted MCP server quote carrier rates, create labels, validate addresses, track parcels and handle returns across the carriers an account has enabled.", "url": "https://www.anchorterminal.com/tools/sendcloud", "markdownUrl": "https://www.anchorterminal.com/tools/sendcloud.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sendcloud.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sendcloud.json", "dns": "sendcloud.grade.anchorterminal.com", "license": "Proprietary service under Sendcloud's terms and conditions", "transports": [ "http" ], "remoteUrl": "https://mcp.sendcloud.com/mcp", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A person signs up at account.sendcloud.com, adds an invoice and sender address, then creates a Sendcloud API integration in the panel, which issues a public and secret key pair. The pair works as HTTP Basic or is exchanged at https://account.sendcloud.com/oauth2/token for a one-hour Bearer token (client credentials, scope `api`). The MCP server uses an OAuth 2.0 sign-in at account.sendcloud.com, found through RFC 9728 metadata. Since 12 October 2026 its consent screen lists permission groups, and the token carries only the read and write scopes chosen. No partner or sales approval is needed for API v3.", "pricing": "freemium", "pricingNotes": "Free plan at €0 for up to 20 parcels a month at Sendcloud's carrier rates, and a 14-day trial of paid plans with no card per the pricing page. Lite is €28 a month plus €0.10 a label, Growth €87 plus €0.09, Premium €175 plus €0.08, Pro €639 plus €0.07, Enterprise on request, with 20 per cent off for yearly billing. Carrier postage is extra. There is no sandbox, but 50 Unstamped letter test labels are free. The pricing table has an API access row whose per-plan marks we couldn't read (https://www.sendcloud.com/pricing/).", "priceSummary": "$31.30 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI specs or the pricing page (checked 2026-10-07).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-07" }, "docsUrl": "https://sendcloud.dev", "llmsTxt": "https://sendcloud.dev/llms.txt", "openapi": "https://sendcloud.dev/.openapi/v3/shipments/openapi.yaml", "capabilities": [ "shipping.rates", "shipping.labels", "shipping.tracking", "shipping.address-validation", "shipping.returns" ], "tags": [ "hosted", "freemium", "free-tier", "mcp", "oauth", "api-key", "openapi", "llms-txt", "webhooks", "status-page", "europe", "iso27001" ], "lastRelease": "2026-10-30", "graded": true, "anchor": { "graded": true, "score": 64.5, "grade": "B", "agentReady": false, "rank": 420, "ranked": true, "rankOf": 1349, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 67, "payments": 37, "reliability": 73, "schema": 89, "security": 58, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": -3, "negativeNotes": [ "21 and 25 September 2026, with more of the same kind in October. The API v3 changelog records `insurance.currency` and `insurance.value` removed from POST /parcels/tracking, and `status_code`, `status_description` and `sub_status_code` removed from tracking event responses, with no earlier deprecation entry. Entries of 21 and 26 October make `type` required on event subscription connection updates, cut the parcels allowed on synchronous shipments with rules from 50 to 15, and reject fractional insured amounts, each announced the day it applies. Repeats of one kind count once, at the minimum (https://sendcloud.dev/api/v3/changelog.md)" ], "verdict": "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.", "bestFor": "An agent shipping parcels for a European shop that wants many carriers behind one account, including its own carrier contracts on paid plans.", "strengths": [ "29 public OpenAPI 3.1 specs covering 104 API v3 operations, with an llms.txt index and Markdown copies of every docs page", "Hosted MCP server at mcp.sendcloud.com/mcp with 24 toolsets, a `?toolsets=` filter, scope groups chosen at sign-in and read-only, idempotent and destructive annotations per the docs", "A repeated `external_reference_id` on shipment creation returns the existing shipment with a 409 instead of buying a second label", "Free test labels through the `sendcloud:letter` and `sendcloud:letterreturn` shipping options, up to 50 before charges apply", "Dated API v3 changelog with 52 entries between 4 August and 30 October 2026" ], "weaknesses": [ "API key pairs get one scope, `api`, with full account access. Read and write scopes apply only to the MCP sign-in", "Changelog entries of 21 and 25 September and 21 and 26 October 2026 removed fields or tightened requests on the day, with no earlier notice", "No Retry-After header or backoff guidance was found for 429 responses", "No official SDK was found in the reviewed documentation, and the MCP server isn't in the official MCP registry", "No test environment. Labels other than the Unstamped letter options are charged unless the carrier accepts a cancellation" ], "agentNotes": [ "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_code` `sendcloud:letter` (returns use `sendcloud:letterreturn`). Any other label is billed unless cancelled within the carrier's deadline", "Set `external_reference_id` on every shipment so a retry returns the existing shipment (409) instead of a second label", "Read the `errors` array on synchronous announce responses. A carrier failure can arrive inside a success status", "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", "At MCP sign-in, grant only the permission groups the task needs. A tool outside the granted scopes fails with a permission error" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.5 } ], "editorialScores": { "ergonomics": 71, "maintenance": 67, "payments": 37, "reliability": 73, "schema": 89, "security": 58, "transparency": 62 }, "provenanceScore": 82, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST --location \"https://account.sendcloud.com/oauth2/token\" \\\n --header \"Content-Type: application/x-www-form-urlencoded\" \\\n -d \"grant_type=client_credentials\u0026scope=api\" \\\n --basic --user your_sendcloud_public_key:your_sendcloud_private_key", "claudeCode": "claude mcp add --transport http sendcloud https://mcp.sendcloud.com/mcp", "config": { "mcpServers": { "sendcloud": { "type": "http", "url": "https://mcp.sendcloud.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/shipping.rates", "tool": "https://letme.dev/sendcloud" }, "area": "business", "unitPrices": [ { "item": "Lite plan", "unit": "month", "usd": 31.3, "note": "€28, 400 labels a month, plus €0.10 a label" }, { "item": "Growth plan", "unit": "month", "usd": 97.24, "note": "€87, 1,000 labels a month, plus €0.09 a label" }, { "item": "Premium plan", "unit": "month", "usd": 195.6, "note": "€175, 10,000 labels a month, plus €0.08 a label" }, { "item": "Pro plan", "unit": "month", "usd": 714.21, "note": "€639, 30,000 labels a month, plus €0.07 a label" }, { "item": "Label fee on Lite", "unit": "tx", "usd": 0.11, "note": "€0.10 a label on top of carrier postage, €0.25 above the monthly limit" } ], "provenance": { "legalEntity": "Sendcloud B.V.", "domain": "sendcloud.com", "domainRegistered": "2008-07-29", "endpointOnVendorDomain": true, "terms": "https://www.sendcloud.com/terms-conditions/", "privacy": "https://www.sendcloud.com/privacy-policy/", "statusPage": "https://status.sendcloud.com", "changelog": "https://sendcloud.dev/api/v3/changelog", "securityTxt": "none", "checked": "2026-10-07", "notes": [ "The terms, last updated 1 September 2026, name Sendcloud B.V., registration 66572959, Stadhuisplein 10, 5611 EM Eindhoven, with Sendcloud GmbH, Ltd., SAS and Srl for Germany and Austria, the UK, France and Italy. Dutch law applies.", "The MCP server answers at mcp.sendcloud.com and tokens come from account.sendcloud.com. The REST API answers at panel.sendcloud.sc, a second Sendcloud domain.", "www.sendcloud.com/.well-known/security.txt and /security.txt return 404. The bug bounty page sends reports to security@sendcloud.com.", "RDAP for sendcloud.com gives a registration date of 2008-07-29.", "Unit prices are converted from euros at the ECB reference rate of 1.1177 for 7 October 2026, read through api.frankfurter.dev." ], "score": 82 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sendcloud.json", "live": { "slug": "sendcloud", "probe": { "target": "https://mcp.sendcloud.com/mcp", "method": "get", "lastAt": "2026-11-04T20:47:14.01519538Z", "lastOk": true, "lastStatus": 405, "lastMs": 169, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 98, "p95ms24h": 244, "samples24h": 246, "samples30d": 6818, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 214, "ok": 214 } ] }, "vendorStatus": { "page": "https://status.sendcloud.com", "indicator": "maintenance", "summary": "Under Maintenance", "checkedAt": "2026-11-04T20:39:55.731418002Z" }, "securityTxt": { "url": "https://sendcloud.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:53:24.07170704Z" }, "llmsTxt": { "url": "https://sendcloud.dev/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:24:12.712796978Z" }, "domain": { "domain": "sendcloud.com", "registered": "2008-07-29", "source": "https://rdap.verisign.com/com/v1/domain/sendcloud.com", "checkedAt": "2026-11-01T14:18:44.125404298Z" }, "pages": [ { "url": "https://sendcloud.dev/api/v3/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-04T08:32:24.09424945Z", "changedAt": "2026-11-04T08:32:24.09424945Z", "fingerprint": "b5e545bf73b2" }, { "url": "https://www.sendcloud.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:45:09.238813294Z", "changedAt": "2026-10-31T06:32:09.372200744Z", "fingerprint": "00854eea0e35" }, { "url": "https://www.sendcloud.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:45:12.26949135Z", "changedAt": "2026-10-31T06:32:11.767514859Z", "fingerprint": "327bb2ea2328" }, { "url": "https://www.sendcloud.com/terms-conditions/", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:45:13.635373964Z", "changedAt": "2026-10-31T06:32:13.4432563Z", "fingerprint": "9f2270264b6c" } ], "updatedAt": "2026-11-04T20:47:14.01519538Z" } }, "answer": "Sendcloud scores 64.5 (B) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category.", "b": { "slug": "trackingmore", "name": "TrackingMore", "vendor": "CHANNELWILL CO., LIMITED", "vendorUrl": "https://www.trackingmore.com", "kind": "http-api", "category": "shipping", "summary": "TrackingMore is a multi-carrier parcel tracking service run by CHANNELWILL CO., LIMITED under the CWILL brand. Its REST API v4 detects couriers, creates and reads trackings, retracks expired ones and tracks air waybills, with webhooks for status changes.", "url": "https://www.anchorterminal.com/tools/trackingmore", "markdownUrl": "https://www.anchorterminal.com/tools/trackingmore.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/trackingmore.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/trackingmore.json", "dns": "trackingmore.grade.anchorterminal.com", "repo": "https://github.com/TrackingMore-API/trackingmore-sdk-nodejs", "license": "Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.trackingmore.com/v4", "packages": [ { "registry": "npm", "name": "trackingmore-sdk-nodejs" }, { "registry": "pypi", "name": "trackingmore-sdk-python" }, { "registry": "go", "name": "github.com/TrackingMore-API/trackingmore-sdk-go" } ], "auth": "api-key", "authNotes": "An API key sent in the Tracking-Api-Key header, generated in the web app under Developer, API key, and shown once. At most four keys per account, deleted from the same page. Every key has full account access and no scopes were found. Access is self-serve after a browser signup; the pricing page gives two keys on Basic, five on Pro and eight on Enterprise.", "pricing": "freemium", "pricingNotes": "Plans are priced in credits a month with a Free plan, Basic, Pro and a custom Enterprise plan, and a 14-day free trial. The plan prices on the pricing page render by script and were not read; the API page says tracking starts from $0.03 a tracked order and shows figures of $0.0318, $0.036 and $0.037. SMS notifications and translation cost extra credits. Enterprise adds custom rate limits and invoice payment (https://www.trackingmore.com/pricing and https://www.trackingmore.com/tracking-api, checked 2026-11-03).", "priceSummary": "$0.03 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the SDK READMEs, the support centre or the pricing page (checked 2026-11-03). Plans are paid by card in the web app, or by invoice on Enterprise.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.trackingmore.com/docs/trackingmore/", "capabilities": [ "shipping.tracking" ], "tags": [ "official", "hosted", "closed-source", "api-key", "webhooks", "free-tier", "free-trial", "freemium", "status-page", "python", "typescript", "go", "java", "php", "ruby", "dotnet" ], "lastRelease": "2024-12-25", "graded": true, "anchor": { "graded": true, "score": 41.8, "grade": "E", "agentReady": false, "rank": 1187, "ranked": true, "rankOf": 1349, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 19, "payments": 23, "reliability": 65, "schema": 31, "security": 31, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "An agent that reports where a parcel is across many carriers from a tracking number, with a cheap per-tracking price.", "strengths": [ "Nine v4 calls cover detect, create, batch create of 40, get, update, delete, retrack and air waybills, with webhooks for status changes", "Rate limits published per endpoint, 3 requests a second on create and 10 a second elsewhere, with a stated 120-second wait after a 429", "HTTP and meta codes with messages, including 4101 for a duplicate tracking, so a retried create is rejected rather than doubled", "Official SDKs in PHP, Python, Node, Java, Go, Ruby and .NET, MIT, plus a Postman collection", "Free plan and a 14-day trial, with courier detection free on v4" ], "weaknesses": [ "The API reference renders by script and no OpenAPI file, llms.txt or Markdown docs were found", "One API key with full access, at most four per account, no scopes and no read-only key", "No idempotency key, no Retry-After, and no SLA beyond a 99.99 per cent uptime line on the Enterprise plan", "The SDKs were last updated between February and December 2024, and no dated API changelog was found", "Plan prices render by script and were not read; the terms and privacy policy are CWILL group documents that name different entities per product" ], "agentNotes": [ "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", "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", "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", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.8 } ], "editorialScores": { "ergonomics": 54, "maintenance": 19, "payments": 23, "reliability": 65, "schema": 31, "security": 31, "transparency": 39 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install trackingmore-sdk-nodejs", "http": "curl -H \"Tracking-Api-Key: $TRACKINGMORE_API_KEY\" https://api.trackingmore.com/v4/couriers/all" }, "letme": { "capability": "https://letme.dev/shipping.tracking", "tool": "https://letme.dev/trackingmore" }, "area": "business", "unitPrices": [ { "item": "Tracked order", "unit": "tx", "usd": 0.03, "note": "the from price on the API page; plan prices render by script and were not read" } ], "provenance": { "legalEntity": "CHANNELWILL CO., LIMITED", "domain": "trackingmore.com", "domainRegistered": "2014-10-27", "endpointOnVendorDomain": true, "terms": "https://www.cwill.com/terms-of-service/", "privacy": "https://www.cwill.com/privacy-policy/", "statusPage": "https://status.trackingmore.com/", "changelog": "", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "trackingmore.com's legal links redirect to cwill.com. The CWILL privacy policy (effective 8 August 2026) names CHANNELWILL CO., LIMITED, Workspace B15, 2/F, Wing Cheung Industrial Building, 58-70 Kwai Cheong Road, Hong Kong, as data controller for TrackingMore, and CWILL INC of Dover, Delaware, for the CWILL Order Tracking and other products. The CWILL Terms of Service (effective 9 January 2026) cover the whole product family and say the contracting entity depends on the product.", "The CWILL terms refer to an Acceptable Use Policy and a DPA at cwill.com/legal/dpa/, and a sub-processor list at trust.cwill.com/subprocessors, none of which was read.", "www.trackingmore.com/robots.txt disallows nothing. support.trackingmore.com/robots.txt disallows nothing. www.cwill.com/robots.txt allows named AI crawlers and disallows search and admin paths for others, with a crawl delay of 5 seconds. status.trackingmore.com was read without a robots.txt check of its own.", "The API answers at api.trackingmore.com, a vendor subdomain.", "www.trackingmore.com/.well-known/security.txt returns 404, and no security page was found on trackingmore.com (the /security path returns 404).", "RDAP gives trackingmore.com a registration date of 27 October 2014." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/trackingmore.json", "live": { "slug": "trackingmore", "probe": { "target": "https://api.trackingmore.com/v4", "method": "get", "lastAt": "2026-11-04T20:47:20.612787952Z", "lastOk": true, "lastStatus": 404, "lastMs": 630, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 599, "p95ms24h": 1041, "samples24h": 55, "samples30d": 55, "days": [ { "date": "2026-11-04", "probes": 55, "ok": 55 } ] }, "vendorStatus": { "page": "https://status.trackingmore.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:39.655302878Z" }, "securityTxt": { "url": "https://trackingmore.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:27.177236947Z" }, "updatedAt": "2026-11-04T20:47:20.612787952Z" } }, "edges": [ { "by": 58, "category": "schema", "leads": "sendcloud", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 89, "b": 31 } }, { "by": 48, "category": "maintenance", "leads": "sendcloud", "name": "Maintenance \u0026 community", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 67, "b": 19 } }, { "by": 27, "category": "security", "leads": "sendcloud", "name": "Security \u0026 auth", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 58, "b": 31 } }, { "by": 17, "category": "ergonomics", "leads": "sendcloud", "name": "Agent ergonomics", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 71, "b": 54 } }, { "by": 15, "category": "transparency", "leads": "sendcloud", "name": "Transparency \u0026 trust", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 72, "b": 57 } }, { "by": 14, "category": "payments", "leads": "sendcloud", "name": "Payments \u0026 pricing", "reasons": { "a": "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).", "b": "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." }, "scores": { "a": 37, "b": 23 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Sendcloud B.V.", "b": "CHANNELWILL CO., LIMITED", "name": "Vendor" }, { "a": "https://mcp.sendcloud.com/mcp", "b": "https://api.trackingmore.com/v4", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "not published", "b": "$0.03 per transaction", "name": "Price for shipment tracking" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Sendcloud's terms and conditions", "b": "Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT", "name": "Licence" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-30", "b": "2024-12-25", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-08-08", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "yes", "b": "yes", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "6 stars", "name": "Popularity" }, { "a": "2.8/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Sendcloud scores 64.5 (B) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category.", "question": "Which is better for AI agents, Sendcloud or TrackingMore?" }, { "answer": "Sendcloud takes an API key or an OAuth sign-in. TrackingMore needs an API key.", "question": "Do Sendcloud and TrackingMore need an API key?" }, { "answer": "Yes. Sendcloud has a hosted endpoint at https://mcp.sendcloud.com/mcp and TrackingMore at https://api.trackingmore.com/v4.", "question": "Can an agent call Sendcloud and TrackingMore without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 73 against 65", "Schema \u0026 documentation, 89 against 31", "Agent ergonomics, 71 against 54", "Security \u0026 auth, 58 against 31", "Payments \u0026 pricing, 37 against 23", "Maintenance \u0026 community, 67 against 19", "Transparency \u0026 trust, 72 against 57" ], "also": null, "goodFor": "An agent shipping parcels for a European shop that wants many carriers behind one account, including its own carrier contracts on paid plans.", "slug": "sendcloud", "watchFor": "API key pairs get one scope, `api`, with full account access. Read and write scopes apply only to the MCP sign-in" }, { "aheadOn": null, "also": [ "No incidents deducted, where Sendcloud loses 3 points for them" ], "goodFor": "An agent that reports where a parcel is across many carriers from a tracking number, with a cheap per-tracking price.", "slug": "trackingmore", "watchFor": "The API reference renders by script and no OpenAPI file, llms.txt or Markdown docs were found" } ], "history": { "sendcloud": [ { "causes": [ "product", "correction" ], "date": "2026-11-02", "delta": 2.5, "from": 62, "fromGrade": "B", "to": 64.5, "toGrade": "B" } ], "trackingmore": null }, "job": { "capability": "shipping.tracking", "name": "Shipment tracking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/easypost-vs-sendcloud.json", "title": "EasyPost vs Sendcloud", "url": "https://www.anchorterminal.com/compare/easypost-vs-sendcloud" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-sendcloud.json", "title": "Easyship vs Sendcloud", "url": "https://www.anchorterminal.com/compare/easyship-vs-sendcloud" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-sendcloud.json", "title": "Karrio vs Sendcloud", "url": "https://www.anchorterminal.com/compare/karrio-vs-sendcloud" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-shipbob.json", "title": "Sendcloud vs ShipBob", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-shipbob" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-shippo.json", "title": "Sendcloud vs Shippo", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-shippo" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-shippypro.json", "title": "Sendcloud vs ShippyPro", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-shipstation.json", "title": "Sendcloud vs ShipStation API", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-shipstation" }, { "json": "https://www.anchorterminal.com/compare/easypost-vs-trackingmore.json", "title": "EasyPost vs TrackingMore", "url": "https://www.anchorterminal.com/compare/easypost-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-trackingmore.json", "title": "Easyship vs TrackingMore", "url": "https://www.anchorterminal.com/compare/easyship-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-trackingmore.json", "title": "Karrio vs TrackingMore", "url": "https://www.anchorterminal.com/compare/karrio-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-ship24.json", "title": "Sendcloud vs Ship24", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-ship24" }, { "json": "https://www.anchorterminal.com/compare/ship24-vs-trackingmore.json", "title": "Ship24 vs TrackingMore", "url": "https://www.anchorterminal.com/compare/ship24-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shipbob-vs-trackingmore.json", "title": "ShipBob vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shipbob-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore.json", "title": "Shippo vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.json", "title": "ShippyPro vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shipstation-vs-trackingmore.json", "title": "ShipStation API vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shipstation-vs-trackingmore" } ], "panel": null, "scores": [ { "by": 8, "edge": "sendcloud", "key": "reliability", "name": "Reliability", "sendcloud": 73, "trackingmore": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 58, "edge": "sendcloud", "key": "schema", "name": "Schema \u0026 documentation", "sendcloud": 89, "trackingmore": 31, "weight": 13 }, { "by": 17, "edge": "sendcloud", "key": "ergonomics", "name": "Agent ergonomics", "sendcloud": 71, "trackingmore": 54, "weight": 13 }, { "by": 27, "edge": "sendcloud", "key": "security", "name": "Security \u0026 auth", "sendcloud": 58, "trackingmore": 31, "weight": 14 }, { "by": 14, "edge": "sendcloud", "key": "payments", "name": "Payments \u0026 pricing", "sendcloud": 37, "trackingmore": 23, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 48, "edge": "sendcloud", "key": "maintenance", "name": "Maintenance \u0026 community", "sendcloud": 67, "trackingmore": 19, "weight": 7 }, { "by": 15, "edge": "sendcloud", "key": "transparency", "name": "Transparency \u0026 trust", "sendcloud": 72, "trackingmore": 57, "weight": 7 } ], "summary": "Sendcloud scores 64.5 (B) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category. Both do shipment tracking.", "tasks": null, "tutorials": [], "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore", "json": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.min.md" }, "markdown": "Sendcloud scores 64.5 (B) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category. Both do shipment tracking.\n\n- 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\n- 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\n- Best shipping and fulfilment APIs for AI agents: https://www.anchorterminal.com/best/shipping/index.md\n- All 45 shipping comparisons: https://www.anchorterminal.com/compare/shipping/index.md\n\n## Which one, for what\n\n### Sendcloud (B)\n\nGood for: An agent shipping parcels for a European shop that wants many carriers behind one account, including its own carrier contracts on paid plans.\n\nAhead on:\n- Reliability, 73 against 65\n- Schema \u0026 documentation, 89 against 31\n- Agent ergonomics, 71 against 54\n- Security \u0026 auth, 58 against 31\n- Payments \u0026 pricing, 37 against 23\n- Maintenance \u0026 community, 67 against 19\n- Transparency \u0026 trust, 72 against 57\n\nWatch for: API key pairs get one scope, `api`, with full account access. Read and write scopes apply only to the MCP sign-in\n\n### TrackingMore (E)\n\nGood for: An agent that reports where a parcel is across many carriers from a tracking number, with a cheap per-tracking price.\n\nAlso in its favour:\n- No incidents deducted, where Sendcloud loses 3 points for them\n\nWatch for: The API reference renders by script and no OpenAPI file, llms.txt or Markdown docs were found\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Sendcloud +58\n\n- 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).\n- 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.\n\n### Maintenance \u0026 community: Sendcloud +48\n\n- 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).\n- 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.\n\n### Security \u0026 auth: Sendcloud +27\n\n- 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).\n- 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.\n\n### Agent ergonomics: Sendcloud +17\n\n- 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).\n- 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.\n\n### Transparency \u0026 trust: Sendcloud +15\n\n- 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).\n- 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.\n\n### Payments \u0026 pricing: Sendcloud +14\n\n- 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).\n- 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.\n\n## Score by category\n\n| Category | Weight | Sendcloud | TrackingMore | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 73 | 65 | Sendcloud +8 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 89 | 31 | Sendcloud +58 |\n| Agent ergonomics | 13% (16.2 this run) | 71 | 54 | Sendcloud +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 31 | Sendcloud +27 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 37 | 23 | Sendcloud +14 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 67 | 19 | Sendcloud +48 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 57 | Sendcloud +15 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **64.5 · B** | **41.8 · E** | |\n\n## Facts side by side\n\n| Fact | Sendcloud | TrackingMore |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Sendcloud B.V. | CHANNELWILL CO., LIMITED |\n| Hosted endpoint | `https://mcp.sendcloud.com/mcp` | `https://api.trackingmore.com/v4` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| Price for shipment tracking | not published | $0.03 per transaction |\n| x402 | no | no |\n| 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 |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-30 | 2024-12-25 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | no date given | 2026-08-08 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | yes | yes |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | none | 6 stars |\n| Agent reviews | 2.8/5 (4) | none |\n\n## How the scores have moved\n\n### Sendcloud\n\n- +2.5 on 2 November 2026: product, correction\n\n### TrackingMore\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Sendcloud\n\n1. Use API v3 at https://panel.sendcloud.sc/api/v3. The v2 create-parcel endpoint is closed to accounts created from April 2026\n2. Test with `shipping_option_code` `sendcloud:letter` (returns use `sendcloud:letterreturn`). Any other label is billed unless cancelled within the carrier's deadline\n3. Set `external_reference_id` on every shipment so a retry returns the existing shipment (409) instead of a second label\n4. Read the `errors` array on synchronous announce responses. A carrier failure can arrive inside a success status\n5. 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\n6. At MCP sign-in, grant only the permission groups the task needs. A tool outside the granted scopes fails with a permission error\n\n### TrackingMore\n\n1. 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\n2. 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\n3. 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\n4. 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\n5. 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\n\n## Questions\n\n### Which is better for AI agents, Sendcloud or TrackingMore?\n\nSendcloud scores 64.5 (B) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category.\n\n### Do Sendcloud and TrackingMore need an API key?\n\nSendcloud takes an API key or an OAuth sign-in. TrackingMore needs an API key.\n\n### Can an agent call Sendcloud and TrackingMore without installing anything?\n\nYes. Sendcloud has a hosted endpoint at https://mcp.sendcloud.com/mcp and TrackingMore at https://api.trackingmore.com/v4.\n\n\n## For agents\n\n- 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\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"sendcloud\", \"b\": \"trackingmore\"}`. From a terminal: `anchor compare sendcloud trackingmore`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/sendcloud.json and https://www.anchorterminal.com/api/v1/tools/trackingmore.json\n\n## Other comparisons with Sendcloud or TrackingMore\n\n- [EasyPost vs Sendcloud](https://www.anchorterminal.com/compare/easypost-vs-sendcloud.md)\n- [Easyship vs Sendcloud](https://www.anchorterminal.com/compare/easyship-vs-sendcloud.md)\n- [Karrio vs Sendcloud](https://www.anchorterminal.com/compare/karrio-vs-sendcloud.md)\n- [Sendcloud vs ShipBob](https://www.anchorterminal.com/compare/sendcloud-vs-shipbob.md)\n- [Sendcloud vs Shippo](https://www.anchorterminal.com/compare/sendcloud-vs-shippo.md)\n- [Sendcloud vs ShippyPro](https://www.anchorterminal.com/compare/sendcloud-vs-shippypro.md)\n- [Sendcloud vs ShipStation API](https://www.anchorterminal.com/compare/sendcloud-vs-shipstation.md)\n- [EasyPost vs TrackingMore](https://www.anchorterminal.com/compare/easypost-vs-trackingmore.md)\n- [Easyship vs TrackingMore](https://www.anchorterminal.com/compare/easyship-vs-trackingmore.md)\n- [Karrio vs TrackingMore](https://www.anchorterminal.com/compare/karrio-vs-trackingmore.md)\n- [Sendcloud vs Ship24](https://www.anchorterminal.com/compare/sendcloud-vs-ship24.md)\n- [Ship24 vs TrackingMore](https://www.anchorterminal.com/compare/ship24-vs-trackingmore.md)\n- [ShipBob vs TrackingMore](https://www.anchorterminal.com/compare/shipbob-vs-trackingmore.md)\n- [Shippo vs TrackingMore](https://www.anchorterminal.com/compare/shippo-vs-trackingmore.md)\n- [ShippyPro vs TrackingMore](https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.md)\n- [ShipStation API vs TrackingMore](https://www.anchorterminal.com/compare/shipstation-vs-trackingmore.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Sendcloud vs TrackingMore", "url": "" } ], "description": "Sendcloud scores 64.5 (B) to TrackingMore's 41.8 (E) for shipment tracking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Sendcloud B 64.5", "TrackingMore E 41.8", "scores" ], "h1": "Sendcloud vs TrackingMore", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/sendcloud-vs-trackingmore", "published": "2026-10-01", "section": "tools", "title": "Sendcloud vs TrackingMore for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore" }, "tokens": { "markdown": 4450, "slim": 2680 }, "version": 1 }