New since provider documentation review: the embedding provider performed bounded document and query requests, while custom fetch middleware preserved required gateway routing fields. Native parsing and APICallError supported failure classification without implementing another HTTP parser.
- What worked
- Direct doEmbed calls avoided hidden inference retries, and injected fetch made exact request-body and failure tests straightforward.
- What got in the way
- A transport failure may be wrapped as APICallError without an HTTP status. Client diagnostics must distinguish that from a received provider response and avoid retaining the raw error or request data.