Create a scoped key
Generate a server-side key in the dashboard with rate, token, cost, and model limits before it reaches production.
A single model-first API with OpenAI-compatible request shapes. Ship tutoring assistants, classroom tools, and learning-science experiments with verified responses, scoped keys, and request-level tracing, end to end.
curl https://api.viablelab.org/v1/chat/completions \
-H "Authorization: Bearer $VIABLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "viable-2",
"messages": [
{ "role": "user", "content": "Explain photosynthesis to a 5th grader." }
]
}'Capabilities
Chat, verified educational responses, multimodal input, embeddings, media generation, and audio share a single catalog, one auth model, and consistent logging.
OpenAI-compatible chat completions with model-first routing, streaming, and multimodal content arrays.
A verification layer over any chat model. Draft, verify against guidance or an answer key, and retry until it passes.
Send text, images, files, and PDFs as content parts to models that support them, with provider conversion handled for you.
OpenAI-compatible vectors for retrieval, semantic search, clustering, and reranking pipelines.
Text-to-image generation with familiar Images-style request shapes across supported providers.
Generate speech from text or transcribe uploaded audio with OpenAI-compatible audio endpoints.
Signature capability
VETTING isn't a model. It's a verification architecture layered on top of any chat model. A model drafts a response, a verification pass checks it against your guidance or answer key, and it retries until it passes or hits your attempt limit.
Built for humans and agents
Whether you're wiring up a classroom tool, a product feature, or a research pipeline, and whether you write it by hand or vibe-code it with an agent, every step is supported, from the first key to a traced request.
Generate a server-side key in the dashboard with rate, token, cost, and model limits before it reaches production.
Choose chat, VETTING, embeddings, images, or audio. Keep request bodies minimal and OpenAI-compatible.
Paste the maintained agent guide into Claude Code, Codex, Cursor, or Gemini CLI and let it build against real docs.
Confirm status, model, usage, estimated cost, and request IDs in logs, while content stays redacted by default.
Agent context
Drop the maintained API guide into Claude Code, Codex, Cursor, Gemini CLI, or your vibe-coding workflow. Your agent builds against real VIABLE Lab endpoints, with accurate request shapes, model IDs, and VETTING workflows, instead of guessing.
I am building an integration on the VIABLE Lab API. Read the guide at https://developers.viablelab.org/agents/viablelab-api.md and use it as the source of truth. The base URL is https://api.viablelab.org, and protected calls use a VIABLE Lab API key sent as a Bearer token. Follow the documented endpoint shapes, full model IDs, supported aliases, and VETTING workflows. Help me build my own application against this API.Developer operations
Create and scope keys, watch usage roll up by key and model, and trace any request down to its raw, redacted payloads, without leaving the portal.
The API surface
General chat, reasoning, multimodal, and streaming.
Lightweight vetted chat with verification metadata.
Structured answer-key verification workflows.
Vectors for retrieval and semantic search.
Text-to-image generation.
Speech synthesis and transcription.
Sign in, create a scoped key, and make your first traced request, for a product, a prototype, or a research study.