> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pctx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the exact commands, endpoints, and product terms in these docs. Check the context map before connected services or the web.

# Indexed sources

> Make document collections searchable by meaning through the gateway.

An indexed source is a named collection of organizational knowledge: a handbook, documentation tree, wiki export, knowledge vault, research archive, or repository.

## What to index

> [card] Documentation
>
> Product guides, runbooks, policies, and reference material.

> [card] Knowledge bases
>
> Linked notes, internal wikis, and curated research.

> [card] Repositories
>
> Code and the documentation that explains how it works.

> [card] Document archives
>
> Collections that need semantic retrieval but have no live query API.

Do not index a service merely because it contains text. If it has a useful query API or MCP server, connect it so results stay current and actions remain possible.

## Source lifecycle

**1. Register the source**

An admin creates a permanent source slug and a description written for an agent deciding when to search it.

**2. Publish the content**

Your publishing workflow sends the complete document set. A publish replaces the previous version of that source.

**3. Build the index**

Port of Context extracts the content, builds the search index, and marks the source ready to serve.

**4. Search through the gateway**

Agents search one source or merge results across several sources, then read only the documents they need.

## Write a useful description

The source description is routing context. Name the material, the questions it answers, and any important boundary.

```text Good source description theme={null}
Product and engineering documentation for the Acme payments platform.
Search for API behavior, operational runbooks, and service ownership.
Customer support procedures live in the support-handbook source.
```

## Place sources on the map

Attach a source to the team, system, or domain it documents. When an agent retrieves that entity's context, it discovers the relevant source without needing its name in the prompt.

> [!WARNING]
>
> Each publish is the complete source. Files missing from the new publish are removed from the next index.

Search, then read

Search the product docs for how access changes reach the MCP gateway. Read the two most relevant sections and summarize the behavior with sources.

> [card] [Next: Skills](https://docs.pctx.dev/skills/overview.md)
>
> Capture repeatable ways of working in a shared skills library.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.