Can I vibe code EasyPost?

Build a multi-carrier shipping abstraction API using Node.js, Express, and PostgreSQL, normalizing operations across UPS REST API and USPS Web Tools API.

1. DATA MODEL:
- Create tables: `shipments` (id, order_id, status, carrier, tracking_code, label_url, selected_rate, address_from_id, address_to_id, parcel_id), `rates` (id, shipment_id, carrier, service_name, rate_amount, currency, delivery_days), `parcels` (length, width, height, weight_oz), and `addresses` (street1, street2, city, state, zip, country, is_valid).

2. UNIFIED SHIPPING ENDPOINTS:
- POST `/api/v1/shipments`: Accepts package dimensions, weight, origin, and destination addresses. Normalizes input and concurrently fetches rates from both UPS REST API and USPS API.
- Save normalized rates into `rates` table returning a standardized payload with fields: `{ carrier, service, rate, delivery_days, rate_id }`.
- POST `/api/v1/shipments/:id/buy`: Accepts a `rate_id`. Calls the target carrier's buy API endpoint, requests label output in PDF format, uploads PDF to local cloud storage, updates shipment status to `purchased`, and returns `{ tracking_code, label_url }`.
- POST `/api/v1/tracking/webhook`: Standardized endpoint to process incoming tracking webhooks from carriers, updating `shipments.status` to `in_transit`, `out_for_delivery`, or `delivered`.

3. ADDRESS VALIDATION & ERROR HANDLING:
- Integrate a basic address normalization pass (USPS Zipcode Lookup API) before calling rate engines.
- Handle carrier timeout exceptions gracefully: if UPS fails, return USPS rates rather than failing the entire request.
- Retain raw API request/response logs in a `carrier_logs` table for auditing.

4. OUT OF SCOPE:
- Do not build a complex front-end UI; expose clean REST JSON endpoints.
- Exclude international customs generation and hazmat manifest logic for this iteration.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs