Obtain a FedEx OAuth 2.0 access token using client credentials (as described in the FedEx Ship API task above).
POST to the FedEx Rates and Transit Times REST API endpoint (verify current path in FedEx developer docs) with a request body containing 'shipper', 'recipient', 'requestedShipment' (including 'serviceType' — use a wildcard or omit to rate all services, 'packagingType', 'requestedPackageLineItems' with weight and dimensions), and 'rateRequestType' (e.g., 'LIST' for published rates or 'ACCOUNT' for negotiated rates; verify accepted values in current docs).
Parse 'output.rateReplyDetails' array in the response; each element represents a service level and contains 'serviceType', 'ratedShipmentDetails' with 'totalNetCharge', 'totalBaseCharge', and 'shipmentRateDetail'.
Compare 'totalNetCharge' across service types to identify cost differences; filter by 'operationalDetail.transitDays' if transit time is a constraint.
Use 'ratedShipmentDetails.ratedPackageDetails' for per-package cost breakdowns on multi-piece shipments.
Note that rate quotes are estimates; actual invoiced amounts may include additional carrier surcharges not reflected at quote time.
Known gotchas
ACCOUNT rates (negotiated) only appear if your FedEx account number is included in the request and your credentials are associated with that account; LIST rates are the public tariff.
FedEx Rate API responses can be large for many-service shipments; parse defensively and handle partial response structures where some service types may be omitted if not available for the origin-destination pair.
Rate quotes expire quickly; they are intended for display purposes only and are not commitments from FedEx to charge that exact amount.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp