# WebaiBridge 30-Second Overview

If you only have 30 seconds, remember these four lines:

1. WebaiBridge is **not** another AI app.
2. It is a **shared provider runtime for AI apps**.
3. It turns `BYOK + Web/Login` access into one service-first substrate that
   other AI products can call.
4. Today it ships a repo-native runtime, a read-only MCP descriptor, a
   runtime-diagnostics builder packet, starter packs, and truth-first public
   docs. npm, registry, marketplace, Docker, and broader publication are still
   later lanes.

## One Sentence

> **WebaiBridge is the shared runtime pipe for AI apps, not another AI app.**

## The Problem It Solves

- teams keep rebuilding provider contracts
- auth/session/diagnostics are scattered across products
- real users often have subscriptions or web sessions, not just API keys
- runtime truth, starter paths, compat routes, and public claims drift apart

## What It Can Honestly Claim Today

- `shared provider runtime`
- `BYOK + Web/Login`
- `service-first runtime frontdoor`
- `partial thin compat`
- `partial read-only MCP surface`
- `runtime-diagnostics` public skill packet
- `copy-ready starter packs`

## What It Cannot Honestly Claim Yet

- `full Codex parity`
- `full Claude Code parity`
- `full OpenClaw parity`
- `published npm/runtime package`
- `official registry or marketplace listing`
- `MCP execution brain`

## If You Only Do One Next Thing

Read [docs/first-success.md](../first-success.md).

If you only want the proof boundary next, read
[docs/public-proof-pack.md](../public-proof-pack.md).