# Envia

> Envia is a multi-carrier shipping platform, strongest in Latin America, with REST APIs for rates, labels, tracking, pickups, commercial invoices and address data. An official stdio MCP server exposes ten of those operations to agents.

- Canonical: https://www.anchorterminal.com/tools/envia
- Pricing: https://www.anchorterminal.com/tools/envia#pricing
- Reviews: https://www.anchorterminal.com/tools/envia#reviews
- Markdown: https://www.anchorterminal.com/tools/envia.md (~5,450 tokens)
- Slim: https://www.anchorterminal.com/tools/envia.min.md (~1,380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/envia.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT envia.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

## Overview

**Grade F · 36.5/100 · rank #1362 of 1486 · #12 in Shipping & fulfilment · not agent-ready · confidence low**


## Assessment

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.

## Facts

| Field | Value |
| --- | --- |
| Vendor | Envia Shipping (https://envia.com) |
| Kind | HTTP API |
| Category | Shipping & fulfilment (https://www.anchorterminal.com/categories/shipping) |
| Transport | stdio |
| Auth | API key · Bearer API tokens created in the dashboard under `Desarrolladores > Acceso de API`, one environment each: sandbox tokens work only against api-test.envia.com and production tokens only against api.envia.com. Several tokens can exist and each can be deleted to revoke it. No scopes were found. The MCP server reads the token from `ENVIA_API_KEY` and defaults to sandbox. |
| Pricing | Pay per use (Pay per use) · Prepaid balance: labels, notifications, insurance and add-ons draw on money added to the Envia account, and each price is shown when quoting. There is no public price list; volume plans go through sales. A free sandbox account returns simulated rates and creates test labels with no charges. |
| x402 | No · No x402, MPP or L402 in the docs, the MCP package or the pricing page (checked 2026-11-06). Charges come from a prepaid balance. |
| Licence | unknown |
| Tools exposed | 10 |
| Packages | npm: `@envia/envia-mcp` |
| Docs | https://docs.envia.com/docs/getting-started |
| llms.txt | https://docs.envia.com/llms.txt |
| Last release | 2026-03-06 |
| Surface listed | The Envia Shipping, Queries and Geocodes REST APIs and the @envia/envia-mcp server, read from docs.envia.com, envia.com and the npm package's published files on 6 November 2026. No account was made, nothing was installed or run, and no API was called |
| MCP server | Local stdio server started with npx, ten tools, MIT on npm. The repository named in package.json (github.com/envia-ep/envia-mcp-server) could not be cloned and may be private |
| APIs | Shipping API (quotes, labels, cancel, pickups, tracking, manifest, commercial invoice, webhooks), Queries API (carriers, services, additional services, states, address structure) and Geocodes API |
| Carriers | The docs claim more than 100 carriers, compared through one request per carrier |
| Company | The site footer reads "Envia Shipping". The terms page answered 500 and the privacy policy is drawn by script, so no legal entity was read |
| Capabilities | shipping.rates, shipping.labels, shipping.tracking, shipping.address-validation |
| Tags | official, hosted, mcp, llms-txt, openapi, sandbox, prepaid, webhooks, latam, typescript |
| JSON | https://www.anchorterminal.com/api/v1/tools/envia.json |

## Score breakdown (methodology v0.7, October 2026 research run)

Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points.

| Category | Weight | This run | Score (0–100) | Points |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 20 | 20 | 4.0 |
| Performance | 10% | pending | pending | n/a |
| Schema & documentation | 13% | 16.2 | 80 | 13.0 |
| Agent ergonomics | 13% | 16.2 | 53 | 8.6 |
| Security & auth | 14% | 17.5 | 35 | 6.1 |
| Payments & pricing | 10% | 12.5 | 20 | 2.5 |
| Task success | 10% | pending | pending | n/a |
| Maintenance & community | 7% | 8.8 | 10 | 0.9 |
| Transparency & trust (editorial 0, provenance 32) | 7% | 8.8 | 16 | 1.4 |
| Negative events | up to −15 | up to −15 | none recorded | 0 |
| **Total** | | | | **36.5 → F** |

### Why each score

- Reliability 20 (checked 2026-11-06): 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.
- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.
- Schema & documentation 80 (checked 2026-11-06): 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.
- Agent ergonomics 53 (checked 2026-11-06): Ten compact MCP tools (25). Rates take one carrier per request, and the Queries API filters carriers by country and shipment type; no paging or field selection was found (10 of 20). The FAQ maps common errors to fixes, but the changelog says the three APIs return different error formats that need a normalisation helper (10 of 20). No idempotency key for labels; an unscanned label can be cancelled for an automatic refund, and the MCP tools carry no annotations (3 of 20). The MCP server defaults to sandbox, with no official API SDK (5 of 15). 25 + 10 + 10 + 3 + 5 = 53.
- Security & auth 35 (checked 2026-11-06): 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 20 (checked 2026-11-06): 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.
- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.
- Maintenance & community 10 (checked 2026-11-06): The latest dated change found is the docs changelog for March 2026 and @envia/envia-mcp 0.1.0 on 4 March 2026, more than 180 days ago; doc pages show later `updatedAt` stamps (28 October for the FAQ) that record no change (0). No dated entries in the 90 days from 8 August (0). Support through the dashboard and docs, with no public tracker; the MCP repository named on npm could not be cloned (5 of 15). The MCP package is official, with no API SDK and no registry entry (5 of 15). No public CI to read (0). 0 + 0 + 5 + 5 + 0 = 10.
- Transparency & trust 16 (checked 2026-11-06): 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.

Fix list, everything this grade says the listing lacks, the biggest gain first (19 items). What it covers is at https://www.anchorterminal.com/fixes/envia.md (JSON https://www.anchorterminal.com/fixes/envia.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "envia", "plan": "read"}`, free while the beta runs

### What we couldn't check

- unchecked: the terms (every URL tried answered 500) and the privacy policy text (drawn by script)
- unchecked: the legal entity behind Envia; the footer says only "Envia Shipping"
- Rate limits for the Shipping, Queries and Geocodes APIs
- Whether github.com/envia-ep/envia-mcp-server is public; it could not be cloned
- Whether a status page exists; status.envia.com did not connect
- The MCP package's code was read from its published npm tarball as text and not run

### Sources

- docs index: <https://docs.envia.com/llms.txt> (seen 2026-11-06)
- MCP overview: <https://docs.envia.com/docs/mcp-overview.md> (seen 2026-11-06)
- API token guide: <https://docs.envia.com/docs/authentication.md> (seen 2026-11-06)
- FAQs: <https://docs.envia.com/docs/faqs.md> (seen 2026-11-06)
- changelog: <https://docs.envia.com/docs/changelog.md> (seen 2026-11-06)
- Shipping API introduction: <https://docs.envia.com/docs/envia-shipping-api-introduction.md> (seen 2026-11-06)
- quote reference with OpenAPI definition: <https://docs.envia.com/reference/shipping-rates.md> (seen 2026-11-06)
- webhooks guide and production checklist: <https://docs.envia.com/docs/production-checklist.md> (seen 2026-11-06)
- MCP package on npm: <https://registry.npmjs.org/@envia/envia-mcp> (seen 2026-11-06)
- pricing: <https://envia.com/en-US/pricing> (seen 2026-11-06)
- privacy policy page: <https://envia.com/en-US/legal/privacy-policy?n=privacy_policy> (seen 2026-11-06)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/envia/history.json

- 2026-11-06: graded 36.5 F (methodology 0.7)

## Who's behind it (provenance 32/100, checked 2026-11-06)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | not found | 0/20 |
| Domain age | envia.com, no registry record we could read | 0/15 |
| Endpoint on the vendor's domain | envia.com | 15/15 |
| Terms of service | not found | 0/10 |
| Privacy policy | read, states 0 of the 8 things a reader expects | 4/10 |
| Status page | not found | 0/10 |
| Changelog | published | 10/10 |
| security.txt | could not be fetched | 0/10 |
| People named | not researched yet | n/a |
| Support route | help pages | 5/5 |

envia.com/robots.txt allows all but language-change paths; docs.envia.com disallows edit, login and api-next paths and links llms.txt.

The privacy policy page renders only a heading without script, and every terms URL tried answered 500, so neither text was read.

status.envia.com did not connect and no status page is linked. security.txt was not checked.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service**. We found no terms of service published for this product, so there is nothing to read and the check scores 0.


**Privacy policy** (https://envia.com/en-US/legal/privacy-policy?n=privacy_policy), read 2026-11-06, gives no date, states 0 of the 8 things a reader expects.

- Not found in the text. Gives the date it was last updated.
- Not found in the text. Says what personal data is collected.
- Not found in the text. Says how long data is kept.
- Not found in the text. Says who else receives the data.
- Not found in the text. Says whether personal data is sold or shared for advertising.
- Not found in the text. Says what rights people have over their data.
- Not found in the text. Gives a privacy contact.
- Not found in the text. Says where data is transferred or stored.

## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade)

### Key people

- No people named yet.
- Note: envia.com's about page text and the pricing, privacy and docs pages read name no founder or executive, and the terms could not be read (500). On 6 November 2026 envia.com's about pages answered 404 to a plain request. Tendencys Innovations' about page, read 6 November 2026, says Tendencys was born in 2016 and that Envia Paquetería, born in 2017, later became envia.com; it and the Tendencys home page name nobody. The npm package lists an envia.com maintainer account, which is not a public role page, so nobody is listed. No investors are named on the Envia or Tendencys pages, and a news search found none, so ownership stays unknown.

### Getting support

- Help: https://docs.envia.com/docs/faqs
- Help: https://envia.com/en-US/developers
- Sources: https://envia.com/en-US/about-us, https://docs.envia.com/docs/faqs, https://registry.npmjs.org/@envia/envia-mcp, https://tendencys.com/about-us, https://tendencys.com/

## Live (updated 2026-11-07 16:01 UTC)

- npm `@envia/envia-mcp` 0.1.0
- security.txt: unknown
- Watching changelog <https://docs.envia.com/docs/changelog>
- Watching privacy <https://envia.com/en-US/legal/privacy-policy?n=privacy_policy>
- Always current: https://www.anchorterminal.com/api/v1/live/envia.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Strengths

- Free sandbox with simulated rates and test labels, kept apart from production by separate tokens
- OpenAPI definitions embedded in every reference page, plus llms.txt and Markdown docs
- Ten MCP tools that default to the sandbox environment
- Labels cancelled before the first carrier scan are refunded to the balance automatically
- Postal code and address-structure lookups work without a token

## Weaknesses

- No status page or rate limits found
- No public price list; costs appear only when quoting
- Terms and privacy text could not be read, and no legal entity was found
- MCP tools carry no readOnly or destructive annotations, and the package has one release, 0.1.0
- The docs changelog stops at March 2026



## Before you call it (notes for agents)

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

## Connect

Install:

```bash
npx -y @envia/envia-mcp@latest
```

MCP client configuration:

```json
{
  "mcpServers": {
    "envia": {
      "args": [
        "-y",
        "@envia/envia-mcp@latest"
      ],
      "command": "npx",
      "env": {
        "ENVIA_API_KEY": "your_api_key_here"
      }
    }
  }
}
```

Through letme: https://letme.dev/envia. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Easyship | BB | 70.6 | 190 | shipping.rates, shipping.labels, shipping.tracking, shipping.address-validation | no | https://www.anchorterminal.com/tools/easyship.md |
| Sendcloud | B | 64.5 | 461 | shipping.rates, shipping.labels, shipping.tracking, shipping.address-validation | no | https://www.anchorterminal.com/tools/sendcloud.md |
| Shippo | C | 61.9 | 581 | shipping.rates, shipping.labels, shipping.tracking, shipping.address-validation | no | https://www.anchorterminal.com/tools/shippo.md |
| EasyPost | C | 57.4 | 790 | shipping.rates, shipping.labels, shipping.tracking, shipping.address-validation | no | https://www.anchorterminal.com/tools/easypost.md |
| ShipStation API | D | 51 | 1038 | shipping.rates, shipping.labels, shipping.tracking, shipping.address-validation | no | https://www.anchorterminal.com/tools/shipstation.md |
| atoship | E | 43 | 1247 | shipping.rates, shipping.labels, shipping.tracking, shipping.address-validation | no | https://www.anchorterminal.com/tools/atoship.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- @envia/envia-mcp 0.1.0 (MIT, published 4 March 2026) registers ten tools: rates, label creation, pickups, cancellation, shipment history, commercial invoices, tracking, carriers, address validation and HS code classification (source: <https://registry.npmjs.org/@envia/envia-mcp>)
- The MCP server connects to sandbox unless `ENVIA_ENVIRONMENT` is set to production, so shipments are simulated by default (source: <https://docs.envia.com/docs/mcp-overview>)
- Each API reference page's Markdown copy embeds its OpenAPI definition, with sandbox and production servers (source: <https://docs.envia.com/reference/shipping-rates.md>)
- Cancelling a label before the carrier scans it refunds the account balance automatically, per the FAQ (source: <https://docs.envia.com/docs/faqs>)
- Several lookups need no token, such as postal code validation at geocodes.envia.com (source: <https://docs.envia.com/docs/faqs>)
- The docs changelog's latest month is March 2026 (source: <https://docs.envia.com/docs/changelog>)

- #12 of 12 in Best shipping and fulfilment APIs for AI agents: https://www.anchorterminal.com/best/shipping/index.md
- All 66 shipping comparisons: https://www.anchorterminal.com/compare/shipping/index.md

## Compare

- [atoship vs Envia](https://www.anchorterminal.com/compare/atoship-vs-envia.md): E 43 vs F 36.5
- [EasyPost vs Envia](https://www.anchorterminal.com/compare/easypost-vs-envia.md): C 57.4 vs F 36.5
- [Easyship vs Envia](https://www.anchorterminal.com/compare/easyship-vs-envia.md): BB 70.6 vs F 36.5
- [Envia vs Karrio](https://www.anchorterminal.com/compare/envia-vs-karrio.md): F 36.5 vs D 46.4
- [Envia vs Sendcloud](https://www.anchorterminal.com/compare/envia-vs-sendcloud.md): F 36.5 vs B 64.5
- [Envia vs ShipBob](https://www.anchorterminal.com/compare/envia-vs-shipbob.md): F 36.5 vs C 61.3
- [Envia vs Shippo](https://www.anchorterminal.com/compare/envia-vs-shippo.md): F 36.5 vs C 61.9
- [Envia vs ShippyPro](https://www.anchorterminal.com/compare/envia-vs-shippypro.md): F 36.5 vs F 37
- [Envia vs ShipStation API](https://www.anchorterminal.com/compare/envia-vs-shipstation.md): F 36.5 vs D 51
- [Envia vs Ship24](https://www.anchorterminal.com/compare/envia-vs-ship24.md): F 36.5 vs D 52.4
- [Envia vs TrackingMore](https://www.anchorterminal.com/compare/envia-vs-trackingmore.md): F 36.5 vs E 41.8

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on envia.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "envia", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/envia"><img src="https://www.anchorterminal.com/badges/envia.svg" alt="Envia on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Envia on Anchor Terminal](https://www.anchorterminal.com/badges/envia.svg)](https://www.anchorterminal.com/tools/envia)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/envia">Envia on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Envia is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/envia-dark.png
- Light: https://www.anchorterminal.com/assets/share/envia-light.png

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
