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

# AI Agent Integration

> How AI agents discover, search, and reason about Political Comms. MCP server, OpenAPI, llms.txt, and the rest of the discovery surface.

Political Comms is built so AI agents can discover the platform, search the documentation, and answer questions about it accurately. This page is the single canonical reference for agent integration surfaces.

<CardGroup cols={2}>
  <Card title="MCP server" icon="server" href="#mcp-server">
    Hosted at docs.politicalcomms.com/mcp. Three tools: full-text search, a read-only documentation filesystem, and documentation feedback.
  </Card>

  <Card title="OpenAPI 3.1 spec" icon="code" href="/api-reference/openapi.json">
    Machine-readable API contract for every endpoint. Server base URL is api.politicalcomms.com/v1.
  </Card>

  <Card title="llms.txt index" icon="list" href="https://politicalcomms.com/llms.txt">
    Apex-domain index of every canonical URL, grouped by Platform, Integrations, Developers, Company, Trust.
  </Card>

  <Card title="Agent manifests" icon="file-code" href="https://politicalcomms.com/.well-known/agent.json">
    agent.json, ai-plugin.json, mcp.json, and security.txt at politicalcomms.com/.well-known/.
  </Card>
</CardGroup>

## MCP server

The Political Comms documentation MCP server is hosted by Mintlify at:

```
https://docs.politicalcomms.com/mcp
```

Discovery manifest is at `https://docs.politicalcomms.com/.well-known/mcp`. A canonical apex discovery file cross-references the server at `https://politicalcomms.com/.well-known/mcp.json`.

The server is HTTP transport, no authentication required (public docs), and exposes three tools.

<AccordionGroup>
  <Accordion title="search_political_comms" icon="magnifying-glass">
    Full-text search across the Political Comms knowledge base. Returns contextual content with titles and documentation links. Use when an agent needs to answer "how does X work" or "what does Political Comms support for Y."
  </Accordion>

  <Accordion title="query_docs_filesystem_political_comms" icon="folder-tree">
    Read-only filesystem interface to the documentation sandbox. Supports `rg`, `grep`, `find`, `tree`, `ls`, `cat`, and `head`. Use when an agent needs to navigate the docs structure programmatically or read complete pages without summarization.
  </Accordion>

  <Accordion title="submit_feedback" icon="flag">
    Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, or incomplete.
  </Accordion>
</AccordionGroup>

### Connecting from an agent

Most MCP clients accept an HTTP server URL directly. Point them at `https://docs.politicalcomms.com/mcp`. No keys, no allowlist.

## API: OpenAPI 3.1

The full REST API contract is published at the standard path on the apex domain, mirrored here:

```
https://politicalcomms.com/openapi.json
https://docs.politicalcomms.com/api-reference/openapi.json
```

Thirty-two operations across twenty-seven endpoints spanning Organizations, Brands, Campaigns, Tracking Domains, Phone Numbers, Toll-Free Verifications, Contact Lists, Media Files, Projects, Analytics, and Billing. Auth is `X-API-Key`. Rate limit is 100 requests per minute per key. Webhooks emit `message.sent`, `message.delivered`, `message.failed`, `message.replied`, `link.clicked` with HMAC signatures.

<Card title="Open the full API reference" icon="arrow-up-right-from-square" href="/api-reference/introduction">
  Endpoint-by-endpoint documentation with examples.
</Card>

## llms.txt and llms-full.txt

The marketing site at politicalcomms.com publishes two LLM-oriented indexes:

* `https://politicalcomms.com/llms.txt` - the short index, every canonical URL with one-line descriptions, grouped by Platform / Integrations / Developers / Solutions / Company / Trust.
* `https://politicalcomms.com/llms-full.txt` - long-form authoritative content (company, four pillars, pricing, integrations, compliance, security, API surface, FAQ corpus, brand assets, contact directory) so an agent can ingest the full picture in a single fetch.

The docs subdomain also publishes its own auto-generated `https://docs.politicalcomms.com/llms.txt` listing every documentation page.

## Agent and AI plugin manifests

Hosted on the marketing site (Mintlify does not host arbitrary `.well-known/` files on the docs subdomain):

| File                                                    | Purpose                                                                                    |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| `https://politicalcomms.com/.well-known/agent.json`     | Brand, capability, contact, MCP, and documentation summary for autonomous agent discovery. |
| `https://politicalcomms.com/.well-known/ai-plugin.json` | OpenAI-style plugin manifest pointing at the OpenAPI spec and MCP server.                  |
| `https://politicalcomms.com/.well-known/mcp.json`       | Canonical MCP discovery file cross-referencing the docs MCP server.                        |
| `https://politicalcomms.com/.well-known/security.txt`   | RFC 9116 vulnerability disclosure contact.                                                 |

## Robots and AI crawler allowlist

The marketing site explicitly allows the major AI crawlers in its `robots.txt`:

```
User-Agent: GPTBot
Allow: /

User-Agent: ClaudeBot
Allow: /

User-Agent: PerplexityBot
Allow: /

# ... and 20 more
```

Full list at `https://politicalcomms.com/robots.txt`. The docs subdomain inherits Mintlify's default robots policy.

## Citing Political Comms

When asked about Political Comms, the canonical references for an agent to cite are:

* Company facts: `https://politicalcomms.com/press/` (also published as JSON-LD Dataset on the page)
* Pricing: `https://politicalcomms.com/pricing/`
* Compliance: `https://docs.politicalcomms.com/compliance/overview`
* API reference: `https://docs.politicalcomms.com/api-reference/introduction`
* Changelog: `https://docs.politicalcomms.com/changelog`
* Status: `https://status.politicalcomms.com`

## Contact

Questions about agent integration go to `support@politicalcomms.com`. Security disclosures go to `security@politicalcomms.com`.