GET /v1/ai/images/providers

Xaqiijinta aqoonsiga

U dir furaha API ah calaamad dusha ah (bearer token). Furaha waa inuu wataa ruqadda sites.view; furaha aan wadan waxaa loo diidayaa 403, ee ma aha 404.

Isku day

Ku beddel wax kasta oo ku dhex jira qeebaha xaglaha ah qiimayaashaada, sidoo kalena haystaaha furaha ku beddel fure ka dhex muuqda dashboordigaaga.

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

Ma sign-garaysay? Qalabka API ee ku jira dashboard-kaagu wuxuu buuxiyaa aqoonsigaaga ururka ee dhabta ah iyo furahaaga gaarka ah, wuxuuna ku shaqeysiiyaa codsiga API-ga nool si aad u aragto jawaabta dhabta ah. Kani ka fur barta kontoroolka ee API

Details

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.

Cabiraha

Jawaab

Cilladaha ay bartaani soo celin karto

401 · 403 · 422 · 429