GET /v1/ai/images/providers

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin sites.view; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

curl -X GET https://api.zinndigital.com/v1/ai/images/providers \
  -H "Authorization: Bearer zdk_live_…"

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

Whether each provider can draw **right now, for this org**, and a machine-readable `reason` when it cannot. Requires `sites.view`. ⚖️ Owner ruling 2026-08-20 — *"declare capabilities; warn BEFORE they pick"*. That was built for a model's capabilities and never for the provider itself, which is the coarser and far more expensive version of the same question. Measured on production 2026-08-21: the live picker offered **OpenAI** and **xAI Grok** as ordinary enabled choices and both answered `422` on every request, because the estate holds a key for neither and no customer key could promote a model on its own. ⛔ `reason` is a **code**, never a sentence — `no_key`, `no_model`, `key_broken`, or empty when usable. Every string a customer reads is translated into 57 languages (§2.19), so a message assembled in the engine is an English message on a German screen. ⛔ `usable` and `key_broken` are independent. With platform credits behind it, a provider whose customer key has failed its last check is still usable — and the customer still needs telling, which is why both fields travel.

Sigogi

Martani

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 422 · 429