{ "data": { "a": { "slug": "shippo", "name": "Shippo", "vendor": "Shippo", "vendorUrl": "https://goshippo.com", "kind": "http-api", "category": "shipping", "summary": "Multi-carrier shipping API from Shippo. It quotes rates, buys labels, validates addresses, tracks parcels and creates return labels across the carriers it connects, through a REST API, official SDKs and a hosted MCP server.", "url": "https://www.anchorterminal.com/tools/shippo", "markdownUrl": "https://www.anchorterminal.com/tools/shippo.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/shippo.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/shippo.json", "dns": "shippo.grade.anchorterminal.com", "repo": "https://github.com/goshippo/ai", "license": "Proprietary service under Shippo's terms of use. The SDKs and the goshippo/ai repository (skills and MCP bridge) are MIT", "transports": [ "http" ], "remoteUrl": "https://api.goshippo.com", "packages": [ { "registry": "npm", "name": "shippo" }, { "registry": "pypi", "name": "shippo" }, { "registry": "npm", "name": "@shippo/shippo-mcp" } ], "auth": "mixed", "authNotes": "Self-serve API key. A person signs up at apps.goshippo.com/join and creates live (shippo_live_) and test (shippo_test_) keys in the API portal, with no review. Calls send `Authorization: ShippoToken \u003ckey\u003e`. Keys are shown once, can be deleted and replaced, and have no scopes. The hosted MCP server at mcp.shippo.com uses per-user OAuth against the live account, with one scope (\"*\"). OAuth credentials for a platform acting for other Shippo accounts come from the sales team. Client-side apps can use a 12-hour JWT from POST /embedded/authz.", "pricing": "freemium", "pricingNotes": "API Starter has no monthly fee. The first 30 labels a month are free, then 7 cents a label, on top of postage. Calls not tied to a Shippo label are charged per unit (see the price table). API Premier is custom, with volume discounts, through sales. Test mode is free with a test key, so an agent can start without a contract, and billing details are needed for live labels (https://goshippo.com/pricing/api).", "priceSummary": "$0.07 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI spec or the pricing page (checked 2026-10-07).", "endpoints": [] }, "toolCount": 4, "popularity": { "githubStars": 3, "npmWeekly": 73114, "pypiWeekly": 20036, "asOf": "2026-10-07" }, "docsUrl": "https://docs.goshippo.com", "llmsTxt": "https://docs.goshippo.com/llms.txt", "openapi": "https://docs.goshippo.com/spec/shippoapi/public-api.yaml", "registryName": "com.shippo/shippo-mcp", "capabilities": [ "shipping.rates", "shipping.labels", "shipping.tracking", "shipping.address-validation", "shipping.returns" ], "tags": [ "hosted", "freemium", "free-tier", "api-key", "oauth", "mcp", "openapi", "llms-txt", "python", "typescript", "java", "webhooks", "sandbox", "status-page" ], "lastRelease": "2026-10-27", "graded": true, "anchor": { "graded": true, "score": 61.9, "grade": "C", "agentReady": false, "rank": 526, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 77, "payments": 40, "reliability": 69, "schema": 83, "security": 42, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "Per-label and per-call prices are public, test keys are self-serve, and the OpenAPI spec, llms.txt and Markdown docs are open to a fetch. Label purchase has no idempotency key, API keys carry no scopes, and the status page logged carrier-side incidents on most days from August to October 2026.", "bestFor": "An agent that quotes and buys parcel labels across USPS, UPS, FedEx and DHL Express for a small or mid-size shipper, with a free test mode and public unit prices.", "strengths": [ "Public prices per unit, 7 cents a label after 30 free a month, 1 cent a rate request and 2 cents a tracking request", "Test keys (shippo_test_) create free test labels and mock tracking, with data kept apart from live", "OpenAPI 3.1 spec with 71 operations, plus llms.txt and a Markdown copy of each docs page", "Hosted MCP server at mcp.shippo.com with four tools, reads and writes split so a client can require approval for writes", "Rate limits published per endpoint, with separate live and test figures", "Dated release notes gave a month's notice of the EU product identifier requirement of 1 November 2026, with warnings in responses before enforcement" ], "weaknesses": [ "No idempotency key on label purchase or other writes. Only the Reporting API accepts one", "API keys have no scopes or read-only mode, and the OAuth flow has one scope, \"*\"", "The hosted MCP server runs on the live account only, with no test mode", "Carrier-side incidents on the status page on most days from August to October 2026, many marked major or critical", "Terms of use and privacy notice load only with JavaScript, and no SLA or subprocessor list was found", "The Python SDK's latest stable tag is 3.9.0 from 26 November 2024. 5.0.0 has been in beta since 22 October 2026", "No security.txt, and the disclosure page named in Shippo's own security policy returns 404" ], "agentNotes": [ "Build and test with a shippo_test_ key. Test and live object IDs are separate, and the hosted MCP server has no test mode", "Send `Authorization: ShippoToken \u003ckey\u003e`, not Bearer, and pin `Shippo-API-Version: 2018-02-08`", "Before retrying a failed POST /transactions, list recent transactions. There is no idempotency key, and a second purchase is a second charge", "Pass `async: false` on shipments and transactions, or poll the object until its status leaves QUEUED", "Set `results` on list calls (under 200). Defaults vary by resource, and list calls are limited to 50 a minute on live keys" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 61.9 } ], "editorialScores": { "ergonomics": 64, "maintenance": 77, "payments": 40, "reliability": 69, "schema": 83, "security": 42, "transparency": 31 }, "provenanceScore": 85, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install shippo", "http": "curl https://api.goshippo.com/shipments/ \\\n -H \"Authorization: ShippoToken \u003cAPI_TOKEN\u003e\" \\\n -H \"Content-Type: application/json\" \\\n -d '{...}'", "claudeCode": "claude mcp add --transport http shippo https://mcp.shippo.com", "config": { "mcpServers": { "shippo": { "url": "https://mcp.shippo.com" } } } }, "letme": { "capability": "https://letme.dev/shipping.rates", "tool": "https://letme.dev/shippo" }, "area": "business", "unitPrices": [ { "item": "Label, API Starter, after 30 free a month, plus postage", "unit": "tx", "usd": 0.07 }, { "item": "Rate request not tied to a Shippo label", "unit": "call", "usd": 0.01 }, { "item": "Tracking request not tied to a Shippo label", "unit": "call", "usd": 0.02 }, { "item": "Delivery date estimate", "unit": "call", "usd": 0.03 }, { "item": "US address validation", "unit": "call", "usd": 0.02 }, { "item": "Non-US address validation", "unit": "call", "usd": 0.08 } ], "provenance": { "legalEntity": "Shippo", "domain": "goshippo.com", "domainRegistered": "2013-09-21", "endpointOnVendorDomain": true, "terms": "https://privacy.goshippo.com/policies?name=terms-of-use", "privacy": "https://privacy.goshippo.com/policies?name=privacy-notice", "statusPage": "https://status.goshippo.com", "changelog": "https://docs.goshippo.com/api-concepts/api-change-log", "securityTxt": "none", "checked": "2026-11-02", "notes": [ "The registered legal entity wasn't confirmed. goshippo.com/terms and /privacy redirect to a privacy centre that returns no policy text without JavaScript. The SDK licences name \"Shippo\" as copyright holder.", "RDAP for goshippo.com gives a registration date of 2013-09-21.", "The API answers at api.goshippo.com and the MCP server at mcp.shippo.com, whose OAuth metadata names https://goshippo.com as the authorisation server.", "goshippo.com/.well-known/security.txt and goshippo.com/security both return 404. The AI repository's SECURITY.md gives security@goshippo.com.", "trust.goshippo.com answers robots.txt with 403 AccessDenied and privacy.goshippo.com with its app page, so neither was read on 2 November 2026." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/shippo.json", "live": { "slug": "shippo", "probe": { "target": "https://api.goshippo.com", "method": "get", "lastAt": "2026-11-04T20:47:14.472010346Z", "lastOk": true, "lastStatus": 401, "lastMs": 144, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 148, "p95ms24h": 412, "samples24h": 246, "samples30d": 6818, "days": [ { "date": "2026-10-08", "probes": 93, "ok": 93 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 214, "ok": 214 } ] }, "vendorStatus": { "page": "https://status.goshippo.com", "indicator": "maintenance", "summary": "Service Under Maintenance", "checkedAt": "2026-11-04T20:39:56.121718729Z" }, "versions": [ { "registry": "github", "name": "goshippo/ai", "version": "v1.5.4", "released": "2026-07-23", "seenAt": "2026-11-03T20:57:33.164979487Z" }, { "registry": "mcp-registry", "name": "com.shippo/shippo-mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" }, { "registry": "npm", "name": "@shippo/shippo-mcp", "version": "3.0.4", "seenAt": "2026-11-03T20:57:32.022248779Z" }, { "registry": "npm", "name": "shippo", "version": "2.19.1", "seenAt": "2026-11-03T20:57:30.969681454Z" }, { "registry": "pypi", "name": "shippo", "version": "3.9.0", "released": "2024-11-26", "seenAt": "2026-11-03T20:57:31.836463719Z" } ], "githubStars": 3, "npmWeekly": 86060, "pypiWeekly": 24516, "securityTxt": { "url": "https://goshippo.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:37.848765063Z" }, "llmsTxt": { "url": "https://docs.goshippo.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-04T15:24:12.785171566Z" }, "domain": { "domain": "goshippo.com", "registered": "2013-09-21", "source": "https://rdap.verisign.com/com/v1/domain/goshippo.com", "checkedAt": "2026-11-01T14:23:37.391892924Z" }, "pages": [ { "url": "https://docs.goshippo.com/api-concepts/api-change-log", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-04T08:21:10.265248924Z", "changedAt": "2026-10-27T03:44:17.007984027Z", "fingerprint": "222f45f8f94b" }, { "url": "https://goshippo.com/pricing/api", "kind": "pricing", "status": 200, "checkedAt": "2026-11-04T08:24:36.268445967Z", "changedAt": "2026-11-03T07:50:52.570035252Z", "fingerprint": "63a2e0a9d7e4" }, { "url": "https://privacy.goshippo.com/policies?name=privacy-notice", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:30:38.381340812Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" }, { "url": "https://privacy.goshippo.com/policies?name=terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:30:40.782102537Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e3b0c44298fc" } ], "github": { "repo": "goshippo/ai", "checkedAt": "2026-11-02T08:52:34.500876974Z", "stars": 3, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-09T14:55:41Z", "openIssues": 0, "openPRs": 7, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "main", "runs": 48, "success": 46, "failure": 1, "other": 1, "latest": "success", "latestAt": "2026-07-24T02:06:16Z" } }, "updatedAt": "2026-11-04T20:47:14.472010346Z" } }, "answer": "Shippo scores 61.9 (C) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category.", "b": { "slug": "trackingmore", "name": "TrackingMore", "vendor": "CHANNELWILL CO., LIMITED", "vendorUrl": "https://www.trackingmore.com", "kind": "http-api", "category": "shipping", "summary": "TrackingMore is a multi-carrier parcel tracking service run by CHANNELWILL CO., LIMITED under the CWILL brand. Its REST API v4 detects couriers, creates and reads trackings, retracks expired ones and tracks air waybills, with webhooks for status changes.", "url": "https://www.anchorterminal.com/tools/trackingmore", "markdownUrl": "https://www.anchorterminal.com/tools/trackingmore.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/trackingmore.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/trackingmore.json", "dns": "trackingmore.grade.anchorterminal.com", "repo": "https://github.com/TrackingMore-API/trackingmore-sdk-nodejs", "license": "Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.trackingmore.com/v4", "packages": [ { "registry": "npm", "name": "trackingmore-sdk-nodejs" }, { "registry": "pypi", "name": "trackingmore-sdk-python" }, { "registry": "go", "name": "github.com/TrackingMore-API/trackingmore-sdk-go" } ], "auth": "api-key", "authNotes": "An API key sent in the Tracking-Api-Key header, generated in the web app under Developer, API key, and shown once. At most four keys per account, deleted from the same page. Every key has full account access and no scopes were found. Access is self-serve after a browser signup; the pricing page gives two keys on Basic, five on Pro and eight on Enterprise.", "pricing": "freemium", "pricingNotes": "Plans are priced in credits a month with a Free plan, Basic, Pro and a custom Enterprise plan, and a 14-day free trial. The plan prices on the pricing page render by script and were not read; the API page says tracking starts from $0.03 a tracked order and shows figures of $0.0318, $0.036 and $0.037. SMS notifications and translation cost extra credits. Enterprise adds custom rate limits and invoice payment (https://www.trackingmore.com/pricing and https://www.trackingmore.com/tracking-api, checked 2026-11-03).", "priceSummary": "$0.03 / tx", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the SDK READMEs, the support centre or the pricing page (checked 2026-11-03). Plans are paid by card in the web app, or by invoice on Enterprise.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://www.trackingmore.com/docs/trackingmore/", "capabilities": [ "shipping.tracking" ], "tags": [ "official", "hosted", "closed-source", "api-key", "webhooks", "free-tier", "free-trial", "freemium", "status-page", "python", "typescript", "go", "java", "php", "ruby", "dotnet" ], "lastRelease": "2024-12-25", "graded": true, "anchor": { "graded": true, "score": 41.8, "grade": "E", "agentReady": false, "rank": 1187, "ranked": true, "rankOf": 1349, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 54, "maintenance": 19, "payments": 23, "reliability": 65, "schema": 31, "security": 31, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "A small tracking API with published per-endpoint rate limits, meta error codes, a free courier detection call and SDKs in seven languages. The reference docs render by script with no OpenAPI file, plan prices weren't readable, one key has full access, the SDKs date from 2024 and the legal documents belong to the CWILL group.", "bestFor": "An agent that reports where a parcel is across many carriers from a tracking number, with a cheap per-tracking price.", "strengths": [ "Nine v4 calls cover detect, create, batch create of 40, get, update, delete, retrack and air waybills, with webhooks for status changes", "Rate limits published per endpoint, 3 requests a second on create and 10 a second elsewhere, with a stated 120-second wait after a 429", "HTTP and meta codes with messages, including 4101 for a duplicate tracking, so a retried create is rejected rather than doubled", "Official SDKs in PHP, Python, Node, Java, Go, Ruby and .NET, MIT, plus a Postman collection", "Free plan and a 14-day trial, with courier detection free on v4" ], "weaknesses": [ "The API reference renders by script and no OpenAPI file, llms.txt or Markdown docs were found", "One API key with full access, at most four per account, no scopes and no read-only key", "No idempotency key, no Retry-After, and no SLA beyond a 99.99 per cent uptime line on the Enterprise plan", "The SDKs were last updated between February and December 2024, and no dated API changelog was found", "Plan prices render by script and were not read; the terms and privacy policy are CWILL group documents that name different entities per product" ], "agentNotes": [ "Send the key as `Tracking-Api-Key` to https://api.trackingmore.com/v4; the v2 header name `Trackingmore-Api-Key` and the v3 path are the older versions", "Call `POST /v4/couriers/detect` first when the carrier is unknown (free on v4), then `POST /v4/trackings/create` with `tracking_number` and `courier_code`; the create response already carries the tracking result", "Create up to 40 shipments at once with `POST /v4/trackings/batch` and read them with `GET /v4/trackings/get`, which filters by tracking numbers, courier and created date", "Treat meta code 4101 as an existing tracking rather than a failure, and 4190 as a plan quota to raise with the person; after a 429 wait 120 seconds", "Stay under 3 creates a second and 10 requests a second on other calls per account, and prefer a webhook (same version as the API) to polling" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 41.8 } ], "editorialScores": { "ergonomics": 54, "maintenance": 19, "payments": 23, "reliability": 65, "schema": 31, "security": 31, "transparency": 39 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install trackingmore-sdk-nodejs", "http": "curl -H \"Tracking-Api-Key: $TRACKINGMORE_API_KEY\" https://api.trackingmore.com/v4/couriers/all" }, "letme": { "capability": "https://letme.dev/shipping.tracking", "tool": "https://letme.dev/trackingmore" }, "area": "business", "unitPrices": [ { "item": "Tracked order", "unit": "tx", "usd": 0.03, "note": "the from price on the API page; plan prices render by script and were not read" } ], "provenance": { "legalEntity": "CHANNELWILL CO., LIMITED", "domain": "trackingmore.com", "domainRegistered": "2014-10-27", "endpointOnVendorDomain": true, "terms": "https://www.cwill.com/terms-of-service/", "privacy": "https://www.cwill.com/privacy-policy/", "statusPage": "https://status.trackingmore.com/", "changelog": "", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "trackingmore.com's legal links redirect to cwill.com. The CWILL privacy policy (effective 8 August 2026) names CHANNELWILL CO., LIMITED, Workspace B15, 2/F, Wing Cheung Industrial Building, 58-70 Kwai Cheong Road, Hong Kong, as data controller for TrackingMore, and CWILL INC of Dover, Delaware, for the CWILL Order Tracking and other products. The CWILL Terms of Service (effective 9 January 2026) cover the whole product family and say the contracting entity depends on the product.", "The CWILL terms refer to an Acceptable Use Policy and a DPA at cwill.com/legal/dpa/, and a sub-processor list at trust.cwill.com/subprocessors, none of which was read.", "www.trackingmore.com/robots.txt disallows nothing. support.trackingmore.com/robots.txt disallows nothing. www.cwill.com/robots.txt allows named AI crawlers and disallows search and admin paths for others, with a crawl delay of 5 seconds. status.trackingmore.com was read without a robots.txt check of its own.", "The API answers at api.trackingmore.com, a vendor subdomain.", "www.trackingmore.com/.well-known/security.txt returns 404, and no security page was found on trackingmore.com (the /security path returns 404).", "RDAP gives trackingmore.com a registration date of 27 October 2014." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/trackingmore.json", "live": { "slug": "trackingmore", "probe": { "target": "https://api.trackingmore.com/v4", "method": "get", "lastAt": "2026-11-04T20:47:20.612787952Z", "lastOk": true, "lastStatus": 404, "lastMs": 630, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 599, "p95ms24h": 1041, "samples24h": 55, "samples30d": 55, "days": [ { "date": "2026-11-04", "probes": 55, "ok": 55 } ] }, "vendorStatus": { "page": "https://status.trackingmore.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:39.655302878Z" }, "securityTxt": { "url": "https://trackingmore.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:27.177236947Z" }, "updatedAt": "2026-11-04T20:47:20.612787952Z" } }, "edges": [ { "by": 58, "category": "maintenance", "leads": "shippo", "name": "Maintenance \u0026 community", "reasons": { "a": "The API release notes were last updated on 20 October 2026, and the `shippo` npm SDK 2.19.1 was tagged on 27 October 2026 (30). Six dated entries from 4 August, the latest on 1, 8, 14 and 20 October, plus TypeScript SDK 2.19.0 and 2.19.1 (20). Closed service with dated release notes and a support portal. Open issue counts weren't re-read (9 of 15). The MCP server is in the official registry as com.shippo/shippo-mcp, verified by DNS. Official SDKs exist in five languages. The TypeScript SDK was regenerated in October, while the Python SDK's latest stable tag is 3.9.0 from 26 November 2024, with 5.0.0 in beta since 22 October 2026 (12 of 15). SDKs are generated and validated by CI workflows, and goshippo/ai has test and validation workflows, last tagged 23 July (6 of 10).", "b": "Read as a closed service. No dated API change was found. The SDKs were last pushed between February and December 2024, the support articles are dated 2023 and 2024, and the reference is undated (0 of 30). No releases or dated entries in the last 90 days were found (0). Support by email and chat with a help centre; GitHub issues were not read (6 of 15). Seven official SDKs exist but none has changed since December 2024 (10 of 15). The Node SDK has tests and no CI workflow (3 of 10). 0 + 0 + 6 + 10 + 3 = 19." }, "scores": { "a": 77, "b": 19 } }, { "by": 52, "category": "schema", "leads": "shippo", "name": "Schema \u0026 documentation", "reasons": { "a": "OpenAPI 3.1 spec for the main API with 71 operations, and six further specs for addresses v2, estimates, reporting, invoices and surcharges (25). llms.txt at docs.goshippo.com and a Markdown copy of each page (10). Descriptions state purpose and some conditions, such as the 390-day limit on shipments and when a batch is asynchronous, but rarely when not to use an endpoint (13 of 20). 94 enums and required fields marked. The 400 response schema is an open object, and weights and dimensions are strings (11 of 15). 427 examples in the spec and samples in six languages. The spec documents 400 on 66 operations, 401 and 404 once each and never 429, and the status-code page is one line per code (9 of 15). Dated API versions set by the Shippo-API-Version header and dated release notes (15).", "b": "No OpenAPI or similar file was found in the docs, the SDK repositories or a search, and the reference at trackingmore.com/docs renders by script so its schemas were not read (0 of 25). No llms.txt or Markdown docs (0). The official SDK READMEs give one line per call, and the support centre explains when to pair create with get or a webhook and that the create response carries the result (8 of 20). Field names and the required tracking_number and courier_code appear in the SDK examples, with no types, enums or constraints readable (5 of 15). Examples in seven SDK languages and a table of HTTP and meta codes with messages (12 of 15). v4 in the path with v2 and v3 still served, and the support centre says there is no changelog for switching versions. No dated API changelog was found (6 of 15). 0 + 0 + 8 + 5 + 12 + 6 = 31." }, "scores": { "a": 83, "b": 31 } }, { "by": 17, "category": "payments", "leads": "shippo", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-unit prices are public without a login. API Starter is 7 cents a label after 30 free a month, 1 cent a rate request, 2 cents a tracking request, 2 cents a US address validation and 8 cents elsewhere, plus the postage itself (20). Signup is free, and test keys create test labels and mock tracking at no charge. The docs say billing details are needed only for live label purchase. We didn't open an account to confirm (20). A person signs up in a browser and creates the key in the portal, or signs in through OAuth for the MCP server (0).", "b": "Read with the hosted rubric. No x402, MPP or L402 (0). The API page gives a from price of $0.03 a tracked order and three unlabelled figures, and the pricing page's plan prices render by script, so per-unit pricing is partly public (8 of 20). A Free plan and a 14-day trial are offered, and whether a card is asked for was not established (15 of 20). A person signs up in a browser and generates the key there (0). 0 + 8 + 15 + 0 = 23." }, "scores": { "a": 40, "b": 23 } }, { "by": 11, "category": "security", "leads": "shippo", "name": "Security \u0026 auth", "reasons": { "a": "Self-serve API keys, live and test kept apart, shown once, deletable in the portal, with no scopes and no documented expiry. The OAuth flow for platforms has one scope, \"*\". JWTs for client-side use last 12 hours (20 of 30). A webhook can carry a self-made token in its URL query string. That is the receiver's secret, not the API credential, so we noted it without the deduction. No read-only key. Test keys can't spend money, and the MCP server separates reads from writes and its docs say writes ask for confirmation (9 of 20). Tracking events, metadata and address text come from carriers and other parties. The AI repository's security policy puts prompt injection in scope for reports, with no guidance in the API docs (5 of 15). The API portal is described as showing usage. No audit log was found in the docs (3 of 15). The AI repository's security policy gives security@goshippo.com and names goshippo.com/security as the disclosure page, which returns 404, as does security.txt. The trust centre at trust.goshippo.com, where the 7 October check read SOC 2 Type II, PCI DSS, a penetration test and a bug bounty, now refuses our crawler, so those readings are set aside and unscored (5 of 20).", "b": "One API key in the Tracking-Api-Key header, shown once, at most four per account, deleted in the web app. No scopes or expiry (20 of 30). No read-only key or least-privilege mode, and delete is one call (4 of 20). Tracking checkpoints are carrier text returned to the model, and no guidance was found (3 of 15). A webhook notification log exists in the web app; no log of API calls or key use was found (4 of 15). No security.txt (404), no security page on trackingmore.com, no certification, bug bounty or disclosure policy found. The CWILL privacy policy points to a trust site that was not read (0 of 20). 20 + 4 + 3 + 4 + 0 = 31." }, "scores": { "a": 42, "b": 31 } }, { "by": 10, "category": "ergonomics", "leads": "shippo", "name": "Agent ergonomics", "reasons": { "a": "Scored on the REST API, with the MCP server noted. List calls take `results` and `page`, and `expand` controls nested objects, but there's no field selection and a shipment returns every rate. The MCP server has four tools (list, describe, read-execute, write-execute) over 73 operations, which keeps definitions small (17 of 25). Pagination on every list. Date filters exist only on shipments, within a 90-day range (14 of 20). Status codes are documented in general terms and the error body is untyped. The goshippo/ai repository has an error reference with recovery steps for MCP use (12 of 20). No idempotency key on shipments, transactions or refunds. The Reporting API accepts `idempotency_key`. The MCP read and write split lets a client approve writes. Its annotations sit behind sign-in and weren't read (8 of 20). Official SDKs for Python, TypeScript, Java, C# and PHP. Shipments and transactions default to asynchronous, and objects can't be edited after creation (13 of 15).", "b": "trackings/get filters by tracking numbers, courier and created date range, and batch create takes 40 at once. No field selection was found, and the unread reference may document more (10 of 25). Date and courier filters exist; pagination parameters were not found in what was read (8 of 20). Every response carries an HTTP code and a meta code with a message, such as 4121 for an undetected courier and 4190 for a reached quota (14 of 20). No idempotency key. A repeated create is rejected with 4101, so the write is safe to retry, and delete and retrack take ids (10 of 20). Create needs only tracking_number and courier_code, detect is free, and official SDKs cover seven languages (12 of 15). 10 + 8 + 14 + 10 + 12 = 54." }, "scores": { "a": 64, "b": 54 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Shippo", "b": "CHANNELWILL CO., LIMITED", "name": "Vendor" }, { "a": "https://api.goshippo.com", "b": "https://api.trackingmore.com/v4", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$0.02 per call", "b": "$0.03 per transaction", "name": "Price for shipment tracking" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Shippo's terms of use. The SDKs and the goshippo/ai repository (skills and MCP bridge) are MIT", "b": "Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT", "name": "Licence" }, { "a": "4", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "com.shippo/shippo-mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-27", "b": "2024-12-25", "name": "Last release" }, { "a": "couldn't be read", "b": "no date given", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "2026-08-08", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "3 stars, 73k npm/wk, 20k PyPI/wk", "b": "6 stars", "name": "Popularity" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Shippo scores 61.9 (C) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category.", "question": "Which is better for AI agents, Shippo or TrackingMore?" }, { "answer": "Shippo takes an API key or an OAuth sign-in. TrackingMore needs an API key.", "question": "Do Shippo and TrackingMore need an API key?" }, { "answer": "Yes. Shippo has a hosted endpoint at https://api.goshippo.com and TrackingMore at https://api.trackingmore.com/v4.", "question": "Can an agent call Shippo and TrackingMore without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 83 against 31", "Agent ergonomics, 64 against 54", "Security \u0026 auth, 42 against 31", "Payments \u0026 pricing, 40 against 23", "Maintenance \u0026 community, 77 against 19" ], "also": null, "goodFor": "An agent that quotes and buys parcel labels across USPS, UPS, FedEx and DHL Express for a small or mid-size shipper, with a free test mode and public unit prices.", "slug": "shippo", "watchFor": "No idempotency key on label purchase or other writes. Only the Reporting API accepts one" }, { "aheadOn": null, "also": null, "goodFor": "An agent that reports where a parcel is across many carriers from a tracking number, with a cheap per-tracking price.", "slug": "trackingmore", "watchFor": "The API reference renders by script and no OpenAPI file, llms.txt or Markdown docs were found" } ], "history": { "shippo": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-02", "delta": -0.1, "from": 62, "fromGrade": "B", "to": 61.9, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-28", "delta": 0.1, "from": 61.9, "fromGrade": "C", "to": 62, "toGrade": "B" } ], "trackingmore": null }, "job": { "capability": "shipping.tracking", "name": "Shipment tracking" }, "others": [ { "json": "https://www.anchorterminal.com/compare/easypost-vs-shippo.json", "title": "EasyPost vs Shippo", "url": "https://www.anchorterminal.com/compare/easypost-vs-shippo" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-shippo.json", "title": "Easyship vs Shippo", "url": "https://www.anchorterminal.com/compare/easyship-vs-shippo" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-shippo.json", "title": "Karrio vs Shippo", "url": "https://www.anchorterminal.com/compare/karrio-vs-shippo" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-shippo.json", "title": "Sendcloud vs Shippo", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-shippo" }, { "json": "https://www.anchorterminal.com/compare/shipbob-vs-shippo.json", "title": "ShipBob vs Shippo", "url": "https://www.anchorterminal.com/compare/shipbob-vs-shippo" }, { "json": "https://www.anchorterminal.com/compare/shippo-vs-shippypro.json", "title": "Shippo vs ShippyPro", "url": "https://www.anchorterminal.com/compare/shippo-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/shippo-vs-shipstation.json", "title": "Shippo vs ShipStation API", "url": "https://www.anchorterminal.com/compare/shippo-vs-shipstation" }, { "json": "https://www.anchorterminal.com/compare/easypost-vs-trackingmore.json", "title": "EasyPost vs TrackingMore", "url": "https://www.anchorterminal.com/compare/easypost-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-trackingmore.json", "title": "Easyship vs TrackingMore", "url": "https://www.anchorterminal.com/compare/easyship-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-trackingmore.json", "title": "Karrio vs TrackingMore", "url": "https://www.anchorterminal.com/compare/karrio-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.json", "title": "Sendcloud vs TrackingMore", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore" }, { "json": "https://www.anchorterminal.com/compare/ship24-vs-shippo.json", "title": "Ship24 vs Shippo", "url": "https://www.anchorterminal.com/compare/ship24-vs-shippo" }, { "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/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": 4, "edge": "shippo", "key": "reliability", "name": "Reliability", "shippo": 69, "trackingmore": 65, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 52, "edge": "shippo", "key": "schema", "name": "Schema \u0026 documentation", "shippo": 83, "trackingmore": 31, "weight": 13 }, { "by": 10, "edge": "shippo", "key": "ergonomics", "name": "Agent ergonomics", "shippo": 64, "trackingmore": 54, "weight": 13 }, { "by": 11, "edge": "shippo", "key": "security", "name": "Security \u0026 auth", "shippo": 42, "trackingmore": 31, "weight": 14 }, { "by": 17, "edge": "shippo", "key": "payments", "name": "Payments \u0026 pricing", "shippo": 40, "trackingmore": 23, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 58, "edge": "shippo", "key": "maintenance", "name": "Maintenance \u0026 community", "shippo": 77, "trackingmore": 19, "weight": 7 }, { "by": 1, "edge": "shippo", "key": "transparency", "name": "Transparency \u0026 trust", "shippo": 58, "trackingmore": 57, "weight": 7 } ], "summary": "Shippo scores 61.9 (C) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category. Both do shipment tracking.", "tasks": null, "tutorials": [], "verdicts": { "shippo": "Per-label and per-call prices are public, test keys are self-serve, and the OpenAPI spec, llms.txt and Markdown docs are open to a fetch. Label purchase has no idempotency key, API keys carry no scopes, and the status page logged carrier-side incidents on most days from August to October 2026.", "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/shippo-vs-trackingmore", "json": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore.min.md" }, "markdown": "Shippo scores 61.9 (C) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category. Both do shipment tracking.\n\n- Shippo: grade C, 61.9/100, rank #526 of 1349. Markdown https://www.anchorterminal.com/tools/shippo.md · JSON https://www.anchorterminal.com/api/v1/tools/shippo.json\n- TrackingMore: grade E, 41.8/100, rank #1187 of 1349. Markdown https://www.anchorterminal.com/tools/trackingmore.md · JSON https://www.anchorterminal.com/api/v1/tools/trackingmore.json\n- Best shipping and fulfilment APIs for AI agents: https://www.anchorterminal.com/best/shipping/index.md\n- All 45 shipping comparisons: https://www.anchorterminal.com/compare/shipping/index.md\n\n## Which one, for what\n\n### Shippo (C)\n\nGood for: An agent that quotes and buys parcel labels across USPS, UPS, FedEx and DHL Express for a small or mid-size shipper, with a free test mode and public unit prices.\n\nAhead on:\n- Schema \u0026 documentation, 83 against 31\n- Agent ergonomics, 64 against 54\n- Security \u0026 auth, 42 against 31\n- Payments \u0026 pricing, 40 against 23\n- Maintenance \u0026 community, 77 against 19\n\nWatch for: No idempotency key on label purchase or other writes. Only the Reporting API accepts one\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\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### Maintenance \u0026 community: Shippo +58\n\n- Shippo (77): The API release notes were last updated on 20 October 2026, and the `shippo` npm SDK 2.19.1 was tagged on 27 October 2026 (30). Six dated entries from 4 August, the latest on 1, 8, 14 and 20 October, plus TypeScript SDK 2.19.0 and 2.19.1 (20). Closed service with dated release notes and a support portal. Open issue counts weren't re-read (9 of 15). The MCP server is in the official registry as com.shippo/shippo-mcp, verified by DNS. Official SDKs exist in five languages. The TypeScript SDK was regenerated in October, while the Python SDK's latest stable tag is 3.9.0 from 26 November 2024, with 5.0.0 in beta since 22 October 2026 (12 of 15). SDKs are generated and validated by CI workflows, and goshippo/ai has test and validation workflows, last tagged 23 July (6 of 10).\n- TrackingMore (19): Read as a closed service. No dated API change was found. The SDKs were last pushed between February and December 2024, the support articles are dated 2023 and 2024, and the reference is undated (0 of 30). No releases or dated entries in the last 90 days were found (0). Support by email and chat with a help centre; GitHub issues were not read (6 of 15). Seven official SDKs exist but none has changed since December 2024 (10 of 15). The Node SDK has tests and no CI workflow (3 of 10). 0 + 0 + 6 + 10 + 3 = 19.\n\n### Schema \u0026 documentation: Shippo +52\n\n- Shippo (83): OpenAPI 3.1 spec for the main API with 71 operations, and six further specs for addresses v2, estimates, reporting, invoices and surcharges (25). llms.txt at docs.goshippo.com and a Markdown copy of each page (10). Descriptions state purpose and some conditions, such as the 390-day limit on shipments and when a batch is asynchronous, but rarely when not to use an endpoint (13 of 20). 94 enums and required fields marked. The 400 response schema is an open object, and weights and dimensions are strings (11 of 15). 427 examples in the spec and samples in six languages. The spec documents 400 on 66 operations, 401 and 404 once each and never 429, and the status-code page is one line per code (9 of 15). Dated API versions set by the Shippo-API-Version header and dated release notes (15).\n- TrackingMore (31): No OpenAPI or similar file was found in the docs, the SDK repositories or a search, and the reference at trackingmore.com/docs renders by script so its schemas were not read (0 of 25). No llms.txt or Markdown docs (0). The official SDK READMEs give one line per call, and the support centre explains when to pair create with get or a webhook and that the create response carries the result (8 of 20). Field names and the required tracking_number and courier_code appear in the SDK examples, with no types, enums or constraints readable (5 of 15). Examples in seven SDK languages and a table of HTTP and meta codes with messages (12 of 15). v4 in the path with v2 and v3 still served, and the support centre says there is no changelog for switching versions. No dated API changelog was found (6 of 15). 0 + 0 + 8 + 5 + 12 + 6 = 31.\n\n### Payments \u0026 pricing: Shippo +17\n\n- Shippo (40): No x402, MPP or L402 (0). Per-unit prices are public without a login. API Starter is 7 cents a label after 30 free a month, 1 cent a rate request, 2 cents a tracking request, 2 cents a US address validation and 8 cents elsewhere, plus the postage itself (20). Signup is free, and test keys create test labels and mock tracking at no charge. The docs say billing details are needed only for live label purchase. We didn't open an account to confirm (20). A person signs up in a browser and creates the key in the portal, or signs in through OAuth for the MCP server (0).\n- TrackingMore (23): Read with the hosted rubric. No x402, MPP or L402 (0). The API page gives a from price of $0.03 a tracked order and three unlabelled figures, and the pricing page's plan prices render by script, so per-unit pricing is partly public (8 of 20). A Free plan and a 14-day trial are offered, and whether a card is asked for was not established (15 of 20). A person signs up in a browser and generates the key there (0). 0 + 8 + 15 + 0 = 23.\n\n### Security \u0026 auth: Shippo +11\n\n- Shippo (42): Self-serve API keys, live and test kept apart, shown once, deletable in the portal, with no scopes and no documented expiry. The OAuth flow for platforms has one scope, \"*\". JWTs for client-side use last 12 hours (20 of 30). A webhook can carry a self-made token in its URL query string. That is the receiver's secret, not the API credential, so we noted it without the deduction. No read-only key. Test keys can't spend money, and the MCP server separates reads from writes and its docs say writes ask for confirmation (9 of 20). Tracking events, metadata and address text come from carriers and other parties. The AI repository's security policy puts prompt injection in scope for reports, with no guidance in the API docs (5 of 15). The API portal is described as showing usage. No audit log was found in the docs (3 of 15). The AI repository's security policy gives security@goshippo.com and names goshippo.com/security as the disclosure page, which returns 404, as does security.txt. The trust centre at trust.goshippo.com, where the 7 October check read SOC 2 Type II, PCI DSS, a penetration test and a bug bounty, now refuses our crawler, so those readings are set aside and unscored (5 of 20).\n- TrackingMore (31): One API key in the Tracking-Api-Key header, shown once, at most four per account, deleted in the web app. No scopes or expiry (20 of 30). No read-only key or least-privilege mode, and delete is one call (4 of 20). Tracking checkpoints are carrier text returned to the model, and no guidance was found (3 of 15). A webhook notification log exists in the web app; no log of API calls or key use was found (4 of 15). No security.txt (404), no security page on trackingmore.com, no certification, bug bounty or disclosure policy found. The CWILL privacy policy points to a trust site that was not read (0 of 20). 20 + 4 + 3 + 4 + 0 = 31.\n\n### Agent ergonomics: Shippo +10\n\n- Shippo (64): Scored on the REST API, with the MCP server noted. List calls take `results` and `page`, and `expand` controls nested objects, but there's no field selection and a shipment returns every rate. The MCP server has four tools (list, describe, read-execute, write-execute) over 73 operations, which keeps definitions small (17 of 25). Pagination on every list. Date filters exist only on shipments, within a 90-day range (14 of 20). Status codes are documented in general terms and the error body is untyped. The goshippo/ai repository has an error reference with recovery steps for MCP use (12 of 20). No idempotency key on shipments, transactions or refunds. The Reporting API accepts `idempotency_key`. The MCP read and write split lets a client approve writes. Its annotations sit behind sign-in and weren't read (8 of 20). Official SDKs for Python, TypeScript, Java, C# and PHP. Shipments and transactions default to asynchronous, and objects can't be edited after creation (13 of 15).\n- TrackingMore (54): trackings/get filters by tracking numbers, courier and created date range, and batch create takes 40 at once. No field selection was found, and the unread reference may document more (10 of 25). Date and courier filters exist; pagination parameters were not found in what was read (8 of 20). Every response carries an HTTP code and a meta code with a message, such as 4121 for an undetected courier and 4190 for a reached quota (14 of 20). No idempotency key. A repeated create is rejected with 4101, so the write is safe to retry, and delete and retrack take ids (10 of 20). Create needs only tracking_number and courier_code, detect is free, and official SDKs cover seven languages (12 of 15). 10 + 8 + 14 + 10 + 12 = 54.\n\n## Score by category\n\n| Category | Weight | Shippo | TrackingMore | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 69 | 65 | Shippo +4 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 31 | Shippo +52 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 54 | Shippo +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 42 | 31 | Shippo +11 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 23 | Shippo +17 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 77 | 19 | Shippo +58 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 58 | 57 | Shippo +1 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **61.9 · C** | **41.8 · E** | |\n\n## Facts side by side\n\n| Fact | Shippo | TrackingMore |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Shippo | CHANNELWILL CO., LIMITED |\n| Hosted endpoint | `https://api.goshippo.com` | `https://api.trackingmore.com/v4` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Freemium |\n| Price for shipment tracking | $0.02 per call | $0.03 per transaction |\n| x402 | no | no |\n| Licence | Proprietary service under Shippo's terms of use. The SDKs and the goshippo/ai repository (skills and MCP bridge) are MIT | Proprietary hosted service under the CWILL Terms of Service. The seven official SDKs on GitHub are MIT |\n| Tools exposed | 4 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | `com.shippo/shippo-mcp` | not listed |\n| Last release | 2026-10-27 | 2024-12-25 |\n| Terms last updated | couldn't be read | no date given |\n| Privacy policy last updated | couldn't be read | 2026-08-08 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | yes |\n| Terms or service can change without notice | couldn't be read | yes |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n| Popularity | 3 stars, 73k npm/wk, 20k PyPI/wk | 6 stars |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Shippo\n\n- -0.1 on 2 November 2026 (B to C): new evidence, correction\n- +0.1 on 28 October 2026 (C to B): checklist\n\n### TrackingMore\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Shippo.** Per-label and per-call prices are public, test keys are self-serve, and the OpenAPI spec, llms.txt and Markdown docs are open to a fetch. Label purchase has no idempotency key, API keys carry no scopes, and the status page logged carrier-side incidents on most days from August to October 2026.\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### Shippo\n\n1. Build and test with a shippo_test_ key. Test and live object IDs are separate, and the hosted MCP server has no test mode\n2. Send `Authorization: ShippoToken \u003ckey\u003e`, not Bearer, and pin `Shippo-API-Version: 2018-02-08`\n3. Before retrying a failed POST /transactions, list recent transactions. There is no idempotency key, and a second purchase is a second charge\n4. Pass `async: false` on shipments and transactions, or poll the object until its status leaves QUEUED\n5. Set `results` on list calls (under 200). Defaults vary by resource, and list calls are limited to 50 a minute on live keys\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, Shippo or TrackingMore?\n\nShippo scores 61.9 (C) on agent readiness against TrackingMore's 41.8 (E), and leads in every scored category.\n\n### Do Shippo and TrackingMore need an API key?\n\nShippo takes an API key or an OAuth sign-in. TrackingMore needs an API key.\n\n### Can an agent call Shippo and TrackingMore without installing anything?\n\nYes. Shippo has a hosted endpoint at https://api.goshippo.com and TrackingMore at https://api.trackingmore.com/v4.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/shippo-vs-trackingmore.json, and with the fewest tokens: https://www.anchorterminal.com/compare/shippo-vs-trackingmore.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"shippo\", \"b\": \"trackingmore\"}`. From a terminal: `anchor compare shippo trackingmore`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/shippo.json and https://www.anchorterminal.com/api/v1/tools/trackingmore.json\n\n## Other comparisons with Shippo or TrackingMore\n\n- [EasyPost vs Shippo](https://www.anchorterminal.com/compare/easypost-vs-shippo.md)\n- [Easyship vs Shippo](https://www.anchorterminal.com/compare/easyship-vs-shippo.md)\n- [Karrio vs Shippo](https://www.anchorterminal.com/compare/karrio-vs-shippo.md)\n- [Sendcloud vs Shippo](https://www.anchorterminal.com/compare/sendcloud-vs-shippo.md)\n- [ShipBob vs Shippo](https://www.anchorterminal.com/compare/shipbob-vs-shippo.md)\n- [Shippo vs ShippyPro](https://www.anchorterminal.com/compare/shippo-vs-shippypro.md)\n- [Shippo vs ShipStation API](https://www.anchorterminal.com/compare/shippo-vs-shipstation.md)\n- [EasyPost vs TrackingMore](https://www.anchorterminal.com/compare/easypost-vs-trackingmore.md)\n- [Easyship vs TrackingMore](https://www.anchorterminal.com/compare/easyship-vs-trackingmore.md)\n- [Karrio vs TrackingMore](https://www.anchorterminal.com/compare/karrio-vs-trackingmore.md)\n- [Sendcloud vs TrackingMore](https://www.anchorterminal.com/compare/sendcloud-vs-trackingmore.md)\n- [Ship24 vs Shippo](https://www.anchorterminal.com/compare/ship24-vs-shippo.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- [ShippyPro vs TrackingMore](https://www.anchorterminal.com/compare/shippypro-vs-trackingmore.md)\n- [ShipStation API vs TrackingMore](https://www.anchorterminal.com/compare/shipstation-vs-trackingmore.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Shippo vs TrackingMore", "url": "" } ], "description": "Shippo scores 61.9 (C) to TrackingMore's 41.8 (E) for shipment tracking. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Shippo C 61.9", "TrackingMore E 41.8", "scores" ], "h1": "Shippo vs TrackingMore", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/shippo-vs-trackingmore", "published": "2026-10-01", "section": "tools", "title": "Shippo vs TrackingMore for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/shippo-vs-trackingmore" }, "tokens": { "markdown": 4300, "slim": 2680 }, "version": 1 }