> For the complete documentation index, see [llms.txt](https://earthlinc.gitbook.io/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://earthlinc.gitbook.io/protocol/build/bring-an-ai-agent.md). # Bring an AI agent *Extend the compose layer — give activities new kinds of living form.* Composing is where AI lives on Earth LinC: a person brings an activity for this earth, and AI gives it form — a **station**, composed into a living page. **NaviCanvas** is the composing surface, and it is open by design: the protocol grows by admitting more ways AI can give an activity form. That could include yours. ## What an agent does An agent offers a way to turn a human activity into a living station page — a new compositional style, a new medium, a new kind of interaction between a person and their page. The person authors; the agent composes. Your capability becomes one of the ways holders give their activity form, inside the protocol. ## Acceptance — open by design **NaviCanvas accepts all agents.** There is no protocol-level gate: no allow-list, no stake, no approval committee. *Which* agents are invoked, and how, is an implementation choice of each surface — outside the protocol itself. ## The integrity boundary — the one HARD rule An agent composes **authored, human-supplied expression** only. It may **never generate, alter, or assert verified ecological fact.** Concretely: * An agent shapes what the person gave it. It does not invent claims that something happened for the earth. * The **verified-fact layer** of any NaviStar is untouchable — agents compose *around* it, never *into* it. * This holds at every level: prompt, pipeline, tooling. An agent that crosses this boundary — however cleverly — **is not conformant**, and surfaces are required to treat it that way. * The same boundary shapes **Navi**, the protocol's own surface: Navi *surfaces*; it never generates verified fact. Your agent lives under the same law. *Why the rule exists:* the protocol's entire value is that a recorded claim is true. An AI that could write fact would dissolve the one thing everything else stands on. ## Interfaces Compose via **NaviCanvas**; surface via **Navi**. Exact APIs ship with the reference implementation (see *Contracts & reference implementation*). ## Start Read the **Protocol Specification** (Part B1 is your section), then write to **** — subject "agent." *** *A protocol anchored by YuCROWN Corporation · 501(c)(3) — anchored, never owned.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://earthlinc.gitbook.io/protocol/build/bring-an-ai-agent.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.