This page is the thin human-readable hub for WebaiBridge's machine-readable public truth.
Think of it as:
- the signboard for what public surfaces are real today
- the shortest route into the JSON catalogs that tools should actually consume
It is not a marketing page, and it does not quietly rewrite future ambition into current support.
Today the outward catalog should still be read like this:
CLI=partialMCP=partialCodex / Claude Code / OpenClaw compat=partialLanguage policy= English-first public front door with bilingual helper pages
In plain English:
The catalog is the truth-first directory for current boundaries. It exists so humans and tools can consume the same honest support surface.
Start with these public catalogs:
- catalogs/public-surface-catalog.json
- catalogs/public-surface-catalog.schema.json
- catalogs/public-distribution-ledger.json
- catalogs/public-distribution-ledger.schema.json
If you need a narrower slice, read these directly:
- catalogs/compat-target-catalog.json
- catalogs/builder-kit-catalog.json
- catalogs/skill-pack-catalog.json
- catalogs/builder-intent-router.json
- catalogs/builder-journeys.json
- catalogs/starter-pack-comparison.json
- catalogs/provider-runtime-catalog.json
- catalogs/provider-runtime-catalog.schema.json
There is no separate provider-runtime markdown wrapper required to understand the public provider directory. The JSON catalog is the public source of truth for provider ids, lanes, and stability targets.
pnpm run webai-bridge:cli -- surface-catalog
pnpm run webai-bridge:cli -- surface-catalog-schema
pnpm run webai-bridge:cli -- public-distribution-ledger
pnpm run webai-bridge:cli -- public-distribution-ledger-schema
pnpm run webai-bridge:cli -- compat-target-catalog
pnpm run webai-bridge:cli -- builder-kit-catalog
pnpm run webai-bridge:cli -- skill-pack-catalog
pnpm run webai-bridge:cli -- provider-catalog
pnpm run webai-bridge:cli -- provider-entry --target gemini:web-login
pnpm run webai-bridge:cli -- builder-intent-router
pnpm run webai-bridge:cli -- keyword-truth
pnpm run webai-bridge:mcp -- --base-url http://127.0.0.1:4010These commands exist so that plugin/build tooling can consume current truth without hard-coding it.
The same catalog truth is readable from the read-only MCP surface:
webai-bridge.catalog.surface_catalogwebai-bridge.catalog.public_distribution_ledgerwebai-bridge.catalog.compat_target_catalogwebai-bridge.catalog.provider_catalogwebai-bridge.catalog.provider_entrywebai-bridge.catalog.builder_kit_catalogwebai-bridge.catalog.skill_pack_catalogwebai-bridge.catalog.builder_journeyswebai-bridge.catalog.builder_intent_routerwebai-bridge.catalog.keyword_truthwebai-bridge.catalog.mcp_statuswebai-bridge.catalog.mcp_tools
If you need a human-facing route instead of raw JSON:
- choose the pack first:
- then open the builder handoff hub:
- then copy a runnable host-local shape if needed:
If you need keyword or discoverability truth instead of support truth, go to docs/discoverability-keyword-truth.md.
Use this catalog to stop four common mistakes:
- turning
partialintosupported now - turning read-only into execution capability
- turning package-ready into listed-live
- turning bilingual helper surfaces into the default public-language policy
The public surface catalog is a truth-first directory, not a hype page. It is intentionally thinner than the underlying JSON family so the public docs plane stays narrow while tools still have a full machine-readable shelf.