Skip to content
showmesh

Documentation

Learn the product by following one launch.

Start with an illustrated company story, then move into the exact workflow and technical references. You should understand why each Showmesh object exists before meeting its API shape.

Start here · illustrated field guide

The morning Fjordlane stopped giving fourteen-minute demos.

An enjoyable, fictional story about Elin, a launch under pressure, one stubborn buyer question, and the shortest path to proof. Along the way, you will build a complete Showmesh experience.

Read the story

12 minute read

  1. 1Declare one belief
  2. 2Plan three deliberate routes
  3. 3Capture only approved proof
  4. 4Publish, learn, and repair

The working sequence

Four ideas before the reference manual.

Each chapter links into the same story, so concepts arrive with a reason and a consequence.

01Declare the beliefChoose the audience, the one thing they should understand, the proof event, and the time budget.02Plan the routeSee how Qwen 3.8 Max drafts deliberate paths while GLM keeps an advisor’s eye on assumptions and risk.03Capture and verifyProve control of the origin, let OxyBlink capture only the approved surface, and require a successful replay.04Publish and learnShip an immutable release, measure proof instead of vanity activity, and repair drift with evidence attached.
Keep nearby

Reference when the story becomes work.

API and MCP

Stable product objects, scoped tokens, webhooks, and MCP tools.

Open API specification

Security model

Tenant boundaries, capture restrictions, audit events, and production controls.

Read security model

Access and privacy

Passwordless access, consent, retention, exports, and deletion rights.

Open privacy matrix

Operational status

Live service health for the Cloudflare and OxyBlink production stack.

View system status