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

# AI at social.plus

> Engagement infrastructure for the AI era — answers from your first-party data, docs your coding tools can read, and guardrails for AI agents building on social.plus.

social.plus is the engagement infrastructure behind consumer apps — and every interaction it powers generates first-party data and insight your business owns. AI turns both into leverage. Teams ask their own data questions in the AI apps they already use, and AI coding agents build on the platform with the same grounding a senior integrator would have.

## Three products

<CardGroup cols={3}>
  <Card title="Agentry" icon="comments-question-check" href="/ai/agentry/overview">
    Ask questions about your first-party data in plain language, from the AI apps your team already uses.
  </Card>

  <Card title="Documentation MCP Server" icon="book-open" href="/ai/docs-mcp-server">
    Give your AI coding tool direct access to the social.plus docs while it helps you implement SDK features.
  </Card>

  <Card title="Vise" icon="shield-check" href="/ai/vise/overview">
    Guardrails for AI coding agents building social.plus features — evaluate, build, and verify with confidence.
  </Card>
</CardGroup>

## Which one do you need?

| You want to…                                          | Use                                             |
| ----------------------------------------------------- | ----------------------------------------------- |
| Answers from your first-party data, in plain language | [Agentry](/ai/agentry/overview)                 |
| SDK docs, inside your coding tools                    | [Documentation MCP Server](/ai/docs-mcp-server) |
| AI agents that build social.plus features — verified  | [Vise](/ai/vise/overview)                       |

They compose: build with Vise, keep the docs server connected in every editor, and give marketing and community teams Agentry for the questions that used to become dashboard requests.

## Engagement, insight, intelligence

* **Your data answers back.** Agentry turns the first-party data your app already generates — posts, comments, reactions, users, communities — into a conversation. Read-only, scoped to your own network, authorized by your admins.
* **The docs meet your tools where they are.** The documentation MCP server is a public, no-auth endpoint any MCP-capable tool can read, so assistants cite canonical guidance instead of guessing.
* **Building is verifiable.** Vise gives coding agents the project knowledge and verification steps to implement features that pass review, not just compile.

Owned engagement compounds: the experiences you power create the data, the data powers the answers, and the answers sharpen what you build next.