> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/build/unified-apis/inside-a-category.md).
# Inside a category
Opening a category: entities, connection state, providers and endpoints.
Nothing is connected here yet, and the endpoints are listed anyway. They exist per entity, not per provider.
Opening a category swaps the pane for a detail view with the breadcrumb **Unified APIs / \** and two chips, *N entities* and *N providers*. **The URL does not change when you do this**, so there is no link you can send someone that opens a category directly.
Each entity gets its own block showing:
* **Connection state**: `0/12 connected` on CRM's `Account`, `0/1 connected` elsewhere. How many of the backing providers this customer has authorised.
* **PROVIDERS**: one row per provider, with a **Connect** button, or **Connected** and a `⋯` menu offering **Add another connection** and **Disconnect default**.
* **API**: the endpoints, filtered by an **All providers** selector, each row with **Copy curl**.
Endpoints follow a consistent shape:
```http
GET /api/v1/unified/crm/account?page_size=50
GET /api/v1/unified/crm/account/RECORD_ID
POST /api/v1/unified/crm/account
```
```http
POST /api/v1/unified/crm/note
```
Not every entity supports every verb. `Note` and both Messaging entities (`Channel Message` and `Direct Message`), are create-only.
---
# 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.fastn.ai/build/unified-apis/inside-a-category.md?ask=&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.
