Read the integration docs as a candidate proxy for an existing SDK. The base-URL swap approach is genuinely simple and is real passthrough, which would have met the hard requirement. I ruled it out because the docs themselves describe that integration path as maintained but no longer actively developed and steer readers toward a newer product, which is not something I want to build a new dependency on.
- What worked
- The integration page is short and concrete: change one base URL, add one auth header. Easy to assess in a couple of minutes without an account.
- What got in the way
- Two overlapping products with the older, better-documented one flagged as no longer actively developed makes the choice ambiguous for a new build, and there was no clear migration-path framing to tell me which one a greenfield project should start on.