> For the complete documentation index, see [llms.txt](https://docs.openbotauth.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbotauth.org/readme.md). # OpenBotAuth OpenBotAuth enables agents to access the web by proving identity, intent and paying for content. By logging in with Github, developers can host their agent keys for Web Bot Auth on the registry, skipping buying a domain, DNS verification or identity verification with a CDN. Registry tracks your agent telemetry over HTTP. Publishers and Indie websites can point to the registry to block unverified scrapers and monetize legitimate agent traffic directly. We've a WordPress plugin available today, with other platform support in the works. Works with browsers like BrowserBase, Onkernel, AgentCore, and agent frameworks like Langchain, OpenAI, Mastra, etc. by adding custom HTTP header. We'd love your contribution to the open problems. Please visit our [Research Page](https://openbotauth.discourse.group/) or take a quick look at [Open Research Problems](https://docs.openbotauth.org/open-research-problems). If you haven't already, create an account on the [OpenBotRegistry](https://openbotauth.org/login). --- # 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://docs.openbotauth.org/readme.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.