{ "data": { "a": { "slug": "karrio", "name": "Karrio", "vendor": "Karrio, Inc.", "vendorUrl": "https://www.karrio.io", "kind": "http-api", "category": "shipping", "summary": "Karrio is an open-source multi-carrier shipping server from Karrio, Inc. Its REST API quotes rates, buys labels, tracks parcels and books pickups through the owner's own carrier accounts, self-hosted with Docker or run by Karrio as a paid platform.", "url": "https://www.anchorterminal.com/tools/karrio", "markdownUrl": "https://www.anchorterminal.com/tools/karrio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/karrio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/karrio.json", "repo": "https://github.com/karrioapi/karrio", "license": "LGPL-3.0 for the server, SDK and modules. Code under `ee/` is under the Karrio Enterprise licence and needs a subscription for production use. The MCP package in `packages/mcp` is Apache-2.0", "transports": [ "http" ], "packages": [ { "registry": "pypi", "name": "karrio" }, { "registry": "pypi", "name": "karrio-server" }, { "registry": "oci", "name": "karrio/server" } ], "auth": "api-key", "authNotes": "A private API key from the instance's dashboard, sent as the HTTP Basic username with no password or as `Authorization: Token key_...`. Keys carry a label and are bound to test or live mode, and the docs say a private key can perform any request without restriction. A JWT pair is also issued by `POST /api/token` for an email and password. On a self-hosted instance the owner creates the first account, so no approval from Karrio is involved. The managed platform is reached through a demo booking.", "pricing": "freemium", "pricingNotes": "Free when self-hosted under LGPL-3.0, with carrier postage billed by the owner's own carrier accounts. The platform page says the managed Scale platform starts at $499 a month with pay-as-you-go pricing and a commercial licence for embedding starts at $50,000 a year, with no unit prices published. An agent can start on a self-hosted instance in test mode with no contract. The managed platform has no self-serve signup, only a demo booking (checked 2026-10-08).", "priceSummary": "$499 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the repository, the OpenAPI file, the docs or the platform page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 799, "npmWeekly": null, "pypiWeekly": 338, "asOf": "2026-10-08" }, "docsUrl": "https://www.karrio.io/docs", "openapi": "https://raw.githubusercontent.com/karrioapi/karrio/main/schemas/openapi.yml", "capabilities": [ "shipping.rates", "shipping.labels", "shipping.tracking", "shipping.returns" ], "tags": [ "open-source", "self-hosted", "api-key", "openapi", "graphql", "webhooks", "sandbox", "docker", "python", "mcp" ], "lastRelease": "2026-06-23", "graded": true, "anchor": { "graded": true, "score": 48.7, "grade": "D", "agentReady": false, "rank": 717, "ranked": true, "rankOf": 842, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 29, "payments": 40, "reliability": 76, "schema": 68, "security": 44, "transparency": 56 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -7, "negativeNotes": [ "12 March to 23 June 2026. Versions 2026.1.22 to 2026.1.31 applied an MD5 `PASSWORD_HASHERS` override outside the test runner, so production instances stored MD5 password hashes. Fixed in 2026.1.32 and described in the changelog, with no published advisory, so 4 of a possible 15 (https://github.com/karrioapi/karrio/blob/main/CHANGELOG.md).", "8 October 2026. The README and the MCP guide tell users to run `npx karrio-mcp` and `npx -y @karrio/mcp`, and the npm registry answers 404 for both. The examples' API host `api.karrio.io` didn't resolve the same day. 3 for a claim the listing can't meet (https://registry.npmjs.org/@karrio%2fmcp, https://www.karrio.io/docs/developing/mcp-server)." ], "verdict": "A current OpenAPI 3.0.3 contract with 65 paths, a free LGPL-3.0 server and 30 carrier connectors suit a team that hosts it. The last release was 23 June 2026, the `@karrio/mcp` package the docs install is absent from npm, and `api.karrio.io` didn't resolve on 8 October 2026.", "bestFor": "A team that wants to host its own multi-carrier API with its own carrier contracts and can maintain a Django and PostgreSQL stack.", "strengths": [ "OpenAPI 3.0.3 contract in the repository at version 2026.1.32, with 65 paths covering rates, shipments, trackers, pickups, manifests, orders, documents and webhooks", "The core server and SDK are LGPL-3.0 and run on the owner's infrastructure with Docker Compose, with no fee to Karrio", "30 carrier connectors in `modules/connectors`, among them UPS, FedEx, USPS, DHL Express, Canada Post, DPD and Australia Post, used with the owner's own carrier accounts", "API keys are bound to test or live mode, and test mode runs rates, labels, trackers and pickups against carrier sandboxes", "Default throttles are in the settings file with numbers (600 requests a minute per user, 300 for carrier calls) and can be changed by environment variable" ], "weaknesses": [ "No release since 2026.1.32 on 23 June 2026, 107 days before this check, and fix pull requests opened in September 2026 were still open", "Neither `@karrio/mcp` nor `karrio-mcp` exists on npm, though the README and the MCP guide give `npx` commands for them", "`api.karrio.io` didn't resolve and `app.karrio.io` answered 503 with a paused deployment on 8 October 2026, and the managed platform starts with a demo booking", "Versions 2026.1.22 to 2026.1.31 stored passwords as MD5 hashes in production, fixed in 2026.1.32 with a changelog line and no published advisory", "No idempotency keys were found, and a private API key can perform any request. Team permissions and audit logging sit in the paid `ee/` code" ], "agentNotes": [ "Run your own instance with Docker Compose and call it at `http://localhost:5002`. Don't rely on `api.karrio.io`, which didn't resolve on 8 October 2026", "Don't run `npx karrio-mcp` or `npx -y @karrio/mcp`. Neither name is published on npm, so build the server from `packages/mcp` in the repository", "Change the default `admin@example.com` and `demo` login before the instance is reachable, and upgrade to 2026.1.32 or later so passwords aren't stored as MD5", "Don't blind-retry `POST /v1/shipments` with a `service` set or `POST /v1/shipments/{id}/purchase`. Fetch the shipment and check its status first, since no idempotency key exists", "Use a test-mode API key while building. Send it as the HTTP Basic username or as `Authorization: Token key_...`" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.7 } ], "editorialScores": { "ergonomics": 57, "maintenance": 29, "payments": 40, "reliability": 76, "schema": 68, "security": 44, "transparency": 59 }, "provenanceScore": 53 }, "connect": { "install": "git clone --depth 1 https://github.com/karrioapi/karrio\ncd karrio\ngit submodule update --init community\ncd docker\ndocker compose up", "http": "curl http://localhost:5002/v1/shipments \\\n -u key_xxxxxx:" }, "letme": { "capability": "https://letme.dev/shipping.rates", "tool": "https://letme.dev/karrio" }, "area": "business", "unitPrices": [ { "item": "Open-source edition, self-hosted", "unit": "month", "usd": 0, "note": "LGPL-3.0, you pay for your own hosting and carrier postage" }, { "item": "Scale managed platform, starting price", "unit": "month", "usd": 499, "note": "plus pay-as-you-go usage with no published unit price, by demo booking" } ], "provenance": { "legalEntity": "Karrio, Inc.", "domain": "karrio.io", "domainRegistered": "2022-01-20", "endpointOnVendorDomain": false, "terms": "https://www.karrio.io/terms-of-service", "privacy": "https://www.karrio.io/privacy-policy", "statusPage": "", "changelog": "https://github.com/karrioapi/karrio/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The Customer Terms and Conditions (last modified 8 April 2025) name Karrio, Inc., a Delaware corporation at 760 Chemin Marie-Le Ber, Verdun, Quebec, Canada, and govern the hosted platform. The self-hosted open-source edition is governed by LGPL-3.0, and `LICENSE_EE` points `ee/` users to the subscription terms at docs.karrio.io/product/resources/terms, an older copy dated 19 April 2022.", "The privacy policy (last modified 8 April 2025) covers karrio.io and associated services and excludes customer data processed on a customer's behalf. No data processing addendum was found.", "The graded surface is an instance on the owner's own host, so the endpoint isn't on the vendor's domain. `api.karrio.io` didn't resolve and `app.karrio.io` returned 503 on 8 October 2026.", "No status page was found. `status.karrio.io` didn't resolve and the site links none.", "www.karrio.io/.well-known/security.txt returns 404. `SECURITY.md` in the repository sends reports to hello@karrio.io.", "The changelog page on www.karrio.io stops at 2024.12.6. `CHANGELOG.md` in the repository is current to 2026.1.32.", "RDAP for karrio.io gives a registration date of 2022-01-20." ], "score": 53 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/karrio.json" }, "answer": "Karrio and ShippyPro score within a point of each other on agent readiness, 48.7 (D) and 48.7 (D). ShippyPro leads on security \u0026 auth.", "b": { "slug": "shippypro", "name": "ShippyPro", "vendor": "Italian Valley S.r.l.", "vendorUrl": "https://www.shippypro.com", "kind": "http-api", "category": "shipping", "summary": "Multi-carrier shipping platform from ShippyPro (Italian Valley S.r.l., Florence). Its REST API quotes rates on a customer's own carrier contracts, creates labels and returns, validates addresses, books pickups and tracks parcels. API access is sold with the Enterprise plan.", "url": "https://www.anchorterminal.com/tools/shippypro", "markdownUrl": "https://www.anchorterminal.com/tools/shippypro.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/shippypro.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/shippypro.json", "license": "Proprietary service under ShippyPro's Terms \u0026 Conditions. Both OpenAPI files state the licence as Proprietary", "transports": [ "http" ], "remoteUrl": "https://api.shippypro.com", "packages": [], "auth": "api-key", "authNotes": "Sales approval, then a key. The help centre says APIs can only be activated with an Enterprise plan and tells users to contact sales. Keys are created in the account panel under API, more than one per account, as Full Access, Maps (pickup-point map only) or PII Excluded (personal data hidden). Calls send `Authorization: Bearer \u003cAPI key\u003e`, per both OpenAPI files. The help centre article still describes the key as a Basic auth username with a blank password. No expiry or rotation was found in the reviewed documentation.", "pricing": "paid", "pricingNotes": "Enterprise plan, custom price through sales, billed annually. It is the only plan the pricing page lists with full access to the Multicarrier APIs. The self-serve plans (49 to 259 EUR a month at regular monthly prices, up to 4,000 shipments) are marked UI only. A 14-day, 30-order trial needs no card per the terms, and whether a trial account can call the API was not established. No sandbox. The Generic carrier creates test labels and rates. A higher rate limit costs extra (https://www.shippypro.com/en/pricing).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the OpenAPI files, the API page or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://api.shippypro.com/docs", "openapi": "https://api.shippypro.com/docs/v1.json", "capabilities": [ "shipping.rates", "shipping.labels", "shipping.tracking", "shipping.address-validation", "shipping.returns" ], "tags": [ "hosted", "paid", "sales-led", "enterprise", "api-key", "openapi", "webhooks", "soap", "status-page", "sla", "europe" ], "graded": true, "anchor": { "graded": true, "score": 48.7, "grade": "D", "agentReady": false, "rank": 718, "ranked": true, "rankOf": 842, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 25, "payments": 5, "reliability": 70, "schema": 64, "security": 51, "transparency": 58 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "Two OpenAPI 3.1 files, a published limit of 20 calls per 10 seconds and a 99.5 per cent monthly SLA with service credits are public. API access needs an Enterprise plan arranged through sales, no changelog or SDK was found, and label creation on v1 has no idempotency key.", "bestFor": "A European shipper or logistics platform with its own carrier contracts that already holds a ShippyPro Enterprise plan and wants rates, labels, pickups and tracking across many regional carriers through one API.", "strengths": [ "OpenAPI 3.1 files for v1 (55 operations) and v2 (17 operations) are public at api.shippypro.com/docs, with 812 examples in the v1 file", "Published SLA of 99.5 per cent monthly availability with service credits of 0.5 to 5 per cent", "API keys come in three types, Full Access, Maps and PII Excluded, and an account can hold several", "The account panel keeps API request and response logs, an API error history and webhook logs", "The Generic carrier creates test labels and rates without a real carrier or tracking number", "The privacy policy lists sub-processors per product area and says customer data is never sold" ], "weaknesses": [ "The help centre says APIs can only be activated with an Enterprise plan, which has no public price and starts with sales", "No API changelog, release notes or deprecation policy was found, and the terms allow changes without notice", "`POST /v1/Ship` takes no idempotency key. Only the 17 v2 operations accept `Idempotency-Key`", "Carrier label incidents marked critical appear on the status page on most days from August to October 2026", "No official SDK, MCP server or llms.txt was found on the pages read", "v1 answers some failures with HTTP 200 and `Status` 2, and `LabelURL` can be a string or an array" ], "agentNotes": [ "Send `Authorization: Bearer \u003cAPI key\u003e` and POST a JSON body with `Method` and `Params` to `https://api.shippypro.com/v1/\u003cMethod\u003e`. Parameter names are case-sensitive", "Check `Status` and `ErrorMessage` in every `Ship` response. HTTP 200 with `Status` 2 means no label was created", "Before retrying a failed `Ship` call, look the order up by `TransactionID`. v1 has no idempotency key, and each label counts against the plan", "Test with the Generic carrier. `Ship` and `Edit` calls on a real carrier create real labels", "Stay under 20 calls per 10 seconds, and use webhooks for tracking. The docs advise against `GetTracking` in bulk" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.7 } ], "editorialScores": { "ergonomics": 46, "maintenance": 25, "payments": 5, "reliability": 70, "schema": 64, "security": 51, "transparency": 48 }, "provenanceScore": 68 }, "connect": { "http": "curl -X POST https://api.shippypro.com/v1/Ping \\\n -H \"Authorization: Bearer \u003cAPI_KEY\u003e\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"Method\": \"Ping\", \"Params\": {}}'" }, "letme": { "capability": "https://letme.dev/shipping.rates", "tool": "https://letme.dev/shippypro" }, "area": "business", "provenance": { "legalEntity": "Italian Valley S.r.l.", "domain": "shippypro.com", "domainRegistered": "2016-10-24", "endpointOnVendorDomain": true, "terms": "https://www.shippypro.com/en/legal/terms", "privacy": "https://www.shippypro.com/en/legal/privacy", "statusPage": "https://status.shippypro.com", "changelog": "", "securityTxt": "unknown", "checked": "2026-10-09", "notes": [ "The Terms \u0026 Conditions name Italian Valley Srl, registered number 06587610483, Piazza Francesca Morvillo 15, 50144 Firenze, Italy, as owner of the ShippyPro software. They cover every ShippyPro product and service, the API included, and carry no date or version.", "The privacy policy names ShippyPro by Italian Valley S.r.l. as data controller and covers shipment sender and recipient data handled by the product, not only the website.", "RDAP for shippypro.com gives a registration date of 2016-10-24.", "The API answers at api.shippypro.com and the reference is served from the same host.", "www.shippypro.com/robots.txt disallows every path outside the language folders, the blog and a short list, so /.well-known/security.txt and /llms.txt were not requested.", "No API changelog or release notes page was found on the API page, the reference or the help centre's API section.", "The SLA at https://www.shippypro.com/en/legal/sla is stated to be part of the agreement with the customer." ], "score": 68 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/shippypro.json", "live": { "slug": "shippypro", "probe": { "target": "https://api.shippypro.com", "method": "get", "lastAt": "2026-10-09T10:42:56.354166696Z", "lastOk": true, "lastStatus": 404, "lastMs": 47, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 55, "p95ms24h": 152, "samples24h": 33, "samples30d": 33, "days": [ { "date": "2026-10-09", "probes": 33, "ok": 33 } ] }, "vendorStatus": { "page": "https://status.shippypro.com", "indicator": "major", "summary": "Partial System Outage", "checkedAt": "2026-10-09T10:42:03.244307999Z" }, "updatedAt": "2026-10-09T10:42:56.354166696Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Karrio, Inc.", "b": "Italian Valley S.r.l.", "name": "Vendor" }, { "a": "no (local only)", "b": "https://api.shippypro.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "LGPL-3.0 for the server, SDK and modules. Code under `ee/` is under the Karrio Enterprise licence and needs a subscription for production use. The MCP package in `packages/mcp` is Apache-2.0", "b": "Proprietary service under ShippyPro's Terms \u0026 Conditions. Both OpenAPI files state the licence as Proprietary", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-06-23", "b": "none", "name": "Last release" }, { "a": "2025-04-08", "b": "no date given", "name": "Terms last updated" }, { "a": "2025-04-08", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "799 stars, 338 PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Karrio and ShippyPro score within a point of each other on agent readiness, 48.7 (D) and 48.7 (D). ShippyPro leads on security \u0026 auth.", "question": "Which is better for AI agents, Karrio or ShippyPro?" }, { "answer": "Both need an API key.", "question": "Do Karrio and ShippyPro need an API key?" }, { "answer": "No hosted endpoint is listed for Karrio. ShippyPro has a hosted endpoint at https://api.shippypro.com.", "question": "Can an agent call Karrio and ShippyPro without installing anything?" }, { "answer": "Karrio is open source (LGPL-3.0 for the server, SDK and modules. Code under `ee/` is under the Karrio Enterprise licence and needs a subscription for production use. The MCP package in `packages/mcp` is Apache-2.0). No open-source release is listed for ShippyPro.", "question": "Are Karrio and ShippyPro open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 76 against 70", "Agent ergonomics, 57 against 46", "Payments \u0026 pricing, 40 against 5" ], "also": [ "Open source" ], "goodFor": "A team that wants to host its own multi-carrier API with its own carrier contracts and can maintain a Django and PostgreSQL stack.", "slug": "karrio", "watchFor": "No release since 2026.1.32 on 23 June 2026, 107 days before this check, and fix pull requests opened in September 2026 were still open" }, { "aheadOn": [ "Security \u0026 auth, 51 against 44" ], "also": [ "A hosted endpoint, with nothing to install", "No incidents deducted, where Karrio loses 7 points for them" ], "goodFor": "A European shipper or logistics platform with its own carrier contracts that already holds a ShippyPro Enterprise plan and wants rates, labels, pickups and tracking across many regional carriers through one API.", "slug": "shippypro", "watchFor": "The help centre says APIs can only be activated with an Enterprise plan, which has no public price and starts with sales" } ], "job": { "capability": "shipping.rates", "name": "Shipping rates" }, "others": [ { "json": "https://www.anchorterminal.com/compare/easypost-vs-karrio.json", "title": "EasyPost vs Karrio", "url": "https://www.anchorterminal.com/compare/easypost-vs-karrio" }, { "json": "https://www.anchorterminal.com/compare/easypost-vs-shippypro.json", "title": "EasyPost vs ShippyPro", "url": "https://www.anchorterminal.com/compare/easypost-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-karrio.json", "title": "Easyship vs Karrio", "url": "https://www.anchorterminal.com/compare/easyship-vs-karrio" }, { "json": "https://www.anchorterminal.com/compare/easyship-vs-shippypro.json", "title": "Easyship vs ShippyPro", "url": "https://www.anchorterminal.com/compare/easyship-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-sendcloud.json", "title": "Karrio vs Sendcloud", "url": "https://www.anchorterminal.com/compare/karrio-vs-sendcloud" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-shipbob.json", "title": "Karrio vs ShipBob", "url": "https://www.anchorterminal.com/compare/karrio-vs-shipbob" }, { "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/karrio-vs-shipstation.json", "title": "Karrio vs ShipStation API", "url": "https://www.anchorterminal.com/compare/karrio-vs-shipstation" }, { "json": "https://www.anchorterminal.com/compare/sendcloud-vs-shippypro.json", "title": "Sendcloud vs ShippyPro", "url": "https://www.anchorterminal.com/compare/sendcloud-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/shipbob-vs-shippypro.json", "title": "ShipBob vs ShippyPro", "url": "https://www.anchorterminal.com/compare/shipbob-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/shippo-vs-shippypro.json", "title": "Shippo vs ShippyPro", "url": "https://www.anchorterminal.com/compare/shippo-vs-shippypro" }, { "json": "https://www.anchorterminal.com/compare/shippypro-vs-shipstation.json", "title": "ShippyPro vs ShipStation API", "url": "https://www.anchorterminal.com/compare/shippypro-vs-shipstation" }, { "json": "https://www.anchorterminal.com/compare/karrio-vs-ship24.json", "title": "Karrio vs Ship24", "url": "https://www.anchorterminal.com/compare/karrio-vs-ship24" }, { "json": "https://www.anchorterminal.com/compare/ship24-vs-shippypro.json", "title": "Ship24 vs ShippyPro", "url": "https://www.anchorterminal.com/compare/ship24-vs-shippypro" } ], "scores": [ { "by": 6, "edge": "karrio", "karrio": 76, "key": "reliability", "name": "Reliability", "shippypro": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 4, "edge": "karrio", "karrio": 68, "key": "schema", "name": "Schema \u0026 documentation", "shippypro": 64, "weight": 13 }, { "by": 11, "edge": "karrio", "karrio": 57, "key": "ergonomics", "name": "Agent ergonomics", "shippypro": 46, "weight": 13 }, { "by": 7, "edge": "shippypro", "karrio": 44, "key": "security", "name": "Security \u0026 auth", "shippypro": 51, "weight": 14 }, { "by": 35, "edge": "karrio", "karrio": 40, "key": "payments", "name": "Payments \u0026 pricing", "shippypro": 5, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "edge": "karrio", "karrio": 29, "key": "maintenance", "name": "Maintenance \u0026 community", "shippypro": 25, "weight": 7 }, { "by": 2, "edge": "shippypro", "karrio": 56, "key": "transparency", "name": "Transparency \u0026 trust", "shippypro": 58, "weight": 7 } ], "summary": "Karrio and ShippyPro score within a point of each other on agent readiness, 48.7 (D) and 48.7 (D). ShippyPro leads on security \u0026 auth. Both do shipping rates.", "verdicts": { "karrio": "A current OpenAPI 3.0.3 contract with 65 paths, a free LGPL-3.0 server and 30 carrier connectors suit a team that hosts it. The last release was 23 June 2026, the `@karrio/mcp` package the docs install is absent from npm, and `api.karrio.io` didn't resolve on 8 October 2026.", "shippypro": "Two OpenAPI 3.1 files, a published limit of 20 calls per 10 seconds and a 99.5 per cent monthly SLA with service credits are public. API access needs an Enterprise plan arranged through sales, no changelog or SDK was found, and label creation on v1 has no idempotency key." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/karrio-vs-shippypro", "json": "https://www.anchorterminal.com/compare/karrio-vs-shippypro.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/karrio-vs-shippypro.md", "slim": "https://www.anchorterminal.com/compare/karrio-vs-shippypro.min.md" }, "markdown": "Karrio and ShippyPro score within a point of each other on agent readiness, 48.7 (D) and 48.7 (D). ShippyPro leads on security \u0026 auth. Both do shipping rates.\n\n- Karrio: grade D, 48.7/100, rank #717 of 842. Markdown https://www.anchorterminal.com/tools/karrio.md · JSON https://www.anchorterminal.com/api/v1/tools/karrio.json\n- ShippyPro: grade D, 48.7/100, rank #718 of 842. Markdown https://www.anchorterminal.com/tools/shippypro.md · JSON https://www.anchorterminal.com/api/v1/tools/shippypro.json\n\n## Which one, for what\n\n### Karrio (D)\n\nGood for: A team that wants to host its own multi-carrier API with its own carrier contracts and can maintain a Django and PostgreSQL stack.\n\nAhead on:\n- Reliability, 76 against 70\n- Agent ergonomics, 57 against 46\n- Payments \u0026 pricing, 40 against 5\n\nAlso in its favour:\n- Open source\n\nWatch for: No release since 2026.1.32 on 23 June 2026, 107 days before this check, and fix pull requests opened in September 2026 were still open\n\n### ShippyPro (D)\n\nGood for: A European shipper or logistics platform with its own carrier contracts that already holds a ShippyPro Enterprise plan and wants rates, labels, pickups and tracking across many regional carriers through one API.\n\nAhead on:\n- Security \u0026 auth, 51 against 44\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- No incidents deducted, where Karrio loses 7 points for them\n\nWatch for: The help centre says APIs can only be activated with an Enterprise plan, which has no public price and starts with sales\n\n\n## Score by category\n\n| Category | Weight | Karrio | ShippyPro | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 76 | 70 | Karrio +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 68 | 64 | Karrio +4 |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 46 | Karrio +11 |\n| Security \u0026 auth | 14% (17.5 this run) | 44 | 51 | ShippyPro +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 5 | Karrio +35 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 29 | 25 | Karrio +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 56 | 58 | ShippyPro +2 |\n| Negative events | ≤15 | -7 | 0 | |\n| **Total** | | **48.7 · D** | **48.7 · D** | |\n\n## Facts side by side\n\n| Fact | Karrio | ShippyPro |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Karrio, Inc. | Italian Valley S.r.l. |\n| Hosted endpoint | no (local only) | `https://api.shippypro.com` |\n| Transports | HTTP | HTTP |\n| Auth | API key | API key |\n| Pricing | Freemium | Paid |\n| x402 | no | no |\n| Licence | LGPL-3.0 for the server, SDK and modules. Code under `ee/` is under the Karrio Enterprise licence and needs a subscription for production use. The MCP package in `packages/mcp` is Apache-2.0 | Proprietary service under ShippyPro's Terms \u0026 Conditions. Both OpenAPI files state the licence as Proprietary |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-06-23 | none |\n| Terms last updated | 2025-04-08 | no date given |\n| Privacy policy last updated | 2025-04-08 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | not found in the text |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 799 stars, 338 PyPI/wk | none |\n\n## Verdicts\n\n**Karrio.** A current OpenAPI 3.0.3 contract with 65 paths, a free LGPL-3.0 server and 30 carrier connectors suit a team that hosts it. The last release was 23 June 2026, the `@karrio/mcp` package the docs install is absent from npm, and `api.karrio.io` didn't resolve on 8 October 2026.\n\n**ShippyPro.** Two OpenAPI 3.1 files, a published limit of 20 calls per 10 seconds and a 99.5 per cent monthly SLA with service credits are public. API access needs an Enterprise plan arranged through sales, no changelog or SDK was found, and label creation on v1 has no idempotency key.\n\n## Before you call either\n\n### Karrio\n\n1. Run your own instance with Docker Compose and call it at `http://localhost:5002`. Don't rely on `api.karrio.io`, which didn't resolve on 8 October 2026\n2. Don't run `npx karrio-mcp` or `npx -y @karrio/mcp`. Neither name is published on npm, so build the server from `packages/mcp` in the repository\n3. Change the default `admin@example.com` and `demo` login before the instance is reachable, and upgrade to 2026.1.32 or later so passwords aren't stored as MD5\n4. Don't blind-retry `POST /v1/shipments` with a `service` set or `POST /v1/shipments/{id}/purchase`. Fetch the shipment and check its status first, since no idempotency key exists\n5. Use a test-mode API key while building. Send it as the HTTP Basic username or as `Authorization: Token key_...`\n\n### ShippyPro\n\n1. Send `Authorization: Bearer \u003cAPI key\u003e` and POST a JSON body with `Method` and `Params` to `https://api.shippypro.com/v1/\u003cMethod\u003e`. Parameter names are case-sensitive\n2. Check `Status` and `ErrorMessage` in every `Ship` response. HTTP 200 with `Status` 2 means no label was created\n3. Before retrying a failed `Ship` call, look the order up by `TransactionID`. v1 has no idempotency key, and each label counts against the plan\n4. Test with the Generic carrier. `Ship` and `Edit` calls on a real carrier create real labels\n5. Stay under 20 calls per 10 seconds, and use webhooks for tracking. The docs advise against `GetTracking` in bulk\n\n## Questions\n\n### Which is better for AI agents, Karrio or ShippyPro?\n\nKarrio and ShippyPro score within a point of each other on agent readiness, 48.7 (D) and 48.7 (D). ShippyPro leads on security \u0026 auth.\n\n### Do Karrio and ShippyPro need an API key?\n\nBoth need an API key.\n\n### Can an agent call Karrio and ShippyPro without installing anything?\n\nNo hosted endpoint is listed for Karrio. ShippyPro has a hosted endpoint at https://api.shippypro.com.\n\n### Are Karrio and ShippyPro open source?\n\nKarrio is open source (LGPL-3.0 for the server, SDK and modules. Code under `ee/` is under the Karrio Enterprise licence and needs a subscription for production use. The MCP package in `packages/mcp` is Apache-2.0). No open-source release is listed for ShippyPro.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/karrio-vs-shippypro.json, and with the fewest tokens: https://www.anchorterminal.com/compare/karrio-vs-shippypro.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"karrio\", \"b\": \"shippypro\"}`. From a terminal: `anchor compare karrio shippypro`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/karrio.json and https://www.anchorterminal.com/api/v1/tools/shippypro.json\n\n## Other comparisons with Karrio or ShippyPro\n\n- [EasyPost vs Karrio](https://www.anchorterminal.com/compare/easypost-vs-karrio.md)\n- [EasyPost vs ShippyPro](https://www.anchorterminal.com/compare/easypost-vs-shippypro.md)\n- [Easyship vs Karrio](https://www.anchorterminal.com/compare/easyship-vs-karrio.md)\n- [Easyship vs ShippyPro](https://www.anchorterminal.com/compare/easyship-vs-shippypro.md)\n- [Karrio vs Sendcloud](https://www.anchorterminal.com/compare/karrio-vs-sendcloud.md)\n- [Karrio vs ShipBob](https://www.anchorterminal.com/compare/karrio-vs-shipbob.md)\n- [Karrio vs Shippo](https://www.anchorterminal.com/compare/karrio-vs-shippo.md)\n- [Karrio vs ShipStation API](https://www.anchorterminal.com/compare/karrio-vs-shipstation.md)\n- [Sendcloud vs ShippyPro](https://www.anchorterminal.com/compare/sendcloud-vs-shippypro.md)\n- [ShipBob vs ShippyPro](https://www.anchorterminal.com/compare/shipbob-vs-shippypro.md)\n- [Shippo vs ShippyPro](https://www.anchorterminal.com/compare/shippo-vs-shippypro.md)\n- [ShippyPro vs ShipStation API](https://www.anchorterminal.com/compare/shippypro-vs-shipstation.md)\n- [Karrio vs Ship24](https://www.anchorterminal.com/compare/karrio-vs-ship24.md)\n- [Ship24 vs ShippyPro](https://www.anchorterminal.com/compare/ship24-vs-shippypro.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Karrio vs ShippyPro", "url": "" } ], "description": "Karrio and ShippyPro score within a point of each other on agent readiness, 48.7 (D) and 48.7 (D). ShippyPro leads on security \u0026 auth. Both do shipping rates. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Karrio D 48.7", "ShippyPro D 48.7", "scores" ], "h1": "Karrio vs ShippyPro", "image": "https://www.anchorterminal.com/assets/og/compare-karrio-vs-shippypro.png", "path": "/compare/karrio-vs-shippypro", "published": "2026-10-01", "section": "tools", "title": "Karrio vs ShippyPro for AI agents, D 48.7 vs D 48.7 | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/karrio-vs-shippypro" }, "tokens": { "markdown": 2250, "slim": 680 }, "version": 1 }