Answer-first front door

One shared provider runtime for AI apps.

Start with what WebaiBridge is, what is proved, and what to try next.

WebaiBridge is a shared provider runtime for AI apps. Start here for the product sentence, the shortest first success, and the proof or API lane you actually need next.

Shared runtime for AI apps BYOK + Web/Login only Proof before overclaim API and docs stay front-row

Open first success Open API reference

Current rule of thumb: repo-side green and proof-pack green still do not erase credentialed workstation reality or later listing work.

Start with one of these 4 front-row routes

01 30-second overview Use this when you need the product sentence fast.
02 First success Use this when you want one bounded route that really runs.
03 Proof pack Open this when the question becomes “what is really proved”.
04 API reference Open this when the question becomes “what can I call”.

This page stays docs-first on purpose. It should read like a clear public front door, not like an internal file cabinet.

Need the builder workflow, compat map, or read-only MCP shelf after the front-row question is answered? Open docs/README.md for the deeper map.

Need local bootstrap or workstation-bound reality instead? Open the public-but-demoted dev bootstrap runbook.

Question router

Start from the question, not the file tree.

The fastest way to understand WebaiBridge is to match your current question to the one route built for it. That keeps the docs front door reviewer-friendly even though the repo contains a larger atlas behind it.

Primary route

I need the 30-second product verdict.

Go here when you need one clean sentence for what WebaiBridge is, what V1 includes, and what it refuses to pretend.

First success

I want the shortest runnable first success.

Use this when you are not browsing theory. You want one bounded route from runtime identity to a runnable path without opening the full builder warehouse first.

Public truth

I need proof or public-distribution truth.

Open these shelves when the question becomes public claims, official-listing boundaries, or what is still later-lane only.

API surface

I need the core API front door.

Use this when the question becomes routes, request shapes, diagnostics, or what the runtime substrate actually exposes.

Builder workflow

I need the builder workflow, compat shelf, or MCP map.

Use this when you already know the product sentence and need the fuller tooling atlas without turning this front door into a file cabinet.

Docs atlas map

Need support truth or local bootstrap? Keep those routes visible, but one shelf deeper: support matrix and dev bootstrap runbook.

Identity shelf

30-second overview, V1 brief, scope, and runtime identity.

First-success shelf

One bounded route, one invoke path, and the shortest next proof.

Proof shelf

Proof pack, support matrix, and package-ready versus listed-live truth.

API shelf

Service HTTP reference, OpenAPI, diagnostics, and web-login routes.

Atlas map

What each docs shelf is for

The point of this second cut is IA, not ornament. Each shelf below answers one kind of review question and helps visitors avoid opening the wrong page first.

Shelf one

Identity and scope

Use the 30-second overview, V1 brief, and non-goals pages when you need the product sentence to stay honest.

Shelf two

First success and proof

Use first-success, proof pack, and the support matrix when you want one bounded route plus the current claim ceiling.

Shelf three

Core API substrate

Use the service HTTP reference, OpenAPI, diagnostics, and web-login docs when the question becomes runtime contract, not marketing copy.

Shelf four

Builder and deeper shelves

Use the fuller docs atlas, builder routes, compat hubs, media shelf, catalogs, and packet/accounting pages only after the front-row product questions are already answered.

Support and bootstrap

Keep operational truth visible without sending readers into dead ends.

The public front door should still answer package-ready versus listed-live questions and local bootstrap questions, but it should do that on the live root surface instead of shipping readers into a broken deep-link path.

Support truth

Package-ready versus listed-live

Use this shelf when the question becomes proof, distribution status, support matrix boundaries, or what still depends on later listing work.

Bootstrap

Local first success and workstation reality

Use this shelf when the question becomes local bootstrap, start-local-experience, auth-portal, debug workbench, or workstation-bound browser/session reality.