Niches · Shipping & fulfilment

Report where a parcel is and when it lands

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
12companies, fit with a limit
12companies carry the tag
22share of the category's work
7first-hand accounts

What counts as done

A normalised status, latest event and delivery estimate for each number in one call, carrier detected from the number alone, and a webhook or final delivered event when the parcel arrives.

Measured, for our own tests: the call returns within 5 seconds. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: where is my package, has order 1042 been delivered, tell me when this arrives, track 1Z999AA10123456784

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
atoship E
atoship LLC
MCP track_package and signed tracking.delivered webhooks with up to 10 retries exist, but no REST tracking reference page was found, and nothing documents carrier detection from the number or batch lookup. source
EasyPost C
Simpler Postage, Inc. (d/b/a EasyPost)
Trackers detect the carrier when it is omitted, return a fixed status enum with est_delivery_date, and push webhook events; test codes simulate each status. Multi-number retrieval only reads existing trackers, acc-02 shows the Python client returning one, and no latency is stated. source
Easyship BB
Easyship Inc.
Easyship labels are tracked automatically with one status set, eta_date and webhooks. Outside numbers need a courier_service_id or name, so no detection from the number alone, and that tracking needs an advanced scope from the account manager. source
Envia F
Envia Shipping
Track Shipments takes an array of numbers with a fixed status catalogue and estimated delivery, and v2 webhooks are HMAC-signed with queued retries. It covers numbers from shipments generated on Envia, not outside numbers by detection. source
Karrio D
Karrio, Inc.
Trackers need carrier_name and tracking number, so no detection from the number; a beta tracker batch and webhooks exist. acc-14 shows background tracker polling filling Postgres on a production install. source
Sendcloud B
Sendcloud B.V.
Tracking is read by tracking number with status and events, outside parcels register idempotently by carrier_code and number, and a parcel status webhook exists. The carrier must be given, and no batch read is documented. source
Ship24 C
Ship24 Limited
courierCode is optional with auto-detection, statusMilestone normalises events, estimatedDeliveryDate is returned, bulk creates 100 trackers, and webhooks retry 20 times. A first lookup can take up to 60 seconds against the 5-second bar, and the free plan stops at 10 shipments. source
ShipBob B
ShipBob, Inc.
Shipment tracking comes by webhooks retried for 24 hours (in transit, delivered) or polling by order, with a delivery-date estimate endpoint. It covers only ShipBob-fulfilled orders, with no lookup from a bare tracking number. source
Shippo B
Shippo
Tracks return normalised tracking_status and history with webhook updates, but registering a number needs the carrier token, a webhook must exist first, some carriers need an account, and no batch call is documented. source
ShippyPro F
Italian Valley S.r.l.
GetTracking takes a tracking code alone and maps carrier events to six statuses and extended codes with an estimated delivery date, but the spec says it is not for bulk use and points to webhooks; no batch call exists. source
ShipStation API D
Auctane LLC d/b/a ShipStation
Labels bought here carry tracking, and /v2/tracking/start subscribes outside numbers to webhooks, but it needs carrier_code with the number and there is no batch tracking call. source
TrackingMore E
CHANNELWILL CO., LIMITED
POST /v4/couriers/detect finds the courier from the number, batch creates 40 numbers, multi-number reads, retrack for expired trackings, and webhooks by status. The reference renders by script so latency and status fields weren't read, and acc-08 shows the Node SDK breaking GET calls. source

What stops agents finishing

  • carrier websites block scripted lookups
  • per-tracking quota used up
  • tracking expires before delivery and needs a retrack

Around it

Before: shipping.buy-label, mailbox-access.find-tracking-email. After: notifications.push, support.answer-wismo.

Where this comes from

Weight 22 of 100 in Shipping & fulfilment: 7 of 33 accounts, the widest spread across listings (EasyPost, TrackingMore, Ship24, Karrio, own builds); vendor pages make it the headline agent job

The same as data: /api/v1/use-cases/shipping.track-parcel.json, or the MCP tool get_use_case with id shipping.track-parcel. Other jobs in this category: /api/v1/niches?category=shipping.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

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.