API Reference

Aweb V2 exposes public discovery, selected OpenAI-compatible generation routes, Aweb-native lifecycle routes, Maestro orchestration, and OS9 governance surfaces. The catalog currently reports 245 provider surfaces, 200 API genome providers, and 506 MCP tools.

Base URLs

REST APIhttps://aweblabs.ai/api/v2
OpenAPIhttps://aweblabs.ai/api/openapi.json
Interactive API docshttps://aweblabs.ai/api/docs

Authentication

Execution routes require a bearer token. Public discovery routes may be readable without a token, but clients should still send scoped keys for workspace-specific behavior.

Authorization: Bearer sk-aweb-your_api_key

Endpoint map

GET/api/v2V2 contract root and discovery summary
GET/api/v2/healthPublic health check
GET/api/v2/capabilitiesPublic capability discovery
GET/api/v2/capabilities/:slugOne capability descriptor
GET/api/v2/familiesPublic intent families
GET/api/v2/providersProvider discovery from the API Warehouse seed
GET/api/v2/integrations/catalogFull API/MCP integration catalog
POST/api/v2/responsesResponses-style model output and streaming
POST/api/v2/chat/completionsChat completions
POST/api/v2/audio/speechText-to-speech synthesis
POST/api/v2/audio/transcriptionsSpeech-to-text transcription
POST/api/v2/images/generateImage generation
POST/api/v2/images/editImage editing
POST/api/v2/images/upscaleImage upscaling
POST/api/v2/videos/generateVideo generation
POST/api/v2/videos/from-imageImage-to-video generation
POST/api/v2/music/generateMusic generation
POST/api/v2/music/composeMusic composition
POST/api/v2/batchBatch job creation
GET/api/v2/batch/:idBatch job status
POST/api/v2/orchestrate/runMaestro orchestration ingress
GET/api/v2/os9/mission-contractsOS9 mission contract discovery
GET/api/v2/os9/receiptsOS9 receipt discovery
GET/api/v2/os9/approvalsOS9 approval queue

Catalog discovery

Use the integration catalog when docs, agents, SDK examples, or startup-program reviewers need the current provider/API/MCP state.

curl "https://aweblabs.ai/api/v2/integrations/catalog" | jq '.summary'

Chat completion

curl -X POST "https://aweblabs.ai/api/v2/chat/completions" \
  -H "Authorization: Bearer $AWEB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      { "role": "user", "content": "Explain Aweb provider routing." }
    ],
    "stream": false
  }'

Maestro orchestration

curl -X POST "https://aweblabs.ai/api/v2/orchestrate/run" \
  -H "Authorization: Bearer $AWEB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "Research competitors, synthesize the signal, and draft launch positioning",
    "capabilities": ["search.web", "llm.chat"],
    "policy": "balanced"
  }'

Errors and receipts

Errors use problem-detail style fields when available. Lifecycle routes may include additive job, run, and audit_receipt objects.

{
  "type": "https://aweblabs.ai/errors/provider_unavailable",
  "title": "Provider Unavailable",
  "status": 503,
  "detail": "No provider could fulfill the request.",
  "request_id": "req_provider_123",
  "code": "providers_exhausted"
}