> 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/expected-outcomes.md). # Expected Outcomes #### Non-Spoofable Identity The specification must provide non-repudiable proof of bot identity and actions, creating a verifiable record that can serve as legal evidence when disputes arise. #### No Discrimination Bots and agents from large corporations shouldn't receive preferential access or rates over smaller organisations. #### Private Browsing Internet was built on the backbone of privacy and we don't want a future where private lanes don't exists. There must be reasonable rate limites to accomodate anonymous bot traffic. #### Open Registry Verification No single entity should monopolize bot authentication and blocking decisions, ensuring the system remains open and resistant to centralized control. #### Runtime Attenuation Origin can dynamically adjust bot permissions during an active session—restricting or expanding access in real-time based on observed behavior, declared intent, and current context without forcing re-authentication. --- # 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/expected-outcomes.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.