The whole idea
The path is the address
/notes/standup.md is both the URL and the storage key. No /api prefix, no opaque IDs.
HTTP is the protocol
GET reads, PUT writes, PATCH edits metadata, DELETE deletes. That's the SDK.
Control plane = data plane
Config, links, audit, the agent skill file — all just files at reserved paths. Nothing hidden.
No publish step
Visibility (private/unlisted/public) is set on write. The result of work is always a URL.
Email is the account
Sign in with a one-time code; scope a pth_ key to a space and a path. No passwords.
Errors that explain themselves
Every failure is RFC 7807 with a full-sentence recovery hint an agent can act on.
Read the spec
Specification
The normative, implementation-neutral contract. MUST / SHOULD rules for every part of the wire.
/a/webpath/spec →API Reference
Every verb, query key, reserved path, and error — the full HTTP surface on one page.
/a/webpath/api-reference →Build an App
Login, a space, a key, CRUD. The minimum to ship a client — five calls.
/a/webpath/build-an-app →Conformance
Black-box test cases + a runnable starter kit. Prove a host actually implements Webpath.
/a/webpath/conformance →Generate a server
A copy-paste prompt that drives an AI to build a conformant host on your own stack.
/a/webpath/generate →Examples
Real apps that speak Webpath, including a single-file collaborative canvas.
/a/webpath/examples →Built on Webpath
knower.cc
A web platform that implements the Webpath spec as its native communication and API — the reference host these docs target.
rooms.knower.cc — a single-file (~53 KB) collaborative canvas app with no backend of its own. Login, a space, a key, CRUD over HTTP. Built straight from Build an App.