# Connect your own AI agent

> Let your own AI agent (Claude, ChatGPT, an IDE assistant or an in-house agent) work with your workspace over MCP with OAuth, or call the REST API with a token.

There are two different agent endpoints. The **public guide** answers questions about this content without any
account. The **workspace MCP endpoint** gives an agent your own finance data and tools, after you sign in and
allow it.

## Public guide (no account)

An agent that needs to find a guide, a course or a formula can ask our guide agent:

- MCP: `/agent/mcp` with the tools `content.search`, `content.read`, `content.list` and `platform.connect`
- A2A: the agent card at `/.well-known/agent-card.json`
- HTTP: `/agent/ask?q=...`, described at `/agent/openapi.json`
- Plain files: `/llms.txt`, and any page as Markdown by adding `.md` to its address

See [For AI agents](/learn/agents) for the full list.

## Your workspace over MCP

1. Add the platform's MCP address (`/mcp` on your platform's address) to your MCP host.
2. The host discovers the sign-in server by itself (OAuth protected resource metadata) and registers.
3. You sign in, pick a workspace you own and allow the app. The consent page warns you when an app registered
   itself.
4. The agent can now read figures and create drafts with the same tools our assistant uses. It cannot approve,
   pay, file taxes or delete anything, and every tool call is in the audit log.
5. Disconnect the app at any time under **Settings → Apps**.

## REST API and tokens

An owner can create a workspace API token under **Settings → API tokens** with scopes (`read`, `edit_records`,
`edit_model`, `view_audit`) and an expiry. The token works for the REST API (`/api/v1`) and in an MCP client
configured by hand. The contract is published at `/api/openapi.yaml`. Apps used by other people should register
as an OAuth app instead.

## Webhooks

Owners can register an endpoint to receive signed events, such as an approved forecast, with retries.