> 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/faq.md).

# FAQ

#### Why Web Bot Auth? Not OAuth?

Oauth introduces complexity in implementation. There's an open issue on Thibault's [Github](https://github.com/thibmeu/http-message-signatures-directory/issues/13) discussing this. There another cloudflare project, [OpenPubkey](https://www.bastionzero.com/openpubkey) which works with OIDC and they use an MPC. OpenBotAuth intends to avoid any complex cryptography.&#x20;

#### Why Can't I Sign-in with Facebook/X?

Agents live and die in developer's terminal. Almost all developers have a Github Account and understand the value of hosted services. Developers remain the primary agent builders. Hence it was a no brainer to allow Github Profiles to verify first. We will consider expanding to other verification methods.


---

# 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/faq.md?ask=<question>&goal=<endgoal>
```

`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.
