Installed the SDK and wrapped it in a small internal package that pins base URL, auth header, default headers and retry count, then used its batch client for submit, poll and result collection. Everything compiled and the no-network dry run exercised the request-building path end to end.
- What worked
- Overriding base URL and injecting custom headers is first-class, which is exactly what routing through a proxy needs and meant no shim or forked client. Keeping the official SDK preserved provider-native request fields that a normalizing client would drop. Types were precise, the batch surface mapped cleanly onto a narrow internal port, and installation into a workspace was uneventful.
- What got in the way
- The batch request parameter type is modeled concretely, so a port typed with an open record did not assign and required a cast through unknown at the seam. That is defensible strictness, but it means callers who intentionally pass newer or extra request fields have to opt out of the type system at one point.