Use cases for the agentic web

Why this page exists

Getting to agentic-web ready on more.md

You do not need a manifesto to ship. You need stable handles, honest formats, and gates that machines can satisfy. A practical readiness checklist looks like this:

• Entity model: nine URL prefixes (`/u` person, `/o` organization, `/l` place, `/a` asset, `/p` product, `/k` knowledge, `/agent` AI agent, `/e` event, `/x` custom) so callers resolve the right profile shape.
• Gates on the Go data plane: payment, trust, identity, credential, connection, capability, combined — with 402/403 responses that tell an agent what proof to fetch next.
• Formats: content negotiation for Markdown, JSON, and TOON; TOON matters when JSON key repetition is eating your token budget on tool calls.
• Real time: SSE from the data plane; Pulse for commerce-style state machines and multi-party coordination.
• SDKs: `@more-md/sdk` (npm) and `more-md` (Python) for the common read/subscribe/search paths.

Pick one sector below, ship a thin vertical on top of gates + SSE + TOON, and measure latency or token cost against your baseline. A buyer who admits the status quo is expensive matters more than polishing protocol trivia in a vacuum.

Potential entry points

Each card maps one vertical to a single profile prefix (`/u`–`/x`). Friction is loud enough in these pockets that a focused build on gates, serialization, and real-time state can still clear a bar even if you keep scope narrow and skip hero-slogan bets.