> For the complete documentation index, see [llms.txt](https://docs.mikopbx.com/mikopbx-development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mikopbx.com/mikopbx-development/internal-structure.md).

# Internal structure

- [Admin interface](https://docs.mikopbx.com/mikopbx-development/internal-structure/admin-interface.md): Architecture of the MikoPBX admin-cabinet web application.
- [API](https://docs.mikopbx.com/mikopbx-development/internal-structure/api.md): Overview of MikoPBX APIs and integration surfaces — REST API v3, AMI/AJAM, AGI, and the legacy module REST callback — with guidance on when to use each.
- [REST API](https://docs.mikopbx.com/mikopbx-development/internal-structure/api/rest-api.md): The MikoPBX PBXCoreREST API: v3 architecture, auth, routing and async processing.
- [AMI / AJAM](https://docs.mikopbx.com/mikopbx-development/internal-structure/api/ami-ajam.md): Interacting with Asterisk via AMI (TCP 5038) and AJAM (HTTP).
- [AGI](https://docs.mikopbx.com/mikopbx-development/internal-structure/api/agi.md): MikoPBX implementation of the PHP-AGI library and how to write AGI scripts that hook into the Asterisk dialplan from a module.
- [Core](https://docs.mikopbx.com/mikopbx-development/internal-structure/core.md): Architecture overview of the MikoPBX core engine: the six MikoPBX\ namespaces, the Phalcon 5 / SQLite / Redis platform, and the core data-model graph.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mikopbx.com/mikopbx-development/internal-structure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.