Niches · Shipping & fulfilment
Close the day: manifest and pickup
Four or more companies' docs show a full fit.
What counts as done
A SCAN form or manifest PDF covering every label and a confirmed pickup with a reference, each in one call.
How agents ask for it: make the end-of-day manifest
, book a UPS pickup for tomorrow
Does the job 5
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Easyship BB Easyship Inc. | Create a Manifest and Create a Pickup are API endpoints, with pickup slots listed for the next seven days; pickups depend on the courier offering them. source |
| Envia F Envia Shipping | Create a Shipping Manifest groups tracking numbers into one document, and Schedule a Pickup books a driver for an address and time window, each one call. source |
| Shippo B Shippo | POST /manifests takes transaction ids sharing origin, date and carrier account and returns a manifest or SCAN form; a pickup endpoint is documented alongside. source |
| ShippyPro F Italian Valley S.r.l. | CreateManifest returns ManifestURL for given orders, and BookPickup books a pickup for supported carriers, each one call; concurrent manifests return a retryable MANIFEST_IN_PROGRESS. source |
| ShipStation API D Auctane LLC d/b/a ShipStation | POST /v2/manifests and POST /v2/pickups are documented, with manifest requests readable by id. source |
Does the job, with a limit 4
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 | POST /v1/pickups books pickups, but the SCAN form guide describes dashboard steps only; no manifest endpoint is in the API reference, though a scan_form.created webhook exists. source |
| EasyPost C Simpler Postage, Inc. (d/b/a EasyPost) | ScanForm and Pickup endpoints exist, but a ScanForm needs one origin, one carrier account and dated labels, and acc-03 shows the Python client rejecting a SCAN form batch as invalid parameters. source |
| Karrio D Karrio, Inc. | POST /v1/manifests with a document endpoint and POST /v1/pickups exist, but acc-16 shows a FedEx pickup sent with zero weight returning a generic carrier error. source |
| Sendcloud B Sendcloud B.V. | Create a pickup books a one-time carrier pickup, but no manifest or SCAN form endpoint is in the v3 index apart from a Deutsche Post order finalise. source |
Doesn't do this job 3
Listings in the category that do something else, with the reason.
What stops agents finishing
- pickup needs parcel detail the agent does not have
- carrier returns a generic error
Around it
Before: shipping.buy-label. After: notifications.push.
Where this comes from
Weight 4 of 100 in Shipping & fulfilment: 2 of 33 accounts (EasyPost SCAN form, Karrio FedEx pickup)
The same as data: /api/v1/use-cases/shipping.manifest-pickup.json, or the MCP tool get_use_case with id shipping.manifest-pickup. 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.