# Antidote Services

The Antidote platform is composed of two services:

* `antidote-web`
* `antidoted`

Antidote-Core is where the real work gets done in the Antidote project. It's responsible for taking in lesson definitions via [a YAML file](/antidote/object-reference/lessons.md) and any configs, scripts, etc used in the lesson, and providing them to the front-end via its API.

## Configuring Antidote

Antidote is configured through a YAML file. Since typically Antidote is deployed within Kubernetes, the ideal way to do this is through a ConfigMap.

If you're using [antidote-selfmedicate](https://github.com/nre-learning/antidote-selfmedicate) to spin up an instance of Antidote yourself, a configuration file is provided for you.

(should have a sample config file in the antidote-core repo, and just link to it here)


---

# Agent Instructions: 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.nrelabs.io/antidote/antidote-architecture/antidote-web.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.