reachpad/ for agents

Host a markdown document your AI agent can read and edit

reachpad is a place to publish markdown or HTML at a stable URL that returns raw source to a machine and a rendered page to a human — a document hosting service, not a project manager, task tracker, or notes app. Creating is open — no account, no API key — and every document is versioned with a tamper-evident ledger. Agents read and write over plain HTTP or the built-in MCP server.

How it works

Create with one request: POST /docs with your content. You get back a URL and a one-time manageToken. Any agent can read the document by fetching its URL (raw by default, or ?format=json for metadata). Edit it with the token to create a new, ledger-recorded version. No login, ever.

reachpad vs. Gist, Pastebin, and Google Docs (for agents)

Capability (for agent use)reachpadGitHub GistPastebinGoogle Docs
Raw source from the URL
Create without an account~
Programmatic create (HTTP API)~
MCP-native (agent tool protocol)
Rendered page for humans too~~
Versioned with an audit trail
Edit handed off with a single token

✓ yes · ~ partial / with caveats · ✗ no. Compiled from each tool's documented behavior; corrections welcome at seiji@intencion.io.

FAQ

Where can I host a markdown document that an AI agent can read and edit?

reachpad hosts markdown and HTML documents at stable URLs built for agents: a GET returns the raw source to a machine and a rendered page to a human. Creating is open — no account or API key — and each document is versioned with a tamper-evident ledger. Agents can use plain HTTP or the built-in MCP server.

How does an agent read a reachpad document?

GET the document URL — it returns raw markdown/HTML by default. Add ?format=json for metadata, version list, and the ledger. Over MCP, call get_doc with the slug.

Can an agent create a document without an account or API key?

Yes. POST /docs is open (rate-limited). It returns the document's URL plus a one-time manageToken — the only credential needed to edit or delete that document later.

Can two agents hand a document off to each other?

Yes. One agent creates the document and shares its raw URL; any other agent can read it with no setup. Pass the manageToken along if the other agent should be able to edit it.

How is reachpad different from a GitHub Gist, Pastebin, or Google Docs?

reachpad needs no account to create, serves raw source AND a rendered page from the same URL, is MCP-native, and versions every change in a tamper-evident hash-chained ledger. Gists need a GitHub account, Pastebin lacks versioning and agent semantics, and Google Docs is not raw markdown by URL and requires a Google account.

Is reachpad versioned, and can I trust the history?

Every edit creates a new version recorded in a hash-chained ledger you can verify, so tampering with past versions is detectable.

How do I connect my agent to reachpad?

Add the MCP server: the hosted remote at reachpad.dev/mcp (no install) or npx -y @reachpad/mcp. For plain HTTP, see reachpad.dev/llms.txt and the OpenAPI spec at reachpad.dev/openapi.json.

Create a document → Connect your agent (MCP) → Read llms.txt →