# APIANT.ai for agents

APIANT.ai is a hosted integration and automation platform operated by AI agents. You describe an integration or automation in plain language, to the in-app assistant or to your own AI client over MCP, and the agent connects the apps, builds the automation, tests every scenario before it ships, then keeps it running and reports failures. Automations are stored as data, not as code. Free for everyone to start.

This file tells an AI agent how to work with APIANT.ai. The human-readable site is https://apiant.ai.

## Connect over MCP

- Server: `https://mcp.apiant.ai`, a remote MCP server over Streamable HTTP. Nothing to install.
- Sign-in: OAuth with PKCE. The client opens APIANT's sign-in in the user's browser (multi-factor authentication included when the user has it on) and receives its own token. The user's password never reaches the client.
- Scopes: `mcp:tools` and `mcp:automation_builder`.
- Discovery: the server answers an unauthenticated request with `WWW-Authenticate` pointing at its protected resource metadata, https://mcp.apiant.ai/.well-known/oauth-protected-resource. The authorization server is https://app.apiant.ai.
- Setup, step by step for Claude Code: https://apiant.ai/docs/mcp/claude-code
- How an agent signs in (endpoints, dynamic client registration, PKCE, token lifetimes): https://apiant.ai/auth.md
- Authentication and permissions: https://apiant.ai/docs/mcp/authentication
- MCP Registry: published as `ai.apiant/apiant`, verified against apiant.ai: https://registry.modelcontextprotocol.io/v0/servers?search=ai.apiant/apiant (also on Glama: https://glama.ai/mcp/connectors/ai.apiant/apiant)
- Server card: https://apiant.ai/.well-known/mcp/server-card.json
- Agent skill: https://apiant.ai/.well-known/agent-skills/apiant/SKILL.md (index: https://apiant.ai/.well-known/agent-skills/index.json)
- Claude plugin: https://github.com/APIANT/apiant-plugins. In Claude Code, run `/plugin marketplace add APIANT/apiant-plugins`, then `/plugin install apiant@apiant`. It connects Claude to the same MCP server.

Once connected, the agent can search the app catalog, connect the user's accounts, build a connector from an app's API documentation, build and test automations, read execution history and retry runs. The procedures it follows (skills) are delivered over the MCP connection itself.

## Get an account

The user needs an APIANT account. There is a free plan, and signing up is self-serve: https://app.apiant.ai/register (https://app.apiant.ai/signup redirects there). The free plan needs no credit card. Paid plans are picked in billing after sign-up; plans and prices are at https://apiant.ai/pricing.md.

## What to read

- https://apiant.ai/llms.txt: what APIANT is, when to use it and when not to, and the main pages
- https://apiant.ai/apps/llms.txt: the app catalog by category, and how to reach any app or pair page
- https://apiant.ai/docs/llms.txt: every documentation page with a one-line summary
- https://apiant.ai/docs: the documentation
- https://apiant.ai/pricing.md: plans and prices
- https://apiant.ai/mcp.md: the MCP server page

## Markdown versions of every page

Every content page is also served as Markdown. Add `.md` to its address, or request the page with `Accept: text/markdown`:

- https://apiant.ai/index.md, https://apiant.ai/pricing.md, https://apiant.ai/about.md
- https://apiant.ai/apps.md and https://apiant.ai/apps/{category}.md
- https://apiant.ai/connections/{app}.md, for example https://apiant.ai/connections/slack.md
- https://apiant.ai/connect/{from}-to-{to}.md, for example https://apiant.ai/connect/slack-to-hubspot.md

HTML pages that have a Markdown version name it in `<link rel="alternate" type="text/markdown">`.

## In the browser

When the browser supports WebMCP, pages on apiant.ai register three read-only tools: `search_apps`, `get_pricing` and `get_mcp_setup`. They read the site's own pages and change nothing.

## Discovery files

- https://apiant.ai/.well-known/ai-catalog.json: Agentic Resource Discovery catalog, with the MCP server card inline (also at https://apiant.ai/.well-known/ard.json)
- https://apiant.ai/.well-known/api-catalog: API catalog (RFC 9727) linking the OpenAPI description and docs
- https://apiant.ai/.well-known/mcp/server-card.json: MCP server card
- https://apiant.ai/openapi.json: OpenAPI 3.1 description of the public app catalog feed (https://app.apiant.ai/catalog/v1, no authentication) and of the MCP server's OAuth security scheme and scopes
- https://apiant.ai/sitemap.xml
- https://apiant.ai/robots.txt

## Ground rules

- Building or changing automations happens in the user's own APIANT account, through MCP or the in-app assistant, after the user signs in. The public site takes no actions.
- If an app has no API documentation the agent can read, APIANT stops rather than guessing endpoints.
- Support: https://apiant.ai/support