Can I vibe code ShipEngine?

Build a lightweight Node.js/TypeScript Express API service that acts as a custom shipping carrier abstraction layer for UPS REST API and USPS. 

1. DATA MODEL & SCHEMA:
- Create a Postgres schema with tables for `carrier_accounts` (carrier_code, credentials_encrypted), `shipments` (id, order_id, carrier_code, service_code, status, tracking_number, label_url, zpl_data), and `packages` (dimensions, weight_oz, address_from, address_to).

2. INTEGRATION & LOGIC:
- Implement POST /v1/rates: Accepts origin/destination address and package weight/dims. Calls UPS API rate endpoint and returns normalized rates [{carrier, service_name, service_code, rate_cents}].
- Implement POST /v1/labels: Accepts shipment request payload, selects requested carrier/service, sends label purchase call to carrier API, extracts tracking number and base64 ZPL string, saves to `shipments` table, and returns formatted JSON response.
- Implement GET /v1/tracking/:carrier/:tracking_number: Queries carrier API for latest status payload and normalizes response into standard enum ['in_transit', 'out_for_delivery', 'delivered', 'exception'].

3. ADDRESS NORMALIZATION:
- Add a middleware POST /v1/addresses/validate that performs basic Regex sanity checks on street, zip, state, and city fields before hitting carrier endpoints.

4. ERROR HANDLING & RESILIENCE:
- Implement exponential backoff for carrier API rate limits (HTTP 429).
- Gracefully handle carrier API failures by returning standardized error codes (e.g., CARRIER_UNAVAILABLE, INVALID_ADDRESS).

OUT OF SCOPE:
Do not build multi-tenant enterprise RBAC, complex custom customs document rendering, or non-UPS/USPS carriers. Keep code modular with clean separation between carrier API adapters.

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