Skip to main content
Sample widgets and the API starter app need no account. Live data needs one of these credentials.

Create an account

Sign up and verify your email. Keep the account active: while it is inactive or unverified, its API keys and MCP sign-in stop working.

Get a partner account

An active partner account adds widget approval, webhook management, and its partner tier’s key count and request quota.

Widget ID

A widget ID lists the sites allowed to show your live widgets. It is not an API key and is safe in your page source. Embed a widget walks through creating one.

API keys

  1. Create an account and verify your email.
  2. Create a key in API key settings.
  3. Store it on your server, for example in a CENTAUR_API_KEY environment variable.
  4. Send it in the x-api-key header of every request.
New keys get every read scope, plus webhooks.manage when the account is an active partner. You can have up to five active keys, or your partner tier’s count. Revoke keys in API key settings. Errors and limits covers request allowances and account errors.

AI-agent sign-in

MCP uses OAuth sign-in, not API keys.
  1. Create an account and verify your email.
  2. Add the Centaur server to your AI client with Connect an AI agent.
  3. Sign in to Centaur when the client asks.
Review or revoke authorized clients in Connected Apps. The Telegram bot is separate and grants no API or MCP access.

Scopes

Scopes decide which endpoints a key or AI client can call. Data reads lists the scope of each read.
Last modified on October 26, 2026