# For agents and developers — Aapollo

There are two different things here. Keep them apart.

## 1. Reading about Aapollo (public, no credentials)

Everything on aapollo.net is public marketing information. Nothing here exposes any centre's data.

- Map for language models: https://aapollo.net/llms.txt (full text: https://aapollo.net/llms-full.txt)
- Any page as Markdown: send `Accept: text/markdown` or add `.md` (for example https://aapollo.net/pricing.md)
- Public JSON API: https://aapollo.net/api/public/product, https://aapollo.net/api/public/pricing, https://aapollo.net/api/public/estimate?activeUsers=40 — described by https://aapollo.net/openapi.json
- Public MCP server: `https://aapollo.net/mcp` (Streamable HTTP, JSON responses, no authentication). Card: https://aapollo.net/.well-known/mcp/server-card.json
- Agent skill: https://aapollo.net/.well-known/agent-skills/aapollo/SKILL.md
- Discovery: https://aapollo.net/.well-known/api-catalog, https://aapollo.net/.well-known/ai-catalog.json, https://aapollo.net/sitemap.xml
- In the browser, the site registers WebMCP tools: `get_product_overview`, `get_pricing`, `estimate_monthly_cost`, `open_page`.

## 2. Connecting an agent to your own centre (private, admin approved)

Centres can let an AI agent work inside their own organisation through the Aapollo MCP server at `https://api.aapollo.net/mcp`.

- Only an organisation admin can allow it, from **Settings → Agents & MCP**.
- Admins choose OAuth approval or a bearer key, pick exactly which permissions the agent gets, and can revoke it at any time.
- Every change an agent makes is recorded in the organisation's audit log.
- Agents must never create accounts or sign in on a person's behalf.
