> For the complete documentation index, see [llms.txt](https://docs.rivalz.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rivalz.ai/adcs-ai-oracles/how-to-become-a-provider.md).

# How to Become a Provider

### METHOD 1: Self-hosted Service

* Fork our repository [here](https://github.com/Rivalz-ai/ADCS-core)
* Add information about your provider [here](https://github.com/Rivalz-ai/ADCS-core/blob/main/open/endpoints.json)
* Add your service endpoint, parameters, and expected output
* Create a Pull Request to the ADCS repository We will review your PR and respond accordingly. After the PR is merged, you will become a provider.

### METHOD 2: Use Our Hosted Service

* Fork our repository [here](https://github.com/Rivalz-ai/ADCS-core)
* Implement your custom service under the [inference](https://github.com/Rivalz-ai/ADCS-core/tree/main/inference/blueprints) folder
* Add information about your service in [descriptions.json](https://github.com/Rivalz-ai/ADCS-core/blob/main/inference/descriptions.json)
* Create a Pull Request to the ADCS repository
* We will review your PR and respond accordingly. After the PR is merged, you will become a provider.


---

# 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:

```
GET https://docs.rivalz.ai/adcs-ai-oracles/how-to-become-a-provider.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.