Niches · Shipping & fulfilment
Buy a label for an order
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
A label file (PDF, PNG or ZPL) and tracking number returned, linked to the order, charged once even if the call is retried.
Measured, for our own tests: returned within 15 seconds. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: buy the cheapest tracked label for order 1042
, ship this order with UPS Ground
, print a label for this parcel
Does the job, with a limit 9
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.
| Listing | Why |
|---|---|
| atoship E atoship LLC | Draft then POST /v1/labels/{id}/purchase; a repeat purchase returns INVALID_STATE, order_id links the order, label_format takes pdf, png or zpl. No latency is stated, SHIPPING_HELD can stop buys, and 300 requests a day caps volume. source |
| EasyPost C Simpler Postage, Inc. (d/b/a EasyPost) | POST /shipments/:id/buy returns tracking_code and postage_label in PNG, PDF or ZPL, but there is no idempotency key and reference isn't unique, so a retry can buy twice. acc-01 shows the README buy failing with a test key. source |
| Easyship BB Easyship Inc. | POST /shipments with buy_label_synchronous returns label documents in png, pdf, url or zpl with page size, and platform_order_number links the order. No idempotency key exists, the MCP server has no test mode, and acc-23 shows crons spending usage unattended. source |
| Envia F Envia Shipping | POST /ship/generate/ returns a PDF label URL and tracking number, with printFormat and printSize required settings. No idempotency key or duplicate guard is documented, MCP tools carry no destructive annotations, and no latency is stated. source |
| Karrio D Karrio, Inc. | POST /v1/shipments/{id}/purchase returns label and tracking, with label_type options including PDF and ZPL. No idempotency key exists, and acc-17 shows an expired FedEx token reported as service_unavailable. source |
| Sendcloud B Sendcloud B.V. | Create-and-announce synchronously returns the label, external_reference_id turns a retry into a 409, and order endpoints ship an order. There is no sandbox, carrier errors can sit inside a success, and acc-26 shows a development account put on hold. source |
| Shippo B Shippo | POST /transactions buys a rate, with PDF, PNG or ZPL label formats. No idempotency key, so a retry is a second charge; acc-04 shows the order not marked fulfilled and acc-07 shows live purchases failing where test worked. source |
| ShippyPro F Italian Valley S.r.l. | Ship returns a label in PDF or ZPL with a TransactionID reference, and the Generic carrier makes test labels. The spec has no idempotency key, failures come back as Status 2 with an ErrorMessage, and API access is Enterprise only. source |
| ShipStation API D Auctane LLC d/b/a ShipStation | POST /v2/labels returns a label in pdf, png or zpl with tracking, and labels can be looked up by external_shipment_id before a retry. There is no idempotency key and no approval step before purchase, and no latency is stated. source |
Doesn't do this job 3
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Ship24 C Ship24 Limited | No label purchase in the API; it tracks numbers bought elsewhere. source |
| ShipBob B ShipBob, Inc. | The merchant doesn't buy labels; ShipBob's warehouse picks, packs and labels a created order, and tracking arrives later by order.shipped webhook. source |
| TrackingMore E CHANNELWILL CO., LIMITED | No label purchase in the API. source |
What stops agents finishing
- account put on hold or needs a person to fund it
- no idempotency key, so a retry buys a second label
- live key behaves differently from test key
- carrier token expiry reported as an outage
Around it
Before: shipping.quote-rates, commerce.read-order. After: shipping.track-parcel, commerce.mark-fulfilled, email.send-tracking.
Where this comes from
Weight 26 of 100 in Shipping & fulfilment: 11 of 33 accounts; the job most often built or broken in the GitHub accounts read
The same as data: /api/v1/use-cases/shipping.buy-label.json, or the MCP tool get_use_case with id shipping.buy-label. Other jobs in this category: /api/v1/niches?category=shipping.
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.