{ "data": { "a": { "slug": "envia", "name": "Envia", "vendor": "Envia Shipping", "vendorUrl": "https://envia.com", "kind": "http-api", "category": "shipping", "summary": "Envia is a multi-carrier shipping platform, strongest in Latin America, with REST APIs for rates, labels, tracking, pickups, commercial invoices and address data. An official stdio MCP server exposes ten of those operations to agents.", "url": "https://www.anchorterminal.com/tools/envia", "markdownUrl": "https://www.anchorterminal.com/tools/envia.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/envia.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/envia.json", "dns": "envia.grade.anchorterminal.com", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@envia/envia-mcp" } ], "auth": "api-key", "authNotes": "Bearer API tokens created in the dashboard under `Desarrolladores \u003e Acceso de API`, one environment each: sandbox tokens work only against api-test.envia.com and production tokens only against api.envia.com. Several tokens can exist and each can be deleted to revoke it. No scopes were found. The MCP server reads the token from `ENVIA_API_KEY` and defaults to sandbox.", "pricing": "usage", "pricingNotes": "Prepaid balance: labels, notifications, insurance and add-ons draw on money added to the Envia account, and each price is shown when quoting. There is no public price list; volume plans go through sales. A free sandbox account returns simulated rates and creates test labels with no charges.", "priceSummary": "Pay per use", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the MCP package or the pricing page (checked 2026-11-06). Charges come from a prepaid balance.", "endpoints": [] }, "toolCount": 10, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.envia.com/docs/getting-started", "llmsTxt": "https://docs.envia.com/llms.txt", "openapi": "https://docs.envia.com/reference/shipping-rates.md", "capabilities": [ "shipping.rates", "shipping.labels", "shipping.tracking", "shipping.address-validation" ], "tags": [ "official", "hosted", "mcp", "llms-txt", "openapi", "sandbox", "prepaid", "webhooks", "latam", "typescript" ], "lastRelease": "2026-03-06", "graded": true, "anchor": { "graded": true, "score": 36.5, "grade": "F", "agentReady": false, "rank": 1362, "ranked": true, "rankOf": 1486, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 53, "maintenance": 10, "payments": 20, "reliability": 20, "schema": 80, "security": 35, "transparency": 16 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-06" }, "negative": 0, "verdict": "Envia's shipping APIs are documented for agents, with llms.txt, OpenAPI definitions on every reference page, a free sandbox and a compact ten-tool MCP server that defaults to test mode. No status page, rate limits, public price list or readable terms were found, and the MCP package has had one release.", "bestFor": "Shops and platforms shipping in Mexico and Latin America that want rates and labels from many local carriers.", "strengths": [ "Free sandbox with simulated rates and test labels, kept apart from production by separate tokens", "OpenAPI definitions embedded in every reference page, plus llms.txt and Markdown docs", "Ten MCP tools that default to the sandbox environment", "Labels cancelled before the first carrier scan are refunded to the balance automatically", "Postal code and address-structure lookups work without a token" ], "weaknesses": [ "No status page or rate limits found", "No public price list; costs appear only when quoting", "Terms and privacy text could not be read, and no legal entity was found", "MCP tools carry no readOnly or destructive annotations, and the package has one release, 0.1.0", "The docs changelog stops at March 2026" ], "agentNotes": [ "Leave `ENVIA_ENVIRONMENT` unset until the user confirms live shipping; the default is sandbox", "Ask the user before `envia_create_label` in production, since it spends the account balance", "Validate the postal code at geocodes.envia.com before quoting to avoid no-coverage errors", "Cancel an unwanted label before the carrier scans it to get the automatic refund", "Use a sandbox token with sandbox hosts and a production token with production hosts; they are not interchangeable" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 36.5 } ], "editorialScores": { "ergonomics": 53, "maintenance": 10, "payments": 20, "reliability": 20, "schema": 80, "security": 35, "transparency": 0 }, "provenanceScore": 32, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y @envia/envia-mcp@latest", "config": { "mcpServers": { "envia": { "args": [ "-y", "@envia/envia-mcp@latest" ], "command": "npx", "env": { "ENVIA_API_KEY": "your_api_key_here" } } } } }, "letme": { "capability": "https://letme.dev/shipping.rates", "tool": "https://letme.dev/envia" }, "area": "business", "provenance": { "legalEntity": "", "domain": "envia.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "", "privacy": "https://envia.com/en-US/legal/privacy-policy?n=privacy_policy", "statusPage": "", "changelog": "https://docs.envia.com/docs/changelog", "securityTxt": "unknown", "checked": "2026-11-06", "notes": [ "envia.com/robots.txt allows all but language-change paths; docs.envia.com disallows edit, login and api-next paths and links llms.txt.", "The privacy policy page renders only a heading without script, and every terms URL tried answered 500, so neither text was read.", "status.envia.com did not connect and no status page is linked. security.txt was not checked." ], "score": 32 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/envia.json", "live": { "slug": "envia", "versions": [ { "registry": "npm", "name": "@envia/envia-mcp", "version": "0.1.0", "seenAt": "2026-11-06T23:24:27.893485506Z" } ], "npmWeekly": 81, "securityTxt": { "url": "https://envia.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-07T16:01:23.154161694Z" }, "llmsTxt": { "url": "https://docs.envia.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:25.501362093Z" }, "pages": [ { "url": "https://docs.envia.com/docs/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:16.542743112Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b3c01b7da2e7" }, { "url": "https://envia.com/en-US/legal/privacy-policy?n=privacy_policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:09:20.480053366Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "52e5d34d2a62" } ], "updatedAt": "2026-11-07T16:01:23.154161694Z" } }, "answer": "TrackingMore scores 41.8 (E) on agent readiness against Envia's 36.5 (F), and leads in 5 of 7 scored categories. Envia leads on schema \u0026 documentation.", "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": 1276, "ranked": true, "rankOf": 1486, "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-07T18:21:01.372962258Z", "lastOk": true, "lastStatus": 404, "lastMs": 937, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 535, "p95ms24h": 888, "samples24h": 239, "samples30d": 700, "days": [ { "date": "2026-11-04", "probes": 87, "ok": 87 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://status.trackingmore.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:53.362114985Z" }, "versions": [ { "registry": "github", "name": "TrackingMore-API/trackingmore-sdk-nodejs", "version": "v1.0.8", "released": "2023-11-21", "seenAt": "2026-11-07T00:12:36.024640104Z" }, { "registry": "npm", "name": "trackingmore-sdk-nodejs", "version": "1.0.8", "seenAt": "2026-11-07T00:12:35.079927349Z" }, { "registry": "pypi", "name": "trackingmore-sdk-python", "version": "0.1.4", "released": "2023-11-21", "seenAt": "2026-11-07T00:12:35.842690047Z" } ], "githubStars": 6, "npmWeekly": 509, "pypiWeekly": 23, "securityTxt": { "url": "https://trackingmore.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:55.733989579Z" }, "pages": [ { "url": "https://www.trackingmore.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:35:53.062301094Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b472ec5f3e98" }, { "url": "https://www.cwill.com/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:27:38.652867353Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "d15851c40f83" }, { "url": "https://www.cwill.com/terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:27:41.59812166Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "860f0aa21b4c" } ], "updatedAt": "2026-11-07T18:21:01.372962258Z" } }, "edges": [ { "by": 49, "category": "schema", "leads": "envia", "name": "Schema \u0026 documentation", "reasons": { "a": "Each reference page's Markdown copy embeds an OpenAPI definition with sandbox and production servers (25). llms.txt and a Markdown copy of each page (10). Endpoint descriptions say what each is for and which call comes next in the workflow, and the rate tool warns that sandbox rates are simulated (15 of 20). The quote definition has 17 enums and required lists (11 of 15). Workflow examples and an error-formats guide named in the changelog, though its Markdown address answered 404 and the quote definition documents only 200 (9 of 15). A dated docs changelog by month, the latest March 2026 (10 of 15). 25 + 10 + 15 + 11 + 9 + 10 = 80.", "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": 80, "b": 31 } }, { "by": 45, "category": "reliability", "leads": "trackingmore", "name": "Reliability", "reasons": { "a": "Graded as a hosted service on Envia's REST APIs, with the local MCP server noted. No status page is linked and status.envia.com did not connect (0). No readable incident history (5). No rate limits found in the docs index, FAQs, integration guide or production checklist (0). The production checklist asks for 5xx retry logic and webhook deduplication, with no 429 or idempotency guidance for label creation (5 of 15). No SLA found (0). Neither the APIs nor the MCP server is labelled beta (10). 0 + 5 + 0 + 5 + 0 + 10 = 20.", "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": 20, "b": 65 } }, { "by": 41, "category": "transparency", "leads": "trackingmore", "name": "Transparency \u0026 trust", "reasons": { "a": "Every terms URL tried answered 500 and the privacy policy is drawn by script, so no terms, entity or data-handling statement was read (0 of 30, 0 of 30). No deprecation policy or dated notices (0). No subprocessors or data locations found (0). 0 + 0 + 0 + 0 = 0, as unread rather than absent where the pages exist.", "b": "Closed service. The terms are the CWILL group's (effective 9 January 2026), which say the contracting entity depends on the product, and the privacy policy names CHANNELWILL CO., LIMITED for TrackingMore. The SDKs are MIT (15 of 30). The privacy policy (8 August 2026) distinguishes controller and processor roles and links a DPA and a sub-processor list, neither read; no retention periods were read (12 of 30). v2 and v3 are still served with no notice policy or dates (4 of 20). A sub-processor list exists at trust.cwill.com and was not read; no data location is stated on the pages read (8 of 20). 15 + 12 + 4 + 8 = 39." }, "scores": { "a": 16, "b": 57 } }, { "by": 9, "category": "maintenance", "leads": "trackingmore", "name": "Maintenance \u0026 community", "reasons": { "a": "The latest dated change found is the docs changelog for March 2026 and @envia/envia-mcp 0.1.0 on 4 March 2026, more than 180 days ago; doc pages show later `updatedAt` stamps (28 October for the FAQ) that record no change (0). No dated entries in the 90 days from 8 August (0). Support through the dashboard and docs, with no public tracker; the MCP repository named on npm could not be cloned (5 of 15). The MCP package is official, with no API SDK and no registry entry (5 of 15). No public CI to read (0). 0 + 0 + 5 + 5 + 0 = 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": 10, "b": 19 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Envia Shipping", "b": "CHANNELWILL CO., LIMITED", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.trackingmore.com/v4", "name": "Hosted endpoint" }, { "a": "stdio", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "not published", "b": "$0.03 per transaction", "name": "Price for shipment tracking" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT", "name": "Licence" }, { "a": "10", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-03-06", "b": "2024-12-25", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-08-08", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "6 stars", "name": "Popularity" } ], "faq": [ { "answer": "TrackingMore scores 41.8 (E) on agent readiness against Envia's 36.5 (F), and leads in 5 of 7 scored categories. Envia leads on schema \u0026 documentation.", "question": "Which is better for AI agents, Envia or TrackingMore?" }, { "answer": "Both need an API key.", "question": "Do Envia and TrackingMore need an API key?" }, { "answer": "Envia runs on your own machine, with no hosted endpoint listed. TrackingMore has a hosted endpoint at https://api.trackingmore.com/v4.", "question": "Can an agent call Envia and TrackingMore without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 80 against 31" ], "also": [ "Runs on your own machine" ], "goodFor": "Shops and platforms shipping in Mexico and Latin America that want rates and labels from many local carriers.", "slug": "envia", "watchFor": "No status page or rate limits found" }, { "aheadOn": [ "Reliability, 65 against 20", "Maintenance \u0026 community, 19 against 10", "Transparency \u0026 trust, 57 against 16" ], "also": [ "A hosted endpoint, with nothing to install" ], "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": null, "job": { "capability": "shipping.tracking", "name": "Shipment tracking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/atoship-vs-envia.json", "title": "atoship vs Envia", "url": "https://www.anchorterminal.com/compare/atoship-vs-envia" }, { "json": "https://www.anchorterminal.com/compare/easypost-vs-envia.json", "title": "EasyPost vs Envia", "url": "https://www.anchorterminal.com/compare/easypost-vs-envia" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-envia.json", "title": "Easyship vs Envia", "url": "https://www.anchorterminal.com/compare/easyship-vs-envia" }, { "json": "https://www.anchorterminal.com/compare/envia-vs-karrio.json", "title": "Envia vs Karrio", "url": "https://www.anchorterminal.com/compare/envia-vs-karrio" }, { "json": "https://www.anchorterminal.com/compare/envia-vs-sendcloud.json", "title": "Envia vs Sendcloud", "url": "https://www.anchorterminal.com/compare/envia-vs-sendcloud" }, { "json": "https://www.anchorterminal.com/compare/envia-vs-shipbob.json", "title": "Envia vs ShipBob", "url": "https://www.anchorterminal.com/compare/envia-vs-shipbob" }, { "json": "https://www.anchorterminal.com/compare/envia-vs-shippo.json", "title": "Envia vs Shippo", "url": "https://www.anchorterminal.com/compare/envia-vs-shippo" }, { "json": "https://www.anchorterminal.com/compare/envia-vs-shippypro.json", "title": "Envia vs ShippyPro", "url": "https://www.anchorterminal.com/compare/envia-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/envia-vs-shipstation.json", "title": "Envia vs ShipStation API", "url": "https://www.anchorterminal.com/compare/envia-vs-shipstation" }, { "json": "https://www.anchorterminal.com/compare/atoship-vs-trackingmore.json", "title": "atoship vs TrackingMore", "url": "https://www.anchorterminal.com/compare/atoship-vs-trackingmore" }, { "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/envia-vs-ship24.json", "title": "Envia vs Ship24", "url": "https://www.anchorterminal.com/compare/envia-vs-ship24" }, { "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-trackingmore.json", "title": "Ship24 vs TrackingMore", "url": "https://www.anchorterminal.com/compare/ship24-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shipbob-vs-trackingmore.json", "title": "ShipBob vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shipbob-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore.json", "title": "Shippo vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.json", "title": "ShippyPro vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shippypro-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/shipstation-vs-trackingmore.json", "title": "ShipStation API vs TrackingMore", "url": "https://www.anchorterminal.com/compare/shipstation-vs-trackingmore" } ], "panel": null, "scores": [ { "by": 45, "edge": "trackingmore", "envia": 20, "key": "reliability", "name": "Reliability", "trackingmore": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 49, "edge": "envia", "envia": 80, "key": "schema", "name": "Schema \u0026 documentation", "trackingmore": 31, "weight": 13 }, { "by": 1, "edge": "trackingmore", "envia": 53, "key": "ergonomics", "name": "Agent ergonomics", "trackingmore": 54, "weight": 13 }, { "by": 4, "edge": "envia", "envia": 35, "key": "security", "name": "Security \u0026 auth", "trackingmore": 31, "weight": 14 }, { "by": 3, "edge": "trackingmore", "envia": 20, "key": "payments", "name": "Payments \u0026 pricing", "trackingmore": 23, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 9, "edge": "trackingmore", "envia": 10, "key": "maintenance", "name": "Maintenance \u0026 community", "trackingmore": 19, "weight": 7 }, { "by": 41, "edge": "trackingmore", "envia": 16, "key": "transparency", "name": "Transparency \u0026 trust", "trackingmore": 57, "weight": 7 } ], "summary": "TrackingMore scores 41.8 (E) on agent readiness against Envia's 36.5 (F), and leads in 5 of 7 scored categories. Envia leads on schema \u0026 documentation. Both do shipment tracking.", "tasks": null, "tutorials": [], "verdicts": { "envia": "Envia's shipping APIs are documented for agents, with llms.txt, OpenAPI definitions on every reference page, a free sandbox and a compact ten-tool MCP server that defaults to test mode. No status page, rate limits, public price list or readable terms were found, and the MCP package has had one release.", "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/envia-vs-trackingmore", "json": "https://www.anchorterminal.com/compare/envia-vs-trackingmore.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/envia-vs-trackingmore.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/envia-vs-trackingmore.min.md" }, "markdown": "TrackingMore scores 41.8 (E) on agent readiness against Envia's 36.5 (F), and leads in 5 of 7 scored categories. Envia leads on schema \u0026 documentation. Both do shipment tracking.\n\n- Envia: grade F, 36.5/100, rank #1362 of 1486. Markdown https://www.anchorterminal.com/tools/envia.md · JSON https://www.anchorterminal.com/api/v1/tools/envia.json\n- TrackingMore: grade E, 41.8/100, rank #1276 of 1486. 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 66 shipping comparisons: https://www.anchorterminal.com/compare/shipping/index.md\n\n## Which one, for what\n\n### Envia (F)\n\nGood for: Shops and platforms shipping in Mexico and Latin America that want rates and labels from many local carriers.\n\nAhead on:\n- Schema \u0026 documentation, 80 against 31\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: No status page or rate limits found\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- Reliability, 65 against 20\n- Maintenance \u0026 community, 19 against 10\n- Transparency \u0026 trust, 57 against 16\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\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: Envia +49\n\n- Envia (80): Each reference page's Markdown copy embeds an OpenAPI definition with sandbox and production servers (25). llms.txt and a Markdown copy of each page (10). Endpoint descriptions say what each is for and which call comes next in the workflow, and the rate tool warns that sandbox rates are simulated (15 of 20). The quote definition has 17 enums and required lists (11 of 15). Workflow examples and an error-formats guide named in the changelog, though its Markdown address answered 404 and the quote definition documents only 200 (9 of 15). A dated docs changelog by month, the latest March 2026 (10 of 15). 25 + 10 + 15 + 11 + 9 + 10 = 80.\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### Reliability: TrackingMore +45\n\n- Envia (20): Graded as a hosted service on Envia's REST APIs, with the local MCP server noted. No status page is linked and status.envia.com did not connect (0). No readable incident history (5). No rate limits found in the docs index, FAQs, integration guide or production checklist (0). The production checklist asks for 5xx retry logic and webhook deduplication, with no 429 or idempotency guidance for label creation (5 of 15). No SLA found (0). Neither the APIs nor the MCP server is labelled beta (10). 0 + 5 + 0 + 5 + 0 + 10 = 20.\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### Transparency \u0026 trust: TrackingMore +41\n\n- Envia (16): Every terms URL tried answered 500 and the privacy policy is drawn by script, so no terms, entity or data-handling statement was read (0 of 30, 0 of 30). No deprecation policy or dated notices (0). No subprocessors or data locations found (0). 0 + 0 + 0 + 0 = 0, as unread rather than absent where the pages exist.\n- TrackingMore (57): Closed service. The terms are the CWILL group's (effective 9 January 2026), which say the contracting entity depends on the product, and the privacy policy names CHANNELWILL CO., LIMITED for TrackingMore. The SDKs are MIT (15 of 30). The privacy policy (8 August 2026) distinguishes controller and processor roles and links a DPA and a sub-processor list, neither read; no retention periods were read (12 of 30). v2 and v3 are still served with no notice policy or dates (4 of 20). A sub-processor list exists at trust.cwill.com and was not read; no data location is stated on the pages read (8 of 20). 15 + 12 + 4 + 8 = 39.\n\n### Maintenance \u0026 community: TrackingMore +9\n\n- Envia (10): The latest dated change found is the docs changelog for March 2026 and @envia/envia-mcp 0.1.0 on 4 March 2026, more than 180 days ago; doc pages show later `updatedAt` stamps (28 October for the FAQ) that record no change (0). No dated entries in the 90 days from 8 August (0). Support through the dashboard and docs, with no public tracker; the MCP repository named on npm could not be cloned (5 of 15). The MCP package is official, with no API SDK and no registry entry (5 of 15). No public CI to read (0). 0 + 0 + 5 + 5 + 0 = 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## Score by category\n\n| Category | Weight | Envia | TrackingMore | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 65 | TrackingMore +45 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 31 | Envia +49 |\n| Agent ergonomics | 13% (16.2 this run) | 53 | 54 | TrackingMore +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 35 | 31 | Envia +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 23 | TrackingMore +3 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 10 | 19 | TrackingMore +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 16 | 57 | TrackingMore +41 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **36.5 · F** | **41.8 · E** | |\n\n## Facts side by side\n\n| Fact | Envia | TrackingMore |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Envia Shipping | CHANNELWILL CO., LIMITED |\n| Hosted endpoint | no (local only) | `https://api.trackingmore.com/v4` |\n| Transports | stdio | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\n| Price for shipment tracking | not published | $0.03 per transaction |\n| x402 | no | no |\n| Licence | none | Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT |\n| Tools exposed | 10 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| Last release | 2026-03-06 | 2024-12-25 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no date given | 2026-08-08 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | yes |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | none | 6 stars |\n\n## Verdicts\n\n**Envia.** Envia's shipping APIs are documented for agents, with llms.txt, OpenAPI definitions on every reference page, a free sandbox and a compact ten-tool MCP server that defaults to test mode. No status page, rate limits, public price list or readable terms were found, and the MCP package has had one release.\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### Envia\n\n1. Leave `ENVIA_ENVIRONMENT` unset until the user confirms live shipping; the default is sandbox\n2. Ask the user before `envia_create_label` in production, since it spends the account balance\n3. Validate the postal code at geocodes.envia.com before quoting to avoid no-coverage errors\n4. Cancel an unwanted label before the carrier scans it to get the automatic refund\n5. Use a sandbox token with sandbox hosts and a production token with production hosts; they are not interchangeable\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, Envia or TrackingMore?\n\nTrackingMore scores 41.8 (E) on agent readiness against Envia's 36.5 (F), and leads in 5 of 7 scored categories. Envia leads on schema \u0026 documentation.\n\n### Do Envia and TrackingMore need an API key?\n\nBoth need an API key.\n\n### Can an agent call Envia and TrackingMore without installing anything?\n\nEnvia runs on your own machine, with no hosted endpoint listed. TrackingMore has a hosted endpoint at https://api.trackingmore.com/v4.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/envia-vs-trackingmore.json, and with the fewest tokens: https://www.anchorterminal.com/compare/envia-vs-trackingmore.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"envia\", \"b\": \"trackingmore\"}`. From a terminal: `anchor compare envia trackingmore`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/envia.json and https://www.anchorterminal.com/api/v1/tools/trackingmore.json\n\n## Other comparisons with Envia or TrackingMore\n\n- [atoship vs Envia](https://www.anchorterminal.com/compare/atoship-vs-envia.md)\n- [EasyPost vs Envia](https://www.anchorterminal.com/compare/easypost-vs-envia.md)\n- [Easyship vs Envia](https://www.anchorterminal.com/compare/easyship-vs-envia.md)\n- [Envia vs Karrio](https://www.anchorterminal.com/compare/envia-vs-karrio.md)\n- [Envia vs Sendcloud](https://www.anchorterminal.com/compare/envia-vs-sendcloud.md)\n- [Envia vs ShipBob](https://www.anchorterminal.com/compare/envia-vs-shipbob.md)\n- [Envia vs Shippo](https://www.anchorterminal.com/compare/envia-vs-shippo.md)\n- [Envia vs ShippyPro](https://www.anchorterminal.com/compare/envia-vs-shippypro.md)\n- [Envia vs ShipStation API](https://www.anchorterminal.com/compare/envia-vs-shipstation.md)\n- [atoship vs TrackingMore](https://www.anchorterminal.com/compare/atoship-vs-trackingmore.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- [Envia vs Ship24](https://www.anchorterminal.com/compare/envia-vs-ship24.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 TrackingMore](https://www.anchorterminal.com/compare/ship24-vs-trackingmore.md)\n- [ShipBob vs TrackingMore](https://www.anchorterminal.com/compare/shipbob-vs-trackingmore.md)\n- [Shippo vs TrackingMore](https://www.anchorterminal.com/compare/shippo-vs-trackingmore.md)\n- [ShippyPro vs TrackingMore](https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.md)\n- [ShipStation API vs TrackingMore](https://www.anchorterminal.com/compare/shipstation-vs-trackingmore.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "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": "Envia vs TrackingMore", "url": "" } ], "description": "TrackingMore scores 41.8 (E) to Envia's 36.5 (F) for shipment tracking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Envia F 36.5", "TrackingMore E 41.8", "scores" ], "h1": "Envia vs TrackingMore", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/envia-vs-trackingmore", "published": "2026-10-01", "section": "tools", "title": "Envia vs TrackingMore for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/envia-vs-trackingmore" }, "tokens": { "markdown": 3600, "slim": 1980 }, "version": 1 }