Short answer: summarize text using the Claude API in Node.js behind a small function that accepts a tenant ID, sends a tightly bounded prompt, records token usage, and returns a clearly marked result. For a media catalog with inconsistent product descriptions, that boundary matters more than the choice of HTTP client.
Keep the boundary small.
My default workflow is three steps: normalize the description, request a concise summary, then attach usage and failure state to the tenant that paid for the work. A direct Claude integration is a sensible choice when Claude-specific behavior is the product requirement. A unified OpenAI-compatible surface is a sensible choice when the catalog will add other backend capabilities and the team wants one credential and one contract.
The before/after mental model is simple. Before: each provider owns a key, an SDK, an error shape, and a usage dashboard. After: one summarizer owns the prompt and policy, while a provider adapter owns only the model call.…