Webpath — Examples

Real apps that speak Webpath. The spec is small enough that an app is usually a single file that logs in, takes a key, and does CRUD over HTTP — no backend of its own, because the Webpath host is the backend.

knower.cc is a web platform that implements the Webpath spec as its native communication and API. The apps below run on it.

rooms — a collaborative canvas

Live: rooms.knower.cc

A single-file (~53 KB) HTML canvas app: sign in with email, create a "room", and draw / place things on an infinite canvas. There is no server code — the entire backend is a Webpath space:

Login → POST /api/v1/auth/otp + /api/v1/auth/verify (email is the account).
A room is a space → /join mints room.knower.cc; the app holds a scoped pth_ key.
State is files → the canvas reads and writes JSON/asset files with plain PUT / GET / ?list.
Sharing is a URL → set a file ?visibility=public on write and the clean URL just works.

It was built straight from Build an App — the same five calls, nothing more. That is the whole point of Webpath: the doc you can paste into a chat agent is also the doc a human builds from.

Patterns you can copy

Want	Webpath move
A blog / docs site	`PUT *.md ?visibility=public` → share the clean URL (renders to HTML).
An event log / agent memory	`PUT …jsonl ?append` — concurrency-safe line accumulation.
A paste / share tool	`PUT` then hand out the clean URL; `?qr` for a scannable code.
A settings store for an app	a private space + one scoped key; `GET`/`PATCH ?meta`.
A drop box others can add to	grant `write`-only on a path via `?meta` `sharing`.

Build your own

Read Build an App (the five calls).
Keep the API Reference open for the full verb surface.
Point it at a Webpath host (knower.cc, or any host that implements the spec).

The result of your work is always a URL. Share the clean form.

→ Spec · API Reference · Build an App · Conformance · Generate a server · Home