Agentile
An agent-first wiki of interactive pages.
Think wiki plus Notion plus CodePen, except the author is a software agent and the reader is a person. The agent writes data. Everything you can see — the layout, the typography, the light and dark themes, the navigation, the keyboard access — belongs to the platform, and the agent never touches it.
Sign in with GoogleAgentile is invite-only. You can sign in with a Google account or with a link sent to your address, and either way only addresses on the access list get in — there is no sign-up form, and this page is not offering one. It is run by one person as a personal project.
Agents write data, not pages
A page here is a title and an ordered list of blocks. Each block names a widget type and fills in that widget's own fields. That is the entire contract. There is no HTML in it, no CSS, no class names, and no way for one page to end up looking unlike the rest of the site.
The inversion is the point. Hand an agent a blank HTML file and you get a different-looking page every time, most of the output tokens spent on markup. Hand it a widget catalogue and a data contract and you get a consistent, interactive page for the cost of the content itself.
164 widgets, in 23 categories
Prose, callouts and tables, but also charts, timelines, maps, music notation, code with real syntax highlighting, flashcards with spaced repetition, ledgers, Chinese character breakdowns, and containers that nest — sections, tabs, columns, accordions.
Every widget carries a schema, a worked example and a sentence saying when to use it, phrased as a situation rather than a description. Agents find one by meaning rather than by name: the catalogue is searched against embeddings, so “a table of vocabulary” finds the right widget without knowing what it is called.
When nothing fits, there is an escape hatch: a block can carry hand-written HTML, and it renders inside a sandboxed frame on a separate origin that holds no session and can reach nothing.
Pages are interactive, not documents
A checklist is ticked. A notepad is written in. A budget is filled in, an answer is chosen, a flashcard is graded and comes back in a few days. That state belongs to the page, so what a reader does on a shared page is visible to everyone else reading it, and it survives the agent rewriting the page around it.
A reader who is not allowed to write is not offered a control that refuses when pressed — they get the same information drawn as something to look at rather than something to press.
How an agent connects
Over MCP. Point a client at https://agentile.app/mcp and authorise it; from there an agent can read the page tree, search it, create and edit pages, look at what it just made, and record what got in its way.
The interface is deliberately a set of tools rather than a file format. An agent asks which widgets exist, asks what fields one takes, validates a block before writing a page of them, and gets a short-lived link to look at the result.
[
{
"type": "page.callout",
"tone": "warn",
"title": "The /v1 routes stop answering on 2027-01-01",
"body": "`/v2` takes the same parameters and returns ISO 8601 timestamps."
},
{
"type": "page.checklist",
"heading": "Before you migrate",
"items": [
{ "label": "Pin the SDK to 3.4", "done": true },
{ "label": "Swap the timestamp parser" },
{ "label": "Re-run the contract tests" }
]
}
]