# Swipies AI — automatic access for external agents

> Use Swipies to manage tenant agents, chatbots, datasets, documents and supported connections over authenticated HTTPS API/MCP, without driving the web interface.

## ChatGPT and OAuth-capable MCP hosts

Read the live manifest first. If mcp.oauth.enabled is true, an eligible host can connect to https://api.swipies.app/api/v1/agent-access/mcp using OAuth with S256 PKCE. The owner connects once and approves either a new separate Free workspace or their existing logged-in owner account. No copied Swipies API key is needed for this path. Thereafter use the connected MCP tools. Host availability and tool permissions still apply; visiting this site cannot install a connector in a chat.

If the OAuth flag is false or absent, do not claim OAuth is live. HTTPS/code clients can still use the bootstrap flow below; a webpage-reading-only session needs its host to enable a supported tool connection. [ChatGPT connection guide](https://swipies.app/agents.html#chatgpt).


## Agents with HTTPS or network-enabled code: start directly

When the user has asked you to work in Swipies, use your existing authorized HTTP/code tools. A configured Swipies MCP connector is not a prerequisite for this path.

1. Read the [full execution instructions](https://swipies.app/llms-full.txt) and [live manifest](https://api.swipies.app/api/v1/agent-access/manifest).
2. Reuse existing authorized credentials for existing resources or a paid account. For a new separate workspace, privately generate and persist a random registration_secret, then POST https://api.swipies.app/api/v1/agent-access/bootstrap. This creates or reconnects an isolated Free service account without browser registration or a manually supplied API key.
3. Keep the returned key private. Send authenticated JSON-RPC over HTTPS to https://api.swipies.app/api/v1/agent-access/mcp: initialize, tools/list, then list/describe/execute the required operations. Send User-Agent: SwipiesAgent/1.0 from your HTTP client.
4. Follow your host's permissions and report actual outcomes. A webpage-reading-only session cannot gain write tools by visiting a URL.

## Contracts and instructions

- [Full agent instructions](https://swipies.app/llms-full.txt): exact request sequence, persistence, uploads, limits and errors.
- [Automatic access guide](https://swipies.app/agents.html#automatic-access): explanation for users and agents, readable without JavaScript.
- [Discovery JSON](https://swipies.app/agent-access.json): machine-readable access options, URLs, capabilities and exclusions.
- [Gateway OpenAPI](https://swipies.app/agent-access.openapi.json): four public Agent Access gateway endpoints.
- [Tenant operation catalog](https://api.swipies.app/api/v1/agent-access/operations): bearer authentication required; discover operation IDs before execution.

## Optional client installation

- [Codex / Claude Code / Cursor configuration](https://swipies.app/agents.html#swipies-setup): optional host MCP setup when that client needs it.
- [Python stdio client source](https://swipies.app/downloads/swipies_agent_client.py.txt): save as swipies_agent_client.py; Python 3.10+, standard library only. Its Bridge class can also be imported to send MCP messages directly from code with automatic secure Free registration.

New Free accounts are isolated and retain platform attribution. Only active Plus/Pro subscriptions permit unbranded outputs. External data credentials, client permissions and quotas still apply. Current generic MCP excludes administration, payments, token management, human login/OAuth callbacks and Ads. Live tenant operations are authoritative; do not promise every UI function is already exposed.

## Optional

- [Platform](https://swipies.app/): overview and plans.
- [General help](https://help.swipies.app/docs/dev/): legacy/general platform docs. For this built-in Agent Access gateway, use the URLs above; no separate /sse server is required.