Developer API

IWE3 exposes one machine-facing API at https://api.iwe3.in/v1. The chat app lives on chat.iwe3.in, and account/admin/marketing pages on iwe3.in.

Authentication

Every /v1 request requires a personal API key. Generate one in the developer dashboard, then send it as a Bearer token:

curl

curl "https://api.iwe3.in/v1/models" \
  -H "Authorization: Bearer iwe3_…your_key…"

A missing or invalid key returns 401. Keys are only ever sent in the Authorization header — never in URLs or docs.

Endpoints

List models

GET /v1/models

curl "https://api.iwe3.in/v1/models" \
  -H "Authorization: Bearer iwe3_…your_key…"

Live model list. Free chat models are discovered automatically and may appear or disappear as the upstream tier changes.

Chat

Chat completions

POST /v1/chat/completions — streaming

curl "https://api.iwe3.in/v1/chat/completions" \
  -H "Authorization: Bearer iwe3_…your_key…" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "mimo-v2.5-free",
    "messages": [{"role": "user", "content": "hello"}],
    "stream": true
  }'

Streaming is supported and enabled by default: set "stream": true for Server-Sent Events, or omit it for a normal JSON response. Every request is metered against your daily limit.

Images

Image generation

POST /v1/images/generations

curl "https://api.iwe3.in/v1/images/generations" \
  -H "Authorization: Bearer iwe3_…your_key…" \
  -H "Content-Type: application/json" \
  -d '{"prompt": "a red fox in the snow"}'

Returns a hosted image URL. Generation takes 10–30 seconds depending on upstream load.

Status codes & limits

`200`	Success
`400`	Invalid input (missing/empty prompt, bad model, bad body)
`401`	Missing or invalid API key
`404`	Unknown route
`405`	Method not allowed
`429`	Rate limit or daily request limit reached
`502`	Upstream HTTP / network failure
`504`	Upstream timeout

Base URL https://api.iwe3.in/v1. The web app and chat surface do not expose /v1 endpoints.