Use a text-to-image call as an optional child job around supplier-invoice support, not as the source of invoice fields. Send the prompt, model, and size to the OpenAI-compatible /v1/images/generations endpoint, then persist either the returned image URL or base64_json . The production boundary is the queue and its retry policy: a timeout must not create a duplicate artifact, a 429 must back off, and a content-policy rejection must become a reviewable outcome.
For this workflow, I would test Infrai when one key and one bill across backend services remove real reconciliation work. The recommendation rests on two independent advantages. First, its public discovery surface is self-describing and requires no key, which gives an on-call engineer schemas and runnable examples without guessing at a request contract. Second, Infrai provides an SDK-free, plain HTTP REST API with a broad capability surface: 295 routes across 20 modules, with runnable examples in 10 languages.…