Head to head · Shipping rates · October 2026 research run

atoship vs Envia

atoship scores 43 (E) on agent readiness against Envia's 36.5 (F), and leads in 4 of 7 scored categories. Envia leads on schema & documentation. Both do shipping rates.

Best shipping and fulfilment APIs for AI agents · All 66 shipping comparisons

Which one, for what

atoship E

Best for US sellers who want cheap USPS, UPS and FedEx labels bought by an agent from a capped wallet.

Ahead on

  • Reliability, 30 against 20
  • Security & auth, 55 against 35
  • Payments & pricing, 40 against 20
  • Transparency & trust, 45 against 16

Also in its favour

  • A hosted endpoint, with nothing to install
  • Free to start without a card

Watch for

No status page; status.atoship.com serves the home page

Envia F

Best for Shops and platforms shipping in Mexico and Latin America that want rates and labels from many local carriers.

Ahead on

  • Schema & documentation, 80 against 55

Watch for

No status page or rate limits found

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust atoship +29

atoship 45

Closed service under terms naming atoship LLC of California (15 of 30). The privacy policy (7 May 2026) keeps data as long as necessary with no periods and names no processors (10 of 30). No deprecation policy or dated notices found (0). No subprocessor list or data locations found (0). 15 + 10 + 0 + 0 = 25.

Envia 16

Every terms URL tried answered 500 and the privacy policy is drawn by script, so no terms, entity or data-handling statement was read (0 of 30, 0 of 30). No deprecation policy or dated notices (0). No subprocessors or data locations found (0). 0 + 0 + 0 + 0 = 0, as unread rather than absent where the pages exist.

Schema & documentation Envia +25

atoship 55

No OpenAPI found (/openapi.json is 404); a Postman collection v2.1 of 15 endpoints is the only machine-readable contract, and the hosted MCP tools' schemas were not read because /api/ is disallowed (15 of 25). llms.txt (10). The MCP page gives each tool a one-line description and an example prompt (8 of 20). Input typing could not be checked beyond the docs' object pages (5 of 15). The errors page documents status codes, error.code values and retryAfter, with examples (12 of 15). v1 API, no changelog found (5 of 15). 15 + 10 + 8 + 5 + 12 + 5 = 55.

Envia 80

Each reference page's Markdown copy embeds an OpenAPI definition with sandbox and production servers (25). llms.txt and a Markdown copy of each page (10). Endpoint descriptions say what each is for and which call comes next in the workflow, and the rate tool warns that sandbox rates are simulated (15 of 20). The quote definition has 17 enums and required lists (11 of 15). Workflow examples and an error-formats guide named in the changelog, though its Markdown address answered 404 and the quote definition documents only 200 (9 of 15). A dated docs changelog by month, the latest March 2026 (10 of 15). 25 + 10 + 15 + 11 + 9 + 10 = 80.

Security & auth atoship +20

atoship 55

Live and test API keys sent as Bearer tokens, with the docs advising separate keys with limited scopes and rotation, and OAuth with PKCE for the hosted MCP server (25 of 30). Test keys create no real labels, the consent screen names label buying and voiding, and the docs say the agent can spend only funds already in the wallet, with no per-call confirmation (12 of 20). Responses carry addresses and carrier tracking data rather than free text from strangers (10). No audit log found (0). security.txt valid to December 2027 with a security contact; no certification, bounty or disclosure policy beyond the terms (8 of 20). 25 + 12 + 10 + 0 + 8 = 55.

Envia 35

Bearer tokens bound to one environment, several per account, revocable by deleting them, with no scopes (20). No read-only token; the MCP server's sandbox default keeps test calls from spending money (5 of 20). Responses carry carrier and address data rather than free text from strangers (10). No audit log found (0). No security page, certification, security.txt or disclosure policy found (0). 20 + 5 + 10 + 0 + 0 = 35.

Payments & pricing atoship +20

atoship 40

No x402, MPP or L402 (0). Per-unit fees are published without a login ($0.08 a BYOCA label, $0.03 a tracking number or address check), and wallet postage is priced live in a public calculator (20). Free account with no card, and test keys (20). A person signs up in a browser and funds the wallet (0). 0 + 20 + 20 + 0 = 40.

Envia 20

No x402, MPP or L402 (0). No public price list: each cost is shown when quoting, and volume plans go through sales (0). A free sandbox account creates test labels with no charges (20). A person signs up in a browser and tops up a balance for live labels (0). 0 + 0 + 20 + 0 = 20.

Reliability atoship +10

atoship 30

Graded as a hosted service on the MCP server at atoship.com/api/mcp and REST API v1. status.atoship.com serves the marketing home page and the docs' API Status page rendered no status content, so no status page is counted (0). No readable incident history (5). 429 and a RATE_LIMIT_EXCEEDED code are documented, without numbers (5 of 15). A 429 carries error.retryAfter and Retry-After; no idempotency key for label purchases was found (10 of 15). No SLA (0). Not labelled beta (10). 0 + 5 + 5 + 10 + 0 + 10 = 30.

Envia 20

Graded as a hosted service on Envia's REST APIs, with the local MCP server noted. No status page is linked and status.envia.com did not connect (0). No readable incident history (5). No rate limits found in the docs index, FAQs, integration guide or production checklist (0). The production checklist asks for 5xx retry logic and webhook deduplication, with no 429 or idempotency guidance for label creation (5 of 15). No SLA found (0). Neither the APIs nor the MCP server is labelled beta (10). 0 + 5 + 0 + 5 + 0 + 10 = 20.

Score by category

CategoryWeight this runatoshipEnviaEdge
Reliability16%203020atoship +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25580Envia +25
Agent ergonomics13%16.25353even
Security & auth14%17.55535atoship +20
Payments & pricing10%12.54020atoship +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81010even
Transparency & trust7%8.84516atoship +29
Negative events≤1500
TotalE 43/100F 36.5/100

Facts side by side

FactatoshipEnvia
KindHTTP APIHTTP API
Vendoratoship LLCEnvia Shipping
Hosted endpointhttps://atoship.com/api/mcpno (local only)
TransportsStreamable HTTP, stdiostdio
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
Tools exposed1210
Read-only variant documentednono
llms.txtyesyes
Last release2026-02-182026-03-06
Terms last updated2026-08-20no document linked
Privacy policy last updated2026-05-07no date given
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waiveryesnot read yet

Verdicts

atoship

atoship gives agents twelve MCP tools and a REST API for US labels with published per-unit fees, free sign-up, test keys and a wallet the agent cannot overspend. No status page, rate-limit figures, OpenAPI spec or changelog was found, and the npm MCP package has not changed since February 2026.

Envia

Envia's shipping APIs are documented for agents, with llms.txt, OpenAPI definitions on every reference page, a free sandbox and a compact ten-tool MCP server that defaults to test mode. No status page, rate limits, public price list or readable terms were found, and the MCP package has had one release.

Before you call either

atoship

  1. Use an ak_test_ key until the user confirms live labels; test mode creates no real labels
  2. Ask the user before purchase_label, since it spends the wallet balance
  3. Call void_label promptly for a mistaken label, and check the carrier's refund rules
  4. Branch on error.code, and on 429 wait error.retryAfter seconds
  5. Validate the address with validate_address before buying; the standalone endpoint costs $0.03 a call

Envia

  1. Leave ENVIA_ENVIRONMENT unset until the user confirms live shipping; the default is sandbox
  2. Ask the user before envia_create_label in production, since it spends the account balance
  3. Validate the postal code at geocodes.envia.com before quoting to avoid no-coverage errors
  4. Cancel an unwanted label before the carrier scans it to get the automatic refund
  5. Use a sandbox token with sandbox hosts and a production token with production hosts; they are not interchangeable

Questions

Which is better for AI agents, atoship or Envia?

atoship scores 43 (E) on agent readiness against Envia's 36.5 (F), and leads in 4 of 7 scored categories. Envia leads on schema & documentation.

Do atoship and Envia need an API key?

atoship takes an API key or an OAuth sign-in. Envia needs an API key.

Can an agent call atoship and Envia without installing anything?

atoship has a hosted endpoint at https://atoship.com/api/mcp. Envia runs on your own machine, with no hosted endpoint listed.

Other comparisons with atoship or Envia

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.