Aweb Architecture

Aweb is the mother system: one governed operating layer for agents, provider workflows, generated products, MCP tools, and public API-connected systems. The public docs should explain this without leaking private credentials or overstating beta boundaries.

System layers

01Builder and operating surfacesAweb Studio, WebStudio/System Builder, API Warehouse, and product pages give humans and agents a shared control plane.

02Maestro orchestrationPlans durable work, routes through providers/capabilities, manages lifecycle jobs/runs, and surfaces streaming state.

03Warehouse layerAPI Warehouse and MCP Warehouse merge provider seed data, genomes, adapters, tool schemas, capability mappings, and readiness.

04Governance layerOS9 and Mission Contracts enforce approvals, policy boundaries, receipts, and operator review for sensitive actions.

05Validation and executionAweb Code, E2B sandbox execution, provider evaluation, replay, and quality gates validate generated systems and workflows.

06Observability and receiptsPrometheus/Mission Control style telemetry, request IDs, lifecycle state, and audit receipts make agent work reviewable.

Warehouse truth

The catalog is a merged runtime/build-time view of API Warehouse seed providers, API genomes, adapters, MCP Warehouse genomes, capability-registry projections, and in-house Aweb products.

{
  "providers": "245 provider surfaces",
  "apiGenomes": "200 API genome providers",
  "mcpTools": "506 MCP tools",
  "capabilities": "374 API capabilities",
  "catalog": "https://aweblabs.ai/api/v2/integrations/catalog"
}

Aweb product surfaces

GEXGamma exposure and market structure intelligence.

VeritasPrediction, probability, calibration, and market reasoning.

NinaCommerce and release operating system for product slices and revenue workflows.

LeonyCinema and media operating system for briefs, render planning, and publishing workflows.

Public vs private beta

PublicDocs, public discovery, catalog summary, sitemap, robots, llms.txt, agent card, selected V2 API routes.

AuthenticatedSDK execution, batch jobs, Maestro orchestration, key rotation, workspace-specific state.

Private betaMCP execution, managed credentials, internal Aweb systems, approval-gated external provider actions.

InternalSecrets, unapproved mutable operations, private endpoint internals, production credentials, raw operator playbooks.

Where to go next

Start with the provider warehouse, then read Maestro orchestration and MCP for agent/tool execution boundaries.