{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/easyship.json", "name": "Easyship", "score": 70.6, "shared": [ "shipping.tracking" ], "slug": "easyship" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/sendcloud.json", "name": "Sendcloud", "score": 64.5, "shared": [ "shipping.tracking" ], "slug": "sendcloud" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/shippo.json", "name": "Shippo", "score": 61.9, "shared": [ "shipping.tracking" ], "slug": "shippo" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/shipbob.json", "name": "ShipBob", "score": 60.9, "shared": [ "shipping.tracking" ], "slug": "shipbob" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/shipstation.json", "name": "ShipStation API", "score": 59.3, "shared": [ "shipping.tracking" ], "slug": "shipstation" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/ship24.json", "name": "Ship24", "score": 55, "shared": [ "shipping.tracking" ], "slug": "ship24" } ], "tool": { "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": 1195, "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 65, "points": 13, "reason": "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.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 31, "points": 5.04, "reason": "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.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 54, "points": 8.78, "reason": "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.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 31, "points": 5.43, "reason": "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.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 23, "points": 2.88, "reason": "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.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 19, "points": 1.66, "reason": "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.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 57, "points": 4.99, "note": "editorial 39, provenance 74", "reason": "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.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "low", "notes": { "ergonomics": "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.", "maintenance": "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.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "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.", "transparency": "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." }, "sources": [ { "what": "Node SDK repository, cloned, 1.0.8, endpoints and response codes", "url": "https://github.com/TrackingMore-API/trackingmore-sdk-nodejs", "seen": "2026-11-03" }, { "what": "Python SDK repository, cloned", "url": "https://github.com/TrackingMore-API/trackingmore-sdk-python", "seen": "2026-11-03" }, { "what": "GitHub organisation repositories and push dates", "url": "https://api.github.com/orgs/TrackingMore-API/repos", "seen": "2026-11-03" }, { "what": "API reference, renders by script", "url": "https://www.trackingmore.com/docs/trackingmore/d5ac362fc3cda-api-quick-start", "seen": "2026-11-03" }, { "what": "rate limits", "url": "https://support.trackingmore.com/en/article/trackingmore-api-request-rate-limit-c0ye70/", "seen": "2026-11-03" }, { "what": "429 handling", "url": "https://support.trackingmore.com/en/article/why-do-i-get-429-response-code-error-in-your-api-2405za/", "seen": "2026-11-03" }, { "what": "response codes", "url": "https://support.trackingmore.com/en/article/response-codes-of-trackingmore-api-b0ipk0/", "seen": "2026-11-03" }, { "what": "create API", "url": "https://support.trackingmore.com/en/article/trackingmore-create-api-122cydg/", "seen": "2026-11-03" }, { "what": "API introduction", "url": "https://support.trackingmore.com/en/article/introduction-of-trackingmore-api-7w0txr/", "seen": "2026-11-03" }, { "what": "differences among API versions", "url": "https://support.trackingmore.com/en/article/differences-among-3-versions-of-trackingmore-api-1ip0fmh/", "seen": "2026-11-03" }, { "what": "API keys", "url": "https://support.trackingmore.com/en/article/generate-trackingmore-api-key-lhab6t/", "seen": "2026-11-03" }, { "what": "webhooks", "url": "https://support.trackingmore.com/en/article/webhook-1vrike4/", "seen": "2026-11-03" }, { "what": "bulk API", "url": "https://support.trackingmore.com/en/article/do-you-have-bulk-api-12mz8w4/", "seen": "2026-11-03" }, { "what": "API and webhook versions", "url": "https://support.trackingmore.com/en/article/something-you-need-to-know-about-trackingmore-api-webhook-1w51egp/", "seen": "2026-11-03" }, { "what": "pricing page, prices render by script", "url": "https://www.trackingmore.com/pricing", "seen": "2026-11-03" }, { "what": "tracking API page", "url": "https://www.trackingmore.com/tracking-api", "seen": "2026-11-03" }, { "what": "about page", "url": "https://www.trackingmore.com/about-us", "seen": "2026-11-03" }, { "what": "status page", "url": "https://status.trackingmore.com/", "seen": "2026-11-03" }, { "what": "CWILL terms of service", "url": "https://www.cwill.com/terms-of-service/", "seen": "2026-11-03" }, { "what": "CWILL privacy policy", "url": "https://www.cwill.com/privacy-policy/", "seen": "2026-11-03" }, { "what": "CWILL about page", "url": "https://www.cwill.com/about-us/", "seen": "2026-11-03" }, { "what": "robots.txt", "url": "https://www.trackingmore.com/robots.txt", "seen": "2026-11-03" }, { "what": "security.txt, 404", "url": "https://www.trackingmore.com/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "official MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=trackingmore", "seen": "2026-11-03" }, { "what": "RDAP record", "url": "https://rdap.verisign.com/com/v1/domain/trackingmore.com", "seen": "2026-11-03" } ], "openQuestions": [ "unchecked: the API reference at trackingmore.com/docs, which renders by script. Field types, enums, pagination and response shapes were taken from the SDK READMEs and support articles, so schema and ergonomics may be understated", "unchecked: plan prices on the pricing page, which render by script; the credits per plan and the price per credit are unknown. The $0.03 figure is the API page's from price", "unchecked: the status page's uptime figures and update history, which render by script, and whether it has a readable feed", "unchecked: the CWILL Acceptable Use Policy, the DPA at cwill.com/legal/dpa/ and the sub-processor list at trust.cwill.com, so retention, data locations and any clause on automated access are unread", "unchecked: whether the Free plan or the 14-day trial asks for a card, and whether Free includes API access (the pricing table lists API keys from Basic up)", "unchecked: GitHub issues on the SDK repositories, and npm and PyPI downloads", "Judgement call on the legal entity. trackingmore.com links its terms and privacy policy to cwill.com, whose privacy policy names CHANNELWILL CO., LIMITED (Hong Kong) as controller for TrackingMore. The listing uses that name as vendor", "firstReleased is left empty. The about page says TrackingMore has run since 2014 and the domain was registered on 27 October 2014, but no exact first-hand release date was found", "status.trackingmore.com was fetched before its own robots.txt was checked; the page is a hosted status page that rendered no incident text, and nothing from it moves a score beyond the presence of a status page", "The MCP registry entry io.usefulapi/trackingmore is a third party's server and was not graded" ] }, "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 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "E", "kind": "listed", "method": "0.7", "score": 41.8 } ] }, "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" }, "notable": [ "API v4 at https://api.trackingmore.com/v4 has nine documented calls, couriers/all, couriers/detect, trackings/create, trackings/batch (up to 40), trackings/get, trackings/update/{id}, trackings/delete/{id}, trackings/retrack/{id} and awb, per the official Node SDK README (https://github.com/TrackingMore-API/trackingmore-sdk-nodejs)", "Rate limits are per account and per endpoint, 3 requests a second on trackings/create and 10 a second on every other v4 call, with a 429 after which the application should wait 120 seconds (https://support.trackingmore.com/en/article/trackingmore-api-request-rate-limit-c0ye70/)", "Responses carry an HTTP code and a meta code. 4101 means the tracking already exists, 4121 that no courier was detected, 4190 that the plan quota is reached, 429 too many requests, and 511 to 513 are server errors (https://github.com/TrackingMore-API/trackingmore-sdk-nodejs)", "The API reference at trackingmore.com/docs renders by script and could not be read, and no OpenAPI file was found; the surface was read from the SDKs and the support centre (https://www.trackingmore.com/docs/trackingmore/)", "The terms and privacy links on trackingmore.com redirect to cwill.com, where the privacy policy (effective 8 August 2026) names CHANNELWILL CO., LIMITED of Hong Kong as the data controller for TrackingMore and the terms (effective 9 January 2026) are CWILL's (https://www.cwill.com/privacy-policy/)", "Webhooks are set in the web app, up to four URLs, filtered by status, with a test action, and the webhook version must match the API version (https://support.trackingmore.com/en/article/webhook-1vrike4/)", "The seven official SDKs (PHP, Python, Node, Java, Go, Ruby, .NET) were last pushed between February and December 2024, and npm has trackingmore-sdk-nodejs 1.0.8 (https://api.github.com/orgs/TrackingMore-API/repos)", "The official MCP registry has only a third-party TrackingMore server, io.usefulapi/trackingmore, and no vendor entry (https://registry.modelcontextprotocol.io/v0/servers?search=trackingmore)" ], "area": "business", "details": [ { "label": "Surface listed", "value": "The REST API v4 at api.trackingmore.com, read from the official SDK repositories, the support centre, trackingmore.com, status.trackingmore.com and the CWILL legal pages on 3 November 2026. The reference docs at trackingmore.com/docs render by script and were not read. No account was made and no call was sent" }, { "label": "API", "value": "JSON over HTTPS. GET couriers/all, POST couriers/detect, POST trackings/create, POST trackings/batch, GET trackings/get, PUT trackings/update/{id}, DELETE trackings/delete/{id}, POST trackings/retrack/{id}, POST awb. v2 and v3 are still served with their own headers and meta codes" }, { "label": "Credentials", "value": "Tracking-Api-Key header. Keys are generated under Developer, API key, shown once, at most four per account, deleted from the same page. No scopes" }, { "label": "Rate limits", "value": "Per account per endpoint. 3 requests a second on trackings/create, 10 a second on batch, get, update, delete, retrack, awb, couriers/all and couriers/detect. Custom limits on Enterprise. 429 with a 120-second wait" }, { "label": "Errors", "value": "HTTP 200, 400, 401, 403, 404, 429 and 500 with meta codes 4101 to 4190 for bad requests (duplicate, missing or invalid tracking number, invalid or undetected courier, required fields, invalid field format, awb errors, quota reached) and 511 to 513 for server errors" }, { "label": "Webhooks", "value": "Up to four URLs per account, chosen statuses (info received, in transit, out for delivery, failed attempt, delivered, exception, expired, not found), test and disable actions, a notification log, retries and a published outgoing IP list per the support centre" }, { "label": "Plans", "value": "Free, Basic (two keys, 6 requests a second, two webhook endpoints), Pro (five keys, 10 a second, five endpoints) and Enterprise (eight keys, custom limits, eight endpoints, 99.99 per cent API uptime line, invoice payment), priced in credits a month. Prices render by script" }, { "label": "SDKs", "value": "trackingmore-sdk-nodejs 1.0.8, -python, -php, -ruby, -java, -go and -net on GitHub, MIT. Last pushes February to December 2024. The Node SDK has no CI workflow" }, { "label": "Status", "value": "status.trackingmore.com, a hosted status page whose uptime figures and update history render by script. Its static text says there are no updates in the last 7 days" }, { "label": "Company", "value": "TrackingMore says it was founded in 2014 by Clooney Wang. The CWILL about page says Bo Liu and Clooney Wang built a parcel tracking system in 2014 and the group started as Channelwill. Its privacy policy names CHANNELWILL CO., LIMITED, Hong Kong, as the controller for TrackingMore and CWILL INC, Delaware, for other products" } ], "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, "checks": [ { "check": "Legal entity named", "value": "CHANNELWILL CO., LIMITED", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "trackingmore.com, registered 2014-10-27 (12 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "api.trackingmore.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 5 of the 7 things a reader expects, and has 3 clauses that cost points", "points": 2.3, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 8 of the 8 things a reader expects", "points": 10, "max": 10, "state": "ok" }, { "check": "Status page", "value": "status.trackingmore.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "People named", "value": "2 named with their role, none with a public profile", "points": 7, "max": 10, "state": "part" }, { "check": "Support route", "value": "a support address, help pages, a community", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://www.cwill.com/terms-of-service/", "state": "read", "readAt": "2026-11-03", "words": 8340, "points": 2.3, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "These Terms will be governed by and construed in accordance with the laws of Hong Kong, without giving effect to any conflict of laws, rules or provisions.", "says": "The law of Hong Kong" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "Notwithstanding anything to the contrary in these terms, in no event shall CWILL's entire liability to You under these terms, whether in contract, tort (including negligence), strict liability or otherwise, exceed the price paid by You during the twelve (12) months immediately preceding the first event giving rise to…", "says": "Capped at the fees paid in the 12 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "otherwise, CWILL shall have the right to immediately suspend or terminate the Service without assuming any liability." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": true, "quote": "We may update these Terms from time to time and may notify You of any of these updates by in-app notifications, the Site, or through email if You have subscribed to receive email updates.", "says": "Says it gives notice of a change" }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "You may not use the Site if You are not of a legal age to form a binding contract and otherwise capable of entering into these Terms." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "toKnow": [ { "key": "terms.automated", "label": "Restricts automated access", "found": true, "quote": "(r) not to access the Service in bulk through automated tools (such as crawlers, robot programs) unless prior written permission from CWILL is obtained;", "costsPoints": true }, { "key": "terms.benchmark", "label": "Restricts benchmarking or competitive use", "found": true, "quote": "(o) not to use or access the Service in order to monitor the availability, performance or functionality of the Service or for any other similar benchmarking purposes;", "costsPoints": true }, { "key": "terms.nonotice", "label": "Says the terms or the service can change without notice", "found": true, "quote": "CWILL reserves the right to: (1) modify or update any of the Terms of Service, effective upon its posting on the Site", "costsPoints": true }, { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "CWILL reserves the right in its sole discretion to terminate Your Account, delete Your profile and any of Your Data and restrict Your use of all or any part of the Service for any or no reason, without notice, and without liability to You or anyone else." } ], "notes": [ { "date": "2026-11-03", "text": "Liability is capped at fees paid in the preceding twelve months, or 100 US dollars where no fees were paid in that period.", "quote": "If You have not paid any fees during such period, Your liability cap shall be USD 100." }, { "date": "2026-11-03", "text": "Use of the service for commercial purposes unrelated to logistics tracking, including data mining and machine learning training, is prohibited.", "quote": "(s) not to use the Service for commercial purposes unrelated to logistics tracking, including but not limited to data mining and machine learning training." }, { "date": "2026-11-03", "text": "The customer grants a licence for CWILL to use its trademarks, trade name and logo in marketing, with no obligation to submit materials beforehand.", "quote": "Unless provided otherwise in writing, CWILL shall have no obligations towards User to submit advertising materials containing User's trademark prior to distribution, promotion and marketing of CWILL Service." } ] }, { "kind": "privacy", "url": "https://www.cwill.com/privacy-policy/", "state": "read", "readAt": "2026-11-03", "statedDate": "2026-08-08", "words": 5517, "points": 10, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Effective Date: August 8, 2026", "says": "Last updated 2026-08-08" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "We limit the Personal Data we collect to information required to support the intended purpose of collection." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "For all CWILL Products, Personal Data is generally retained for 180 days from the date of collection, after which it is deleted or anonymized.", "says": "Names a period of 180 days" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "Request to know the categories and specific pieces of Personal Data we have collected, the sources, the purposes, and the categories of third parties with whom we have shared your data." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "CWILL does not sell Personal Data for monetary consideration.", "says": "Says it does not sell personal data" }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "…with a comprehensive privacy law, you may have rights similar to those described above, including the right to access, correct, delete, and opt out of targeted advertising and profiling that produces legal or similarly significant effects." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "Send an email to [email protected], contact our Data Protection Officer at [email protected], or submit a request through our online form.", "says": "Names a data protection officer" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "You may also request a copy of any standard contractual clauses governing the international transfer of your Personal Data.", "says": "Relies on standard contractual clauses" } ], "toKnow": [ { "key": "privacy.sells", "label": "Says it sells personal data or shares it for advertising", "found": true, "quote": "Certain third-party analytics tools used on our Sites may constitute 'sharing' for cross-context behavioral advertising under the CCPA." } ], "notes": [ { "date": "2026-11-03", "text": "Order tracking, review and email data are processed by third-party AI providers, named as Google Gemini and OpenAI models.", "quote": "CWILL utilizes artificial intelligence ('AI') technologies, including third-party AI models, to enhance and provide certain features of the Services ('AI Features')." }, { "date": "2026-11-03", "text": "States that Personal Data collected through the Services is not used to train large language models.", "quote": "CWILL does not use Personal Data collected through the Services for training large language models." } ] } ] }, "humans": { "slug": "trackingmore", "checked": "2026-11-03", "company": "CHANNELWILL CO., LIMITED", "people": [ { "name": "Clooney Wang", "role": "Founder, TrackingMore; Co-founder, CWILL", "founder": true, "bio": "Clooney Wang founded TrackingMore in 2014. The TrackingMore about page says he had been a coding teacher and started the service after a former student described the pain of tracking shipments when selling globally. The CWILL about page says he and Bo Liu built the first parcel tracking system in 2014 and lists him as co-founder.", "bioSources": [ "https://www.trackingmore.com/about-us", "https://www.cwill.com/about-us/" ], "page": "/people/clooney-wang/" }, { "name": "Bo Liu", "role": "Founder and CEO, CWILL", "founder": true, "bio": "Bo Liu is the founder and chief executive of CWILL, the group that runs TrackingMore. Its about page says he sold online before building software, and that in 2014 he and Clooney Wang built a parcel tracking system that grew into the Channelwill, later CWILL, product family.", "bioSources": [ "https://www.cwill.com/about-us/" ], "page": "/people/bo-liu/" } ], "peopleNote": "TrackingMore's about page (read 3 November 2026) names Clooney Wang as founder and gives milestones from 2014. Its legal pages redirect to cwill.com, whose privacy policy names CHANNELWILL CO., LIMITED of Hong Kong as the controller for TrackingMore and whose about page lists Bo Liu as Founder \u0026 CEO and Clooney Wang as Co-Founder of CWILL, which began as Channelwill in 2014. No personal LinkedIn, X or GitHub account is linked from either site, so none is listed. Investors were looked for on the TrackingMore about page, the CWILL about page, terms and privacy policy; none names a funding round or investor, and no outside search was made.", "companySocial": { "linkedin": "https://www.linkedin.com/company/trackingmore-official", "x": "https://x.com/TrackingMore9", "github": "https://github.com/TrackingMore-API" }, "support": { "emails": [ "support@trackingmore.com" ], "urls": [ "https://support.trackingmore.com/en/", "https://support.trackingmore.com/en/category/api-webhook-oop8bq/" ], "community": [ { "label": "TrackingMore API SDKs on GitHub", "url": "https://github.com/TrackingMore-API", "kind": "github" } ], "contactEmails": [ "support@trackingmore.com" ], "contactUrls": [ "https://www.trackingmore.com/en/contact-sales" ] }, "sources": [ "https://www.trackingmore.com/about-us", "https://www.trackingmore.com/", "https://www.cwill.com/about-us/", "https://www.cwill.com/privacy-policy/", "https://www.cwill.com/terms-of-service/", "https://support.trackingmore.com/en/article/differences-among-3-versions-of-trackingmore-api-1ip0fmh/", "https://api.github.com/orgs/TrackingMore-API/repos" ], "ownership": { "status": "private", "checked": "2026-11-03", "sources": [ "https://www.cwill.com/privacy-policy/", "https://www.cwill.com/about-us/" ] } }, "pageJsonUrl": "https://www.anchorterminal.com/tools/trackingmore.json", "live": { "slug": "trackingmore", "probe": { "target": "https://api.trackingmore.com/v4", "method": "get", "lastAt": "2026-11-04T20:05:31.150203661Z", "lastOk": true, "lastStatus": 404, "lastMs": 508, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 565, "p95ms24h": 740, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-11-04", "probes": 48, "ok": 48 } ] }, "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:05:31.150203661Z" } }, "verify": { "accepts": "a page on trackingmore.com or one of its subdomains, or the README at the root of github.com/TrackingMore-API/trackingmore-sdk-nodejs", "badgeUrl": "https://www.anchorterminal.com/badges/trackingmore.svg", "body": { "slug": "trackingmore", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/trackingmore", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/trackingmore\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/trackingmore.svg\" alt=\"TrackingMore on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![TrackingMore on Anchor Terminal](https://www.anchorterminal.com/badges/trackingmore.svg)](https://www.anchorterminal.com/tools/trackingmore)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/trackingmore\"\u003eTrackingMore on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/trackingmore", "json": "https://www.anchorterminal.com/tools/trackingmore.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/trackingmore.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/trackingmore#pricing", "reviews": "https://www.anchorterminal.com/tools/trackingmore#reviews", "slim": "https://www.anchorterminal.com/tools/trackingmore.min.md" }, "markdown": "## Overview\n\n**Grade E · 41.8/100 · rank #1195 of 1349 · #10 in Shipping \u0026 fulfilment · not agent-ready · confidence low**\n\n\n## Assessment\n\nA 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | CHANNELWILL CO., LIMITED (https://www.trackingmore.com) |\n| Kind | HTTP API |\n| Category | Shipping \u0026 fulfilment (https://www.anchorterminal.com/categories/shipping) |\n| Transport | HTTP |\n| Endpoint | `https://api.trackingmore.com/v4` |\n| Auth | API key · 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. |\n| Pricing | Freemium ($0.03 / tx) · 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). |\n| x402 | No · 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. |\n| Licence | Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT |\n| Packages | npm: `trackingmore-sdk-nodejs`; pypi: `trackingmore-sdk-python`; go: `github.com/TrackingMore-API/trackingmore-sdk-go` |\n| Source | https://github.com/TrackingMore-API/trackingmore-sdk-nodejs |\n| Docs | https://www.trackingmore.com/docs/trackingmore/ |\n| llms.txt | not found |\n| Last release | 2024-12-25 |\n| GitHub stars | 6 (as of 2026-11-03) |\n| Surface listed | The REST API v4 at api.trackingmore.com, read from the official SDK repositories, the support centre, trackingmore.com, status.trackingmore.com and the CWILL legal pages on 3 November 2026. The reference docs at trackingmore.com/docs render by script and were not read. No account was made and no call was sent |\n| API | JSON over HTTPS. GET couriers/all, POST couriers/detect, POST trackings/create, POST trackings/batch, GET trackings/get, PUT trackings/update/{id}, DELETE trackings/delete/{id}, POST trackings/retrack/{id}, POST awb. v2 and v3 are still served with their own headers and meta codes |\n| Credentials | Tracking-Api-Key header. Keys are generated under Developer, API key, shown once, at most four per account, deleted from the same page. No scopes |\n| Rate limits | Per account per endpoint. 3 requests a second on trackings/create, 10 a second on batch, get, update, delete, retrack, awb, couriers/all and couriers/detect. Custom limits on Enterprise. 429 with a 120-second wait |\n| Errors | HTTP 200, 400, 401, 403, 404, 429 and 500 with meta codes 4101 to 4190 for bad requests (duplicate, missing or invalid tracking number, invalid or undetected courier, required fields, invalid field format, awb errors, quota reached) and 511 to 513 for server errors |\n| Webhooks | Up to four URLs per account, chosen statuses (info received, in transit, out for delivery, failed attempt, delivered, exception, expired, not found), test and disable actions, a notification log, retries and a published outgoing IP list per the support centre |\n| Plans | Free, Basic (two keys, 6 requests a second, two webhook endpoints), Pro (five keys, 10 a second, five endpoints) and Enterprise (eight keys, custom limits, eight endpoints, 99.99 per cent API uptime line, invoice payment), priced in credits a month. Prices render by script |\n| SDKs | trackingmore-sdk-nodejs 1.0.8, -python, -php, -ruby, -java, -go and -net on GitHub, MIT. Last pushes February to December 2024. The Node SDK has no CI workflow |\n| Status | status.trackingmore.com, a hosted status page whose uptime figures and update history render by script. Its static text says there are no updates in the last 7 days |\n| Company | TrackingMore says it was founded in 2014 by Clooney Wang. The CWILL about page says Bo Liu and Clooney Wang built a parcel tracking system in 2014 and the group started as Channelwill. Its privacy policy names CHANNELWILL CO., LIMITED, Hong Kong, as the controller for TrackingMore and CWILL INC, Delaware, for other products |\n| Capabilities | shipping.tracking |\n| Tags | official, hosted, closed-source, api-key, webhooks, free-tier, free-trial, freemium, status-page, python, typescript, go, java, php, ruby, dotnet |\n| JSON | https://www.anchorterminal.com/api/v1/tools/trackingmore.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 65 | 13.0 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 31 | 5.0 |\n| Agent ergonomics | 13% | 16.2 | 54 | 8.8 |\n| Security \u0026 auth | 14% | 17.5 | 31 | 5.4 |\n| Payments \u0026 pricing | 10% | 12.5 | 23 | 2.9 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 19 | 1.7 |\n| Transparency \u0026 trust (editorial 39, provenance 74) | 7% | 8.8 | 57 | 5.0 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **41.8 → E** |\n\n### Why each score\n\n- Reliability 65 (checked 2026-11-03): 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- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 31 (checked 2026-11-03): 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- Agent ergonomics 54 (checked 2026-11-03): 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- Security \u0026 auth 31 (checked 2026-11-03): 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- Payments \u0026 pricing 23 (checked 2026-11-03): 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 19 (checked 2026-11-03): 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- Transparency \u0026 trust 57 (checked 2026-11-03): 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\nFix list, everything this grade says the listing lacks, the biggest gain first (21 items). What it covers is at https://www.anchorterminal.com/fixes/trackingmore.md (JSON https://www.anchorterminal.com/fixes/trackingmore.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"trackingmore\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- unchecked: the API reference at trackingmore.com/docs, which renders by script. Field types, enums, pagination and response shapes were taken from the SDK READMEs and support articles, so schema and ergonomics may be understated\n- unchecked: plan prices on the pricing page, which render by script; the credits per plan and the price per credit are unknown. The $0.03 figure is the API page's from price\n- unchecked: the status page's uptime figures and update history, which render by script, and whether it has a readable feed\n- unchecked: the CWILL Acceptable Use Policy, the DPA at cwill.com/legal/dpa/ and the sub-processor list at trust.cwill.com, so retention, data locations and any clause on automated access are unread\n- unchecked: whether the Free plan or the 14-day trial asks for a card, and whether Free includes API access (the pricing table lists API keys from Basic up)\n- unchecked: GitHub issues on the SDK repositories, and npm and PyPI downloads\n- Judgement call on the legal entity. trackingmore.com links its terms and privacy policy to cwill.com, whose privacy policy names CHANNELWILL CO., LIMITED (Hong Kong) as controller for TrackingMore. The listing uses that name as vendor\n- firstReleased is left empty. The about page says TrackingMore has run since 2014 and the domain was registered on 27 October 2014, but no exact first-hand release date was found\n- status.trackingmore.com was fetched before its own robots.txt was checked; the page is a hosted status page that rendered no incident text, and nothing from it moves a score beyond the presence of a status page\n- The MCP registry entry io.usefulapi/trackingmore is a third party's server and was not graded\n\n### Sources\n\n- Node SDK repository, cloned, 1.0.8, endpoints and response codes: \u003chttps://github.com/TrackingMore-API/trackingmore-sdk-nodejs\u003e (seen 2026-11-03)\n- Python SDK repository, cloned: \u003chttps://github.com/TrackingMore-API/trackingmore-sdk-python\u003e (seen 2026-11-03)\n- GitHub organisation repositories and push dates: \u003chttps://api.github.com/orgs/TrackingMore-API/repos\u003e (seen 2026-11-03)\n- API reference, renders by script: \u003chttps://www.trackingmore.com/docs/trackingmore/d5ac362fc3cda-api-quick-start\u003e (seen 2026-11-03)\n- rate limits: \u003chttps://support.trackingmore.com/en/article/trackingmore-api-request-rate-limit-c0ye70/\u003e (seen 2026-11-03)\n- 429 handling: \u003chttps://support.trackingmore.com/en/article/why-do-i-get-429-response-code-error-in-your-api-2405za/\u003e (seen 2026-11-03)\n- response codes: \u003chttps://support.trackingmore.com/en/article/response-codes-of-trackingmore-api-b0ipk0/\u003e (seen 2026-11-03)\n- create API: \u003chttps://support.trackingmore.com/en/article/trackingmore-create-api-122cydg/\u003e (seen 2026-11-03)\n- API introduction: \u003chttps://support.trackingmore.com/en/article/introduction-of-trackingmore-api-7w0txr/\u003e (seen 2026-11-03)\n- differences among API versions: \u003chttps://support.trackingmore.com/en/article/differences-among-3-versions-of-trackingmore-api-1ip0fmh/\u003e (seen 2026-11-03)\n- API keys: \u003chttps://support.trackingmore.com/en/article/generate-trackingmore-api-key-lhab6t/\u003e (seen 2026-11-03)\n- webhooks: \u003chttps://support.trackingmore.com/en/article/webhook-1vrike4/\u003e (seen 2026-11-03)\n- bulk API: \u003chttps://support.trackingmore.com/en/article/do-you-have-bulk-api-12mz8w4/\u003e (seen 2026-11-03)\n- API and webhook versions: \u003chttps://support.trackingmore.com/en/article/something-you-need-to-know-about-trackingmore-api-webhook-1w51egp/\u003e (seen 2026-11-03)\n- pricing page, prices render by script: \u003chttps://www.trackingmore.com/pricing\u003e (seen 2026-11-03)\n- tracking API page: \u003chttps://www.trackingmore.com/tracking-api\u003e (seen 2026-11-03)\n- about page: \u003chttps://www.trackingmore.com/about-us\u003e (seen 2026-11-03)\n- status page: \u003chttps://status.trackingmore.com/\u003e (seen 2026-11-03)\n- CWILL terms of service: \u003chttps://www.cwill.com/terms-of-service/\u003e (seen 2026-11-03)\n- CWILL privacy policy: \u003chttps://www.cwill.com/privacy-policy/\u003e (seen 2026-11-03)\n- CWILL about page: \u003chttps://www.cwill.com/about-us/\u003e (seen 2026-11-03)\n- robots.txt: \u003chttps://www.trackingmore.com/robots.txt\u003e (seen 2026-11-03)\n- security.txt, 404: \u003chttps://www.trackingmore.com/.well-known/security.txt\u003e (seen 2026-11-03)\n- official MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=trackingmore\u003e (seen 2026-11-03)\n- RDAP record: \u003chttps://rdap.verisign.com/com/v1/domain/trackingmore.com\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/trackingmore/history.json\n\n- 2026-11-03: graded 41.8 E (methodology 0.7)\n\n## Who's behind it (provenance 74/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | CHANNELWILL CO., LIMITED | 20/20 |\n| Domain age | trackingmore.com, registered 2014-10-27 (12 years) | 15/15 |\n| Endpoint on the vendor's domain | api.trackingmore.com | 15/15 |\n| Terms of service | read, states 5 of the 7 things a reader expects, and has 3 clauses that cost points | 2.3/10 |\n| Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 |\n| Status page | status.trackingmore.com | 10/10 |\n| Changelog | not found | 0/10 |\n| security.txt | not found | 0/10 |\n| People named | 2 named with their role, none with a public profile | 7/10 |\n| Support route | a support address, help pages, a community | 5/5 |\n\ntrackingmore.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.\n\nThe 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.\n\nwww.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.\n\nThe API answers at api.trackingmore.com, a vendor subdomain.\n\nwww.trackingmore.com/.well-known/security.txt returns 404, and no security page was found on trackingmore.com (the /security path returns 404).\n\nRDAP gives trackingmore.com a registration date of 27 October 2014.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://www.cwill.com/terms-of-service/), read 2026-11-03, gives no date, states 5 of the 7 things a reader expects.\n\n- To know. Restricts automated access (costs points). \"(r) not to access the Service in bulk through automated tools (such as crawlers, robot programs) unless prior written permission from CWILL is obtained;\"\n- To know. Restricts benchmarking or competitive use (costs points). \"(o) not to use or access the Service in order to monitor the availability, performance or functionality of the Service or for any other similar benchmarking purposes;\"\n- To know. Says the terms or the service can change without notice (costs points). \"CWILL reserves the right to: (1) modify or update any of the Terms of Service, effective upon its posting on the Site\"\n- To know. Says access can be ended without notice or for any reason. \"CWILL reserves the right in its sole discretion to terminate Your Account, delete Your profile and any of Your Data and restrict Your use of all or any part of the Service for any or no reason, without notice, and without liability to You or anyone else.\"\n- Not found in the text. Gives the date it was last updated.\n- Names the governing law or courts. The law of Hong Kong.\n- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.\n- Says how changes to the terms are announced. Says it gives notice of a change.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-11-03). Liability is capped at fees paid in the preceding twelve months, or 100 US dollars where no fees were paid in that period. \"If You have not paid any fees during such period, Your liability cap shall be USD 100.\"\n- Also in the text (2026-11-03). Use of the service for commercial purposes unrelated to logistics tracking, including data mining and machine learning training, is prohibited. \"(s) not to use the Service for commercial purposes unrelated to logistics tracking, including but not limited to data mining and machine learning training.\"\n- Also in the text (2026-11-03). The customer grants a licence for CWILL to use its trademarks, trade name and logo in marketing, with no obligation to submit materials beforehand. \"Unless provided otherwise in writing, CWILL shall have no obligations towards User to submit advertising materials containing User's trademark prior to distribution, promotion and marketing of CWILL Service.\"\n\n**Privacy policy** (https://www.cwill.com/privacy-policy/), read 2026-11-03, dated 2026-08-08, states 8 of the 8 things a reader expects.\n\n- To know. Says it sells personal data or shares it for advertising. \"Certain third-party analytics tools used on our Sites may constitute 'sharing' for cross-context behavioral advertising under the CCPA.\"\n- Gives the date it was last updated. Last updated 2026-08-08.\n- Says how long data is kept. Names a period of 180 days.\n- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.\n- Gives a privacy contact. Names a data protection officer.\n- Says where data is transferred or stored. Relies on standard contractual clauses.\n- Also in the text (2026-11-03). Order tracking, review and email data are processed by third-party AI providers, named as Google Gemini and OpenAI models. \"CWILL utilizes artificial intelligence ('AI') technologies, including third-party AI models, to enhance and provide certain features of the Services ('AI Features').\"\n- Also in the text (2026-11-03). States that Personal Data collected through the Services is not used to train large language models. \"CWILL does not use Personal Data collected through the Services for training large language models.\"\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- Clooney Wang, Founder, TrackingMore; Co-founder, CWILL\n- Bo Liu, Founder and CEO, CWILL\n- Note: TrackingMore's about page (read 3 November 2026) names Clooney Wang as founder and gives milestones from 2014. Its legal pages redirect to cwill.com, whose privacy policy names CHANNELWILL CO., LIMITED of Hong Kong as the controller for TrackingMore and whose about page lists Bo Liu as Founder \u0026 CEO and Clooney Wang as Co-Founder of CWILL, which began as Channelwill in 2014. No personal LinkedIn, X or GitHub account is linked from either site, so none is listed. Investors were looked for on the TrackingMore about page, the CWILL about page, terms and privacy policy; none names a funding round or investor, and no outside search was made.\n- CHANNELWILL CO., LIMITED: LinkedIn https://www.linkedin.com/company/trackingmore-official X https://x.com/TrackingMore9 GitHub https://github.com/TrackingMore-API\n\n### Getting support\n\n- Support email: support@trackingmore.com\n- Help: https://support.trackingmore.com/en/\n- Help: https://support.trackingmore.com/en/category/api-webhook-oop8bq/\n- Community (TrackingMore API SDKs on GitHub): https://github.com/TrackingMore-API\n- Sources: https://www.trackingmore.com/about-us, https://www.trackingmore.com/, https://www.cwill.com/about-us/, https://www.cwill.com/privacy-policy/, https://www.cwill.com/terms-of-service/, https://support.trackingmore.com/en/article/differences-among-3-versions-of-trackingmore-api-1ip0fmh/, https://api.github.com/orgs/TrackingMore-API/repos\n\n## Live (updated 2026-11-04 20:05 UTC)\n\n- Right now: up, HTTP 404, 508 ms, checked 2026-11-04 20:05 UTC (get on `https://api.trackingmore.com/v4`)\n- Uptime 24h 100.0% (48 probes) · 30 days 100.0% (48 probes) · p50 565 ms · p95 740 ms\n- Vendor status page: unknown, no machine-readable status found\n- security.txt: none\n- Always current: https://www.anchorterminal.com/api/v1/live/trackingmore.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Tracked order | $0.03 | per transaction | the from price on the API page; plan prices render by script and were not read |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Nine v4 calls cover detect, create, batch create of 40, get, update, delete, retrack and air waybills, with webhooks for status changes\n- 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\n- HTTP and meta codes with messages, including 4101 for a duplicate tracking, so a retried create is rejected rather than doubled\n- Official SDKs in PHP, Python, Node, Java, Go, Ruby and .NET, MIT, plus a Postman collection\n- Free plan and a 14-day trial, with courier detection free on v4\n\n## Weaknesses\n\n- The API reference renders by script and no OpenAPI file, llms.txt or Markdown docs were found\n- One API key with full access, at most four per account, no scopes and no read-only key\n- No idempotency key, no Retry-After, and no SLA beyond a 99.99 per cent uptime line on the Enterprise plan\n- The SDKs were last updated between February and December 2024, and no dated API changelog was found\n- Plan prices render by script and were not read; the terms and privacy policy are CWILL group documents that name different entities per product\n\n\n\n## Before you call it (notes for agents)\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## Connect\n\nInstall:\n\n```bash\nnpm install trackingmore-sdk-nodejs\n```\n\nFirst request:\n\n```bash\ncurl -H \"Tracking-Api-Key: $TRACKINGMORE_API_KEY\" https://api.trackingmore.com/v4/couriers/all\n```\n\nThrough letme: https://letme.dev/trackingmore. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| Easyship | BB | 70.6 | 173 | shipping.tracking | no | https://www.anchorterminal.com/tools/easyship.md |\n| Sendcloud | B | 64.5 | 402 | shipping.tracking | no | https://www.anchorterminal.com/tools/sendcloud.md |\n| Shippo | C | 61.9 | 487 | shipping.tracking | no | https://www.anchorterminal.com/tools/shippo.md |\n| ShipBob | C | 60.9 | 531 | shipping.tracking | no | https://www.anchorterminal.com/tools/shipbob.md |\n| ShipStation API | C | 59.3 | 635 | shipping.tracking | no | https://www.anchorterminal.com/tools/shipstation.md |\n| Ship24 | C | 55 | 852 | shipping.tracking | no | https://www.anchorterminal.com/tools/ship24.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- API v4 at https://api.trackingmore.com/v4 has nine documented calls, couriers/all, couriers/detect, trackings/create, trackings/batch (up to 40), trackings/get, trackings/update/{id}, trackings/delete/{id}, trackings/retrack/{id} and awb, per the official Node SDK README (source: \u003chttps://github.com/TrackingMore-API/trackingmore-sdk-nodejs\u003e)\n- Rate limits are per account and per endpoint, 3 requests a second on trackings/create and 10 a second on every other v4 call, with a 429 after which the application should wait 120 seconds (source: \u003chttps://support.trackingmore.com/en/article/trackingmore-api-request-rate-limit-c0ye70/\u003e)\n- Responses carry an HTTP code and a meta code. 4101 means the tracking already exists, 4121 that no courier was detected, 4190 that the plan quota is reached, 429 too many requests, and 511 to 513 are server errors (source: \u003chttps://github.com/TrackingMore-API/trackingmore-sdk-nodejs\u003e)\n- The API reference at trackingmore.com/docs renders by script and could not be read, and no OpenAPI file was found; the surface was read from the SDKs and the support centre (source: \u003chttps://www.trackingmore.com/docs/trackingmore/\u003e)\n- The terms and privacy links on trackingmore.com redirect to cwill.com, where the privacy policy (effective 8 August 2026) names CHANNELWILL CO., LIMITED of Hong Kong as the data controller for TrackingMore and the terms (effective 9 January 2026) are CWILL's (source: \u003chttps://www.cwill.com/privacy-policy/\u003e)\n- Webhooks are set in the web app, up to four URLs, filtered by status, with a test action, and the webhook version must match the API version (source: \u003chttps://support.trackingmore.com/en/article/webhook-1vrike4/\u003e)\n- The seven official SDKs (PHP, Python, Node, Java, Go, Ruby, .NET) were last pushed between February and December 2024, and npm has trackingmore-sdk-nodejs 1.0.8 (source: \u003chttps://api.github.com/orgs/TrackingMore-API/repos\u003e)\n- The official MCP registry has only a third-party TrackingMore server, io.usefulapi/trackingmore, and no vendor entry (source: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=trackingmore\u003e)\n\n- #10 of 10 in 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## Compare\n\n- [EasyPost vs TrackingMore](https://www.anchorterminal.com/compare/easypost-vs-trackingmore.md): C 54.4 vs E 41.8\n- [Easyship vs TrackingMore](https://www.anchorterminal.com/compare/easyship-vs-trackingmore.md): BB 70.6 vs E 41.8\n- [Karrio vs TrackingMore](https://www.anchorterminal.com/compare/karrio-vs-trackingmore.md): D 48.9 vs E 41.8\n- [Sendcloud vs TrackingMore](https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.md): B 64.5 vs E 41.8\n- [Ship24 vs TrackingMore](https://www.anchorterminal.com/compare/ship24-vs-trackingmore.md): C 55 vs E 41.8\n- [ShipBob vs TrackingMore](https://www.anchorterminal.com/compare/shipbob-vs-trackingmore.md): C 60.9 vs E 41.8\n- [Shippo vs TrackingMore](https://www.anchorterminal.com/compare/shippo-vs-trackingmore.md): C 61.9 vs E 41.8\n- [ShippyPro vs TrackingMore](https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.md): D 48.9 vs E 41.8\n- [ShipStation API vs TrackingMore](https://www.anchorterminal.com/compare/shipstation-vs-trackingmore.md): C 59.3 vs E 41.8\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on trackingmore.com or one of its subdomains, or the README at the root of github.com/TrackingMore-API/trackingmore-sdk-nodejs. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"trackingmore\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/trackingmore\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/trackingmore.svg\" alt=\"TrackingMore on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![TrackingMore on Anchor Terminal](https://www.anchorterminal.com/badges/trackingmore.svg)](https://www.anchorterminal.com/tools/trackingmore)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/trackingmore\"\u003eTrackingMore on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say TrackingMore is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/trackingmore-dark.png\n- Light: https://www.anchorterminal.com/assets/share/trackingmore-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Shipping \u0026 fulfilment", "url": "https://www.anchorterminal.com/categories/shipping" }, { "name": "TrackingMore", "url": "" } ], "description": "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.", "facts": [ "rank #1195 of 1349", "API key auth", "0 desk reviews" ], "h1": "TrackingMore", "image": "https://www.anchorterminal.com/assets/og/tools-trackingmore.png", "path": "/tools/trackingmore", "published": "2026-10-01", "section": "tools", "title": "TrackingMore review (2026): pricing, alternatives and grade E", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/trackingmore" }, "tokens": { "markdown": 8700, "slim": 1880 }, "version": 1 }