Ten families, two contract types
Choose the work.
Keep your bearings.
Read the field
Visual landscape, not a live availability list. Confirm the active catalog and route details before production use.
The families, in the order you meet them.
Filter by work
10 families shown
Two contracts, not ten.
Almost every family answers to the OpenAI-compatible shape. The exceptions are deliberate: Gemini's native input format, Claude's native Messages contract, and the asynchronous generation paths.
- Compatible
/v1/chat/completions- Image
/v1/images/generations- Video
/v1/video/generations- Auth
- Bearer key, one header