{ "data": { "a": { "slug": "shippypro", "name": "ShippyPro", "vendor": "Italian Valley S.r.l.", "vendorUrl": "https://www.shippypro.com", "kind": "http-api", "category": "shipping", "summary": "Multi-carrier shipping platform from ShippyPro (Italian Valley S.r.l., Florence). Its REST API quotes rates on a customer's own carrier contracts, creates labels and returns, validates addresses, books pickups and tracks parcels. API access is sold with the Enterprise plan.", "url": "https://www.anchorterminal.com/tools/shippypro", "markdownUrl": "https://www.anchorterminal.com/tools/shippypro.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/shippypro.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/shippypro.json", "dns": "shippypro.grade.anchorterminal.com", "license": "Proprietary service under ShippyPro's Terms \u0026 Conditions. Both OpenAPI files state the licence as Proprietary", "transports": [ "http" ], "remoteUrl": "https://api.shippypro.com", "packages": [], "auth": "api-key", "authNotes": "Sales approval, then a key. The help centre says APIs can only be activated with an Enterprise plan and tells users to contact sales. Keys are created in the account panel under API, more than one per account, as Full Access, Maps (pickup-point map only) or PII Excluded (personal data hidden). Calls send `Authorization: Bearer \u003cAPI key\u003e`, per both OpenAPI files. The help centre article still describes the key as a Basic auth username with a blank password. No expiry or rotation was found in the reviewed documentation.", "pricing": "paid", "pricingNotes": "Enterprise plan, custom price through sales, billed annually. It is the only plan the pricing page lists with full access to the Multicarrier APIs. The self-serve plans (49 to 259 EUR a month at regular monthly prices, up to 4,000 shipments) are marked UI only. A 14-day, 30-order trial needs no card per the terms, and whether a trial account can call the API was not established. No sandbox. The Generic carrier creates test labels and rates. A higher rate limit costs extra (https://www.shippypro.com/en/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI files, the API page or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://api.shippypro.com/docs", "openapi": "https://api.shippypro.com/docs/v1.json", "capabilities": [ "shipping.rates", "shipping.labels", "shipping.tracking", "shipping.address-validation", "shipping.returns" ], "tags": [ "hosted", "paid", "sales-led", "enterprise", "api-key", "openapi", "webhooks", "soap", "status-page", "sla", "europe" ], "graded": true, "anchor": { "graded": true, "score": 48.9, "grade": "D", "agentReady": false, "rank": 1015, "ranked": true, "rankOf": 1349, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 25, "payments": 5, "reliability": 70, "schema": 64, "security": 51, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "OpenAPI 3.1 files for v1 (55 operations) and v2 (17 operations) are public at api.shippypro.com/docs, with 812 examples in the v1 file", "Published SLA of 99.5 per cent monthly availability with service credits of 0.5 to 5 per cent", "API keys come in three types, Full Access, Maps and PII Excluded, and an account can hold several", "The account panel keeps API request and response logs, an API error history and webhook logs", "The Generic carrier creates test labels and rates without a real carrier or tracking number", "The privacy policy lists sub-processors per product area and says customer data is never sold" ], "weaknesses": [ "The help centre says APIs can only be activated with an Enterprise plan, which has no public price and starts with sales", "No API changelog, release notes or deprecation policy was found, and the terms allow changes without notice", "`POST /v1/Ship` takes no idempotency key. Only the 17 v2 operations accept `Idempotency-Key`", "Carrier label incidents marked critical appear on the status page on most days from August to October 2026", "No official SDK, MCP server or llms.txt was found on the pages read", "v1 answers some failures with HTTP 200 and `Status` 2, and `LabelURL` can be a string or an array" ], "agentNotes": [ "Send `Authorization: Bearer \u003cAPI key\u003e` and POST a JSON body with `Method` and `Params` to `https://api.shippypro.com/v1/\u003cMethod\u003e`. Parameter names are case-sensitive", "Check `Status` and `ErrorMessage` in every `Ship` response. HTTP 200 with `Status` 2 means no label was created", "Before retrying a failed `Ship` call, look the order up by `TransactionID`. v1 has no idempotency key, and each label counts against the plan", "Test with the Generic carrier. `Ship` and `Edit` calls on a real carrier create real labels", "Stay under 20 calls per 10 seconds, and use webhooks for tracking. The docs advise against `GetTracking` in bulk" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.9 } ], "editorialScores": { "ergonomics": 46, "maintenance": 25, "payments": 5, "reliability": 70, "schema": 64, "security": 51, "transparency": 48 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "lastMoved": "2026-10-28", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST https://api.shippypro.com/v1/Ping \\\n -H \"Authorization: Bearer \u003cAPI_KEY\u003e\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"Method\": \"Ping\", \"Params\": {}}'" }, "letme": { "capability": "https://letme.dev/shipping.rates", "tool": "https://letme.dev/shippypro" }, "area": "business", "provenance": { "legalEntity": "Italian Valley S.r.l.", "domain": "shippypro.com", "domainRegistered": "2016-10-24", "endpointOnVendorDomain": true, "terms": "https://www.shippypro.com/en/legal/terms", "privacy": "https://www.shippypro.com/en/legal/privacy", "statusPage": "https://status.shippypro.com", "changelog": "", "securityTxt": "unknown", "checked": "2026-10-09", "notes": [ "The Terms \u0026 Conditions name Italian Valley Srl, registered number 06587610483, Piazza Francesca Morvillo 15, 50144 Firenze, Italy, as owner of the ShippyPro software. They cover every ShippyPro product and service, the API included, and carry no date or version.", "The privacy policy names ShippyPro by Italian Valley S.r.l. as data controller and covers shipment sender and recipient data handled by the product, not only the website.", "RDAP for shippypro.com gives a registration date of 2016-10-24.", "The API answers at api.shippypro.com and the reference is served from the same host.", "www.shippypro.com/robots.txt disallows every path outside the language folders, the blog and a short list, so /.well-known/security.txt and /llms.txt were not requested.", "No API changelog or release notes page was found on the API page, the reference or the help centre's API section.", "The SLA at https://www.shippypro.com/en/legal/sla is stated to be part of the agreement with the customer." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/shippypro.json", "live": { "slug": "shippypro", "probe": { "target": "https://api.shippypro.com", "method": "get", "lastAt": "2026-11-04T20:47:14.47229714Z", "lastOk": true, "lastStatus": 404, "lastMs": 64, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 62, "p95ms24h": 163, "samples24h": 246, "samples30d": 6644, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "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.shippypro.com", "indicator": "major", "summary": "Partial System Outage", "checkedAt": "2026-11-04T20:39:56.212908316Z" }, "securityTxt": { "url": "https://shippypro.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-04T15:52:35.620054394Z" }, "domain": { "domain": "shippypro.com", "registered": "2016-10-24", "source": "https://rdap.verisign.com/com/v1/domain/shippypro.com", "checkedAt": "2026-11-01T14:11:55.446503256Z" }, "pages": [ { "url": "https://www.shippypro.com/en/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:45:18.671052265Z", "changedAt": "2026-11-04T08:45:18.671052265Z", "fingerprint": "f0fd3c4f9b1a" }, { "url": "https://www.shippypro.com/en/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:45:13.812839268Z", "changedAt": "2026-11-04T08:45:13.812839268Z", "fingerprint": "bc118e7e931c" }, { "url": "https://www.shippypro.com/en/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:45:16.707406212Z", "changedAt": "2026-11-04T08:45:16.707406212Z", "fingerprint": "4d9ac705d49e" } ], "updatedAt": "2026-11-04T20:47:14.47229714Z" } }, "answer": "ShippyPro scores 48.9 (D) on agent readiness against TrackingMore's 41.8 (E), and leads in 5 of 7 scored categories. TrackingMore leads on agent ergonomics and payments \u0026 pricing.", "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": 33, "category": "schema", "leads": "shippypro", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 files for v1 (55 operations, 119 schemas) and v2 (17 operations), loaded by the reference at api.shippypro.com/docs (25). api.shippypro.com/llms.txt returns 404, the main site's robots.txt disallows /llms.txt so it was not requested, and no Markdown docs were found (0). v1 descriptions state purpose, how to test and known traps, such as `GetTracking` not being meant for bulk use (14 of 20). Required fields are marked, but the v1 file has 14 enums in all, `LabelURL` is a string or an array, `delivery_days` a number or a string, and carrier options are free name and value pairs (9 of 15). 812 examples in the v1 file. v1 error responses are one line per status code with no body schema, and v2 documents RFC 9457 problem types (10 of 15). Versions are in the path, v1 and v2. No changelog was found (6 of 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": 64, "b": 31 } }, { "by": 20, "category": "security", "leads": "shippypro", "name": "Security \u0026 auth", "reasons": { "a": "API keys are created in the panel, several per account, in three types (Full Access, Maps, PII Excluded), and v2 answers 401 for a revoked key. No expiry or rotation was found. The help centre still describes Basic auth with the key as username (22 of 30). The Maps and PII Excluded types narrow a key, but there is no read-only key and no confirmation step for label creation or voiding. The Generic carrier allows tests without a real shipment (8 of 20). Tracking messages and marketplace order text come from third parties, and no guidance on untrusted content was found. Requests are screened for script-like strings (3 of 15). The panel has API logs with requests and responses, an API error history and webhook logs (10 of 15). The site footer states ISO 27001 and SOC 2 Type II, with no certificate, report or trust page found. security.txt was not requested because robots.txt disallows the path. No bug bounty or disclosure policy was found (8 of 20).", "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": 51, "b": 31 } }, { "by": 18, "category": "payments", "leads": "trackingmore", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). The self-serve plans have public monthly prices, but the pricing page marks them UI only and lists API access under Enterprise at a custom price through sales (0). The terms describe a 14-day, 30-order trial with no card. The help centre says APIs are activated by sales on an Enterprise plan, so we could not establish that a trial account can call the API, and give part credit (5 of 20). A person signs up in a browser and sales activates the API (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": 5, "b": 23 } }, { "by": 8, "category": "ergonomics", "leads": "trackingmore", "name": "Agent ergonomics", "reasons": { "a": "Scored on the REST API. v1 report calls take date ranges and switches such as `IncludeItems`, with no field selection, and v2 lists take `pageSize` up to 100 (12 of 25). v1 lists have date filters and no pagination. v2 has cursor pagination and filters by carrier and country (10 of 20). v1 mixes HTTP status codes with 200 responses carrying `Status` 2, though `ErrorType` and `ErrorSuggestion` name a cause and a fix. v2 errors are application/problem+json with field pointers (12 of 20). No idempotency key on `Ship`, `Edit` or `VoidShipments`. v2 accepts `Idempotency-Key` on POST and DELETE and answers 409 on a mismatched replay (7 of 20). `Ship` has eight required parameters and needs a `CarrierID` from the panel or `GetCarriers`. No official SDK was found on the pages read, though the API page's FAQ mentions SDKs (5 of 15).", "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": 46, "b": 54 } }, { "by": 6, "category": "maintenance", "leads": "shippypro", "name": "Maintenance \u0026 community", "reasons": { "a": "No API changelog or dated release notes were found. Both OpenAPI files were last modified on 8 October 2026 per their HTTP headers, and the v2 file reads as recent work, so we give half for recency on that metadata alone (15 of 30). No dated entries in the last 90 days (0). Closed service with no changelog. Support runs through tickets, email and chat, the SLA sets response times, and the status page is updated daily (7 of 15). No official SDK or MCP registry entry was found (0). The contract is current OpenAPI 3.1 with examples (3 of 10).", "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": 25, "b": 19 } }, { "by": 5, "category": "reliability", "leads": "shippypro", "name": "Reliability", "reasons": { "a": "Read with the hosted lines and scored on the v1 REST API, where rates, labels and tracking live. Statuspage at status.shippypro.com with a component for ShippyPro API \u0026 Webhooks and one per carrier (20). From 11 July to 8 October 2026 no entry names the API. A platform login problem ran for 3 hours 6 minutes on 18 September, marked critical, SMS one-time codes went unsent from 29 August to 3 September and from 19 September to 5 October, and one carrier's label creation was marked critical on most days, some for several days (Asendia from 20 to 31 August). We read that as one major, as for other listings in this category (10 of 30). 20 requests every 10 seconds (15). v1 documents the 429 and nothing more, and `Ship` takes no idempotency key. The help centre suggests spreading calls over several IP addresses. v2 documents `Retry-After`, rate-limit headers and `Idempotency-Key`, but covers no shipping call (5 of 15). The SLA commits to 99.5 per cent a month with service credits (10). GA (10).", "b": "Read with the hosted lines and scored on the REST API v4 at api.trackingmore.com. status.trackingmore.com is a hosted status page with uptime and a status update history (20). Its figures and history render by script, so the 90 days could not be read; the static text says there were no updates in the last 7 days (5). Rate limits are published per endpoint, 3 requests a second on trackings/create and 10 a second elsewhere, per account (15). The support centre says a 429 means the application should stop and wait 120 seconds, and a repeated create answers meta code 4101 rather than creating a duplicate. No Retry-After and no idempotency key (10 of 15). No SLA document was found. The Enterprise plan lists 99.99 per cent API uptime as a feature and the API page claims 99.9 per cent uptime, which is marketing rather than a published SLA (5 of 10). v4 is the current version and not marked beta (10). 20 + 5 + 15 + 10 + 5 + 10 = 65." }, "scores": { "a": 70, "b": 65 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Italian Valley S.r.l.", "b": "CHANNELWILL CO., LIMITED", "name": "Vendor" }, { "a": "https://api.shippypro.com", "b": "https://api.trackingmore.com/v4", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Paid", "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 ShippyPro's Terms \u0026 Conditions. Both OpenAPI files state the licence as Proprietary", "b": "Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "none", "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": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "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" } ], "faq": [ { "answer": "ShippyPro scores 48.9 (D) on agent readiness against TrackingMore's 41.8 (E), and leads in 5 of 7 scored categories. TrackingMore leads on agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, ShippyPro or TrackingMore?" }, { "answer": "Both need an API key.", "question": "Do ShippyPro and TrackingMore need an API key?" }, { "answer": "Yes. ShippyPro has a hosted endpoint at https://api.shippypro.com and TrackingMore at https://api.trackingmore.com/v4.", "question": "Can an agent call ShippyPro and TrackingMore without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 65", "Schema \u0026 documentation, 64 against 31", "Security \u0026 auth, 51 against 31", "Maintenance \u0026 community, 25 against 19" ], "also": null, "goodFor": "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.", "slug": "shippypro", "watchFor": "The help centre says APIs can only be activated with an Enterprise plan, which has no public price and starts with sales" }, { "aheadOn": [ "Agent ergonomics, 54 against 46", "Payments \u0026 pricing, 23 against 5" ], "also": null, "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": { "shippypro": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 49, "fromGrade": "D", "to": 48.9, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.3, "from": 48.7, "fromGrade": "D", "to": 49, "toGrade": "D" } ], "trackingmore": null }, "job": { "capability": "shipping.tracking", "name": "Shipment tracking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/easypost-vs-shippypro.json", "title": "EasyPost vs ShippyPro", "url": "https://www.anchorterminal.com/compare/easypost-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-shippypro.json", "title": "Easyship vs ShippyPro", "url": "https://www.anchorterminal.com/compare/easyship-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-shippypro.json", "title": "Karrio vs ShippyPro", "url": "https://www.anchorterminal.com/compare/karrio-vs-shippypro" }, { "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/shipbob-vs-shippypro.json", "title": "ShipBob vs ShippyPro", "url": "https://www.anchorterminal.com/compare/shipbob-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/shippo-vs-shippypro.json", "title": "Shippo vs ShippyPro", "url": "https://www.anchorterminal.com/compare/shippo-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/shippypro-vs-shipstation.json", "title": "ShippyPro vs ShipStation API", "url": "https://www.anchorterminal.com/compare/shippypro-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-trackingmore.json", "title": "Sendcloud vs TrackingMore", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/ship24-vs-shippypro.json", "title": "Ship24 vs ShippyPro", "url": "https://www.anchorterminal.com/compare/ship24-vs-shippypro" }, { "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/shipstation-vs-trackingmore.json", "title": "ShipStation API vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shipstation-vs-trackingmore" } ], "panel": null, "scores": [ { "by": 5, "edge": "shippypro", "key": "reliability", "name": "Reliability", "shippypro": 70, "trackingmore": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 33, "edge": "shippypro", "key": "schema", "name": "Schema \u0026 documentation", "shippypro": 64, "trackingmore": 31, "weight": 13 }, { "by": 8, "edge": "trackingmore", "key": "ergonomics", "name": "Agent ergonomics", "shippypro": 46, "trackingmore": 54, "weight": 13 }, { "by": 20, "edge": "shippypro", "key": "security", "name": "Security \u0026 auth", "shippypro": 51, "trackingmore": 31, "weight": 14 }, { "by": 18, "edge": "trackingmore", "key": "payments", "name": "Payments \u0026 pricing", "shippypro": 5, "trackingmore": 23, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "shippypro", "key": "maintenance", "name": "Maintenance \u0026 community", "shippypro": 25, "trackingmore": 19, "weight": 7 }, { "by": 4, "edge": "shippypro", "key": "transparency", "name": "Transparency \u0026 trust", "shippypro": 61, "trackingmore": 57, "weight": 7 } ], "summary": "ShippyPro scores 48.9 (D) on agent readiness against TrackingMore's 41.8 (E), and leads in 5 of 7 scored categories. TrackingMore leads on agent ergonomics and payments \u0026 pricing. Both do shipment tracking.", "tasks": null, "tutorials": [], "verdicts": { "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.", "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/shippypro-vs-trackingmore", "json": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.min.md" }, "markdown": "ShippyPro scores 48.9 (D) on agent readiness against TrackingMore's 41.8 (E), and leads in 5 of 7 scored categories. TrackingMore leads on agent ergonomics and payments \u0026 pricing. Both do shipment tracking.\n\n- ShippyPro: grade D, 48.9/100, rank #1015 of 1349. Markdown https://www.anchorterminal.com/tools/shippypro.md · JSON https://www.anchorterminal.com/api/v1/tools/shippypro.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### ShippyPro (D)\n\nGood 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.\n\nAhead on:\n- Reliability, 70 against 65\n- Schema \u0026 documentation, 64 against 31\n- Security \u0026 auth, 51 against 31\n- Maintenance \u0026 community, 25 against 19\n\nWatch for: The help centre says APIs can only be activated with an Enterprise plan, which has no public price and starts with sales\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\nAhead on:\n- Agent ergonomics, 54 against 46\n- Payments \u0026 pricing, 23 against 5\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: ShippyPro +33\n\n- ShippyPro (64): OpenAPI 3.1 files for v1 (55 operations, 119 schemas) and v2 (17 operations), loaded by the reference at api.shippypro.com/docs (25). api.shippypro.com/llms.txt returns 404, the main site's robots.txt disallows /llms.txt so it was not requested, and no Markdown docs were found (0). v1 descriptions state purpose, how to test and known traps, such as `GetTracking` not being meant for bulk use (14 of 20). Required fields are marked, but the v1 file has 14 enums in all, `LabelURL` is a string or an array, `delivery_days` a number or a string, and carrier options are free name and value pairs (9 of 15). 812 examples in the v1 file. v1 error responses are one line per status code with no body schema, and v2 documents RFC 9457 problem types (10 of 15). Versions are in the path, v1 and v2. No changelog was found (6 of 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### Security \u0026 auth: ShippyPro +20\n\n- ShippyPro (51): API keys are created in the panel, several per account, in three types (Full Access, Maps, PII Excluded), and v2 answers 401 for a revoked key. No expiry or rotation was found. The help centre still describes Basic auth with the key as username (22 of 30). The Maps and PII Excluded types narrow a key, but there is no read-only key and no confirmation step for label creation or voiding. The Generic carrier allows tests without a real shipment (8 of 20). Tracking messages and marketplace order text come from third parties, and no guidance on untrusted content was found. Requests are screened for script-like strings (3 of 15). The panel has API logs with requests and responses, an API error history and webhook logs (10 of 15). The site footer states ISO 27001 and SOC 2 Type II, with no certificate, report or trust page found. security.txt was not requested because robots.txt disallows the path. No bug bounty or disclosure policy was found (8 of 20).\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### Payments \u0026 pricing: TrackingMore +18\n\n- ShippyPro (5): No x402, MPP or L402 (0). The self-serve plans have public monthly prices, but the pricing page marks them UI only and lists API access under Enterprise at a custom price through sales (0). The terms describe a 14-day, 30-order trial with no card. The help centre says APIs are activated by sales on an Enterprise plan, so we could not establish that a trial account can call the API, and give part credit (5 of 20). A person signs up in a browser and sales activates the API (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### Agent ergonomics: TrackingMore +8\n\n- ShippyPro (46): Scored on the REST API. v1 report calls take date ranges and switches such as `IncludeItems`, with no field selection, and v2 lists take `pageSize` up to 100 (12 of 25). v1 lists have date filters and no pagination. v2 has cursor pagination and filters by carrier and country (10 of 20). v1 mixes HTTP status codes with 200 responses carrying `Status` 2, though `ErrorType` and `ErrorSuggestion` name a cause and a fix. v2 errors are application/problem+json with field pointers (12 of 20). No idempotency key on `Ship`, `Edit` or `VoidShipments`. v2 accepts `Idempotency-Key` on POST and DELETE and answers 409 on a mismatched replay (7 of 20). `Ship` has eight required parameters and needs a `CarrierID` from the panel or `GetCarriers`. No official SDK was found on the pages read, though the API page's FAQ mentions SDKs (5 of 15).\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### Maintenance \u0026 community: ShippyPro +6\n\n- ShippyPro (25): No API changelog or dated release notes were found. Both OpenAPI files were last modified on 8 October 2026 per their HTTP headers, and the v2 file reads as recent work, so we give half for recency on that metadata alone (15 of 30). No dated entries in the last 90 days (0). Closed service with no changelog. Support runs through tickets, email and chat, the SLA sets response times, and the status page is updated daily (7 of 15). No official SDK or MCP registry entry was found (0). The contract is current OpenAPI 3.1 with examples (3 of 10).\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### Reliability: ShippyPro +5\n\n- ShippyPro (70): Read with the hosted lines and scored on the v1 REST API, where rates, labels and tracking live. Statuspage at status.shippypro.com with a component for ShippyPro API \u0026 Webhooks and one per carrier (20). From 11 July to 8 October 2026 no entry names the API. A platform login problem ran for 3 hours 6 minutes on 18 September, marked critical, SMS one-time codes went unsent from 29 August to 3 September and from 19 September to 5 October, and one carrier's label creation was marked critical on most days, some for several days (Asendia from 20 to 31 August). We read that as one major, as for other listings in this category (10 of 30). 20 requests every 10 seconds (15). v1 documents the 429 and nothing more, and `Ship` takes no idempotency key. The help centre suggests spreading calls over several IP addresses. v2 documents `Retry-After`, rate-limit headers and `Idempotency-Key`, but covers no shipping call (5 of 15). The SLA commits to 99.5 per cent a month with service credits (10). GA (10).\n- TrackingMore (65): Read with the hosted lines and scored on the REST API v4 at api.trackingmore.com. status.trackingmore.com is a hosted status page with uptime and a status update history (20). Its figures and history render by script, so the 90 days could not be read; the static text says there were no updates in the last 7 days (5). Rate limits are published per endpoint, 3 requests a second on trackings/create and 10 a second elsewhere, per account (15). The support centre says a 429 means the application should stop and wait 120 seconds, and a repeated create answers meta code 4101 rather than creating a duplicate. No Retry-After and no idempotency key (10 of 15). No SLA document was found. The Enterprise plan lists 99.99 per cent API uptime as a feature and the API page claims 99.9 per cent uptime, which is marketing rather than a published SLA (5 of 10). v4 is the current version and not marked beta (10). 20 + 5 + 15 + 10 + 5 + 10 = 65.\n\n## Score by category\n\n| Category | Weight | ShippyPro | TrackingMore | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 65 | ShippyPro +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 31 | ShippyPro +33 |\n| Agent ergonomics | 13% (16.2 this run) | 46 | 54 | TrackingMore +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 51 | 31 | ShippyPro +20 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 5 | 23 | TrackingMore +18 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 25 | 19 | ShippyPro +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 57 | ShippyPro +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **48.9 · D** | **41.8 · E** | |\n\n## Facts side by side\n\n| Fact | ShippyPro | TrackingMore |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Italian Valley S.r.l. | CHANNELWILL CO., LIMITED |\n| Hosted endpoint | `https://api.shippypro.com` | `https://api.trackingmore.com/v4` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Paid | Freemium |\n| Price for shipment tracking | not published | $0.03 per transaction |\n| x402 | no | no |\n| Licence | Proprietary service under ShippyPro's Terms \u0026 Conditions. Both OpenAPI files state the licence as Proprietary | Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | none | 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 | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | 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\n## How the scores have moved\n\n### ShippyPro\n\n- -0.1 on 28 October 2026: correction\n- +0.3 on 27 October 2026: checklist\n\n### TrackingMore\n\nNo score change since it was listed.\n\n## Verdicts\n\n**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.\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### ShippyPro\n\n1. Send `Authorization: Bearer \u003cAPI key\u003e` and POST a JSON body with `Method` and `Params` to `https://api.shippypro.com/v1/\u003cMethod\u003e`. Parameter names are case-sensitive\n2. Check `Status` and `ErrorMessage` in every `Ship` response. HTTP 200 with `Status` 2 means no label was created\n3. Before retrying a failed `Ship` call, look the order up by `TransactionID`. v1 has no idempotency key, and each label counts against the plan\n4. Test with the Generic carrier. `Ship` and `Edit` calls on a real carrier create real labels\n5. Stay under 20 calls per 10 seconds, and use webhooks for tracking. The docs advise against `GetTracking` in bulk\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, ShippyPro or TrackingMore?\n\nShippyPro scores 48.9 (D) on agent readiness against TrackingMore's 41.8 (E), and leads in 5 of 7 scored categories. TrackingMore leads on agent ergonomics and payments \u0026 pricing.\n\n### Do ShippyPro and TrackingMore need an API key?\n\nBoth need an API key.\n\n### Can an agent call ShippyPro and TrackingMore without installing anything?\n\nYes. ShippyPro has a hosted endpoint at https://api.shippypro.com and TrackingMore at https://api.trackingmore.com/v4.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.json, and with the fewest tokens: https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"shippypro\", \"b\": \"trackingmore\"}`. From a terminal: `anchor compare shippypro trackingmore`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/shippypro.json and https://www.anchorterminal.com/api/v1/tools/trackingmore.json\n\n## Other comparisons with ShippyPro or TrackingMore\n\n- [EasyPost vs ShippyPro](https://www.anchorterminal.com/compare/easypost-vs-shippypro.md)\n- [Easyship vs ShippyPro](https://www.anchorterminal.com/compare/easyship-vs-shippypro.md)\n- [Karrio vs ShippyPro](https://www.anchorterminal.com/compare/karrio-vs-shippypro.md)\n- [Sendcloud vs ShippyPro](https://www.anchorterminal.com/compare/sendcloud-vs-shippypro.md)\n- [ShipBob vs ShippyPro](https://www.anchorterminal.com/compare/shipbob-vs-shippypro.md)\n- [Shippo vs ShippyPro](https://www.anchorterminal.com/compare/shippo-vs-shippypro.md)\n- [ShippyPro vs ShipStation API](https://www.anchorterminal.com/compare/shippypro-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 TrackingMore](https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.md)\n- [Ship24 vs ShippyPro](https://www.anchorterminal.com/compare/ship24-vs-shippypro.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- [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": "ShippyPro vs TrackingMore", "url": "" } ], "description": "ShippyPro scores 48.9 (D) to TrackingMore's 41.8 (E) for shipment tracking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ShippyPro D 48.9", "TrackingMore E 41.8", "scores" ], "h1": "ShippyPro vs TrackingMore", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/shippypro-vs-trackingmore", "published": "2026-10-01", "section": "tools", "title": "ShippyPro vs TrackingMore for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore" }, "tokens": { "markdown": 4650, "slim": 2980 }, "version": 1 }