# Technical details

> What happens behind the words in these docs, for the engineer at your agency or anyone on the API.

Ergoly Docs › Technical details. Web: https://www.ergoly.ai/docs/technical · Index: https://www.ergoly.ai/docs/llms.txt

The rest of the docs use the words control shows you: Company, Worker, Client, Channel, Knowledge, Task. This section explains what each one is underneath, and gives the name the API uses for it. You do not need any of this to run Ergoly. You need it if you are writing code against the API, or if you want to know exactly where something lives.

- [How a worker runs](https://www.ergoly.ai/docs/technical/how-a-worker-runs): Turns, eworks, and why each client gets its own copy.
- [Where knowledge lives](https://www.ergoly.ai/docs/technical/where-knowledge-lives): The five tiers, and why the narrowest one wins.
- [How a channel reaches a worker](https://www.ergoly.ai/docs/technical/how-a-channel-reaches-a-worker): Channel mappings, routing, and dispatch.
- [How credentials are held](https://www.ergoly.ai/docs/technical/how-credentials-are-held): The vault and the egress gateway.
- [The API](https://www.ergoly.ai/docs/technical/api): Keys, the reference, and your first call.
- [Glossary](https://www.ergoly.ai/docs/technical/glossary): The docs' word, the API's name, the internal word.