> For the complete documentation index, see [llms.txt](https://docs.continuousauth.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.continuousauth.dev/usage/requesters.md).

# Requesters

In CFA when we refer to a `Requester` we are referring to the part of your build process that would be running `npm publish` this is typically a CI provider such as Circle CI, Travis or Azure Pipelines.  It is the service that will actually be "requesting" the OTP from CFA.

Once you added your repository as a project in CFA you should be able to choose from any of our supported Requesters to configure.  For more information on each Requester, what they validate and how to configure them please check the individual Requester pages.

### I want to use CI provider X but there is not a requester for it?

Check out our [Contributing FAQ](/contributing/faq.md#i-want-to-use-cfa-with-ci-provider-x) for more information on how to add a new requester.  We're always open to new pull requests.


---

# 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.continuousauth.dev/usage/requesters.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.
