Skill
fedex
Ship, rate, and track FedEx packages from the terminal — built for small business shippers.
When to use fedex
Choose if
You're a small-business shipper or fulfillment-automation agent driving FedEx — rate shopping, bulk label creation from CSV with resume, tracking webhooks, address validation with cache, EOD manifest. Alternative is FedEx's raw developer API, which gives you none of: bulk resume, address cache, FTS5 archive search, or spend reports by lane.
Avoid if
You haven't completed FedEx BAG approval and need production label printing today — sandbox flows work but no real packages move. Also avoid as a long-term commitment without verifying the CLI's path through the SOAP-to-REST migration scheduled for June 1, 2026. Multi-carrier shippers needing UPS/DHL/USPS too should pick a multi-carrier aggregator (EasyPost, Shippo) instead.
Risk Flags
- HIGH deprecation The README explicitly warns "FedEx retires its SOAP APIs on June 1, 2026 and every existing wrapper goes dark." If the CLI depends on a path that hasn't been migrated to REST, the capability has a hard expiry date.
- HIGH scope Production label printing requires FedEx Bar Code Analysis Group (BAG) approval. Without it, production shipments fail. Sandbox/ test flows work without approval but cannot ship real packages.
- MEDIUM rate_limit Per-IP throttle: 1 request/second sustained over 2 minutes triggers a 10-minute block on all requests. Adaptive concurrency is available via `--concurrency`; bulk operations must pace.
- LOW hardware Default PDF labels won't print on thermal printers without specifying ZPL/EPL format. Small-business shippers using thermal hardware must set the label format explicitly.
Cost
Type: Unknown
Install
Default
npx -y @mvanhorn/printing-press install fedex
Estimated time to first success: ~30 min
Dependencies
Minimum runtime: Node.js (npx) or Go 1.26.3+ for source install
Distribution
- Repository
- https://github.com/mvanhorn/printing-press-library
- License
- MIT