---
title: "Solacia API access"
description: "How an agent gets access to the Solacia REST API and MCP server. A customer account makes API keys in the Solacia console; an MCP client signs a person in by OAuth. There is no self-serve sign-up."
canonical: https://www.solacia.ai/auth.md
last_updated: 2026-11-09
---

# Solacia API access

The Solacia REST API reads one customer account's data: leads, demos, transcripts, questions,
knowledge gaps and demo links. Every call needs a bearer key that belongs to that account. The
account makes its keys in the Solacia console. The MCP server at `https://app.solacia.ai/mcp`
offers the same account to Claude, ChatGPT or any MCP client, with a key or by OAuth. There is no
self-serve sign-up or anonymous access.

The reference is the source of truth for keys, scopes, limits and errors:
https://app.solacia.ai/docs (Markdown: https://app.solacia.ai/docs/index.md).

## Discover

- API base URL: `https://app.solacia.ai/v1`
- Reference: https://app.solacia.ai/docs
- Contract (OpenAPI 3.1): https://app.solacia.ai/docs/openapi.v1.json
- Catalog (RFC 9727): https://www.solacia.ai/.well-known/api-catalog
- MCP server (Streamable HTTP): `https://app.solacia.ai/mcp`
- MCP tools: https://app.solacia.ai/docs/mcp.v1.json
- OAuth protected resource (RFC 9728): https://app.solacia.ai/.well-known/oauth-protected-resource/mcp
- OAuth authorization server (RFC 8414): https://app.solacia.ai/.well-known/oauth-authorization-server

## Pick a method

Two methods exist.

- **API key**, for the REST API and the MCP server: a bearer token. The key says which account it
  reads; no account id goes in the URL.
- **OAuth 2.1**, for the MCP server only: authorization code with PKCE (S256), public clients. A
  client names itself with a Client ID Metadata Document, or registers at
  `https://app.solacia.ai/auth/register`. A member of the customer's account signs in and
  approves the scopes, and the client then acts as that person.

## Register

Only a Solacia customer can get a key. The account's owner makes one in the console, on the Team
page, with a name, the scopes it needs and when it expires. How: https://app.solacia.ai/docs#keys.

## Claim

The console shows the key once. Solacia keeps only a hash of it, so a lost key cannot be shown
again; make a new one or roll the old one.

## Exchange

A key is used as it is. An OAuth client exchanges its code at `https://app.solacia.ai/auth/token`
and refreshes its token there.

## Use the access_token

```sh
curl -H "Authorization: Bearer $SOLACIA_API_KEY" https://app.solacia.ai/v1/account/me
```

Every response carries the rate limit headers and `Solacia-Key-Expires`, the key's end or `never`. Errors are `application/problem+json` with a stable `code`:
https://app.solacia.ai/docs#errors.

## Revocation

The owner revokes a key in the console. It stops working at once. A connected MCP client is
revoked on the console's Team page, under Chatbots, or by the client itself at
`https://app.solacia.ai/auth/revoke`.
