CertuAI API and MCP

The CertuAI API lets a program or an AI agent operate a CertuAI account: the AI that answers the business WhatsApp, conversations, the knowledge base, CRM, calendar, business records, ads and the Google Business Profile. The same tools answer over REST and over MCP.

REST base

https://certuai.com/api/v1

MCP endpoint

POST https://certuai.com/api/v1/mcp

OpenAPI 3.1

https://certuai.com/openapi.json

Auth

Authorization: Bearer certu_sk_...

Sandbox

Test keys (certu_sk_test_...) read real data and simulate every write

Limits

60/min per key · 5 active keys · 2,000 calls/day per account

Start

7 days free, no card. Create an account · Plans

When to use the CertuAI API

Use it when a person or an agent needs to run a small or medium business that answers customers on WhatsApp:

• Build the AI that answers the business WhatsApp from an interview with the owner, then test its replies (agente_criar, agente_testar).
• Read recent WhatsApp conversations and a full conversation history (conversas_listar, conversa_ler).
• Teach or fix what the AI knows: knowledge base entries and products (cerebro_*, produto_salvar).
• Run the calendar: list, book, reschedule, confirm, cancel and block time (agenda_*). The customer is not notified by the API.
• Work the CRM pipeline, contacts and tasks (crm_*), and read phone calls with transcripts (ligacoes_listar, ligacao_ler).
• Keep business records: stock, cash book, monthly result, orders and payment requests (erp_*, pedido*, cobranca*).
• Prepare ads: generate a campaign kit, publish it paused, read results, pause it or change its budget (anuncio*).
• Draft and publish replies to Google reviews (google_*). Partners manage their client accounts with conta.

Not a fit

• Sending messages to customers: no tool sends WhatsApp, email or SMS to a customer.
• Turning on ad spend: campaigns are always created paused and there is no tool that activates one.
• Connecting the WhatsApp number or paying: the owner does that in the app.
• Bulk or cold messaging of any kind.

Get started in three steps

1. Create an account. It starts with 7 days free, no card: https://certuai.com/create-my-agent.
2. Create a key in the app, under Settings, Connect to Claude. It starts with certu_sk_ and is shown once. Step-by-step guide: https://certuai.com/claude.
3. Call the API with Authorization: Bearer <key>. Start with GET /conta, which says what the plan includes.

Authentication

Every request carries the key in the Authorization: Bearer header. A key in the URL is refused (chave_na_url).

The key operates the account that created it. Keys are self-serve: the owner creates and revokes them in the app, with no approval step.

The claude.ai connector signs in with OAuth instead of a key. Discovery: /.well-known/oauth-protected-resource.

Test keys (sandbox) and scopes

A test key (certu_sk_test_...) reads the real account and simulates every write: parameters are validated exactly as in production, and the answer is {"sandbox": true, "simulado": true, ...} with nothing saved, no credits spent and nothing sent. Responses carry the header Certu-Modo: teste.

Test keys and scoped keys are created at POST /api/v1/keys, authenticated by the app sign-in (not by another key). Scopes are area:ler (read) or area:escrever (write, which includes read), plus area:*, *:ler and *. Areas: conta, conversas, cerebro, agente, anuncios, site, agenda, erp, ligacoes, crm, google, parceiro, webhooks, cobrancas, pets, imoveis, fiscal, clinica.

POST https://certuai.com/api/v1/keys
{"nome": "Sandbox integration", "teste": true, "escopos": ["crm:ler", "agenda:escrever"]}

Limits and errors

• 60 requests per minute per key (headers X-RateLimit-Limit and X-RateLimit-Remaining; a 429 carries Retry-After).
• 5 active keys and 2,000 tool calls per day per account, across all keys. Request body up to 1 MB.
• Every action still follows the account plan and credits. Read GET /conta first so you do not promise something the plan does not include.
• Errors are JSON with the HTTP status. Rely on the error code; the message text explains it.

MCP server

Endpoint: POST https://certuai.com/api/v1/mcp. Streamable HTTP, stateless, JSON responses only (no SSE); GET answers 405. Protocol versions: 2025-11-25, 2025-06-18, 2025-03-26.

Methods: initialize, ping, tools/list, tools/call. The 65 tools are the same operations as the REST API.

In claude.ai or the Claude app, add a custom connector with the address https://certuai.com/api/v1/mcp and sign in; no key needed. Full guide: https://certuai.com/claude.

Claude Code

claude mcp add --transport http certuai https://certuai.com/api/v1/mcp --header "Authorization: Bearer YOUR_KEY"

Cursor and other MCP clients

{
  "mcpServers": {
    "certuai": {
      "url": "https://certuai.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Examples

Account summary: plan, credits and what the plan includes

curl https://certuai.com/api/v1/conta \
  -H "Authorization: Bearer $CERTUAI_KEY"

Confirmed bookings for a week

curl "https://certuai.com/api/v1/agenda?de=2026-10-12&ate=2026-10-18&status=confirmado" \
  -H "Authorization: Bearer $CERTUAI_KEY"

Teach the AI one fact (with a test key, this is simulated and nothing is saved)

curl -X POST https://certuai.com/api/v1/cerebro \
  -H "Authorization: Bearer $CERTUAI_KEY" \
  -H "Content-Type: application/json" \
  -d '{"titulo": "Opening hours", "conteudo": "Monday to Friday, 9am to 6pm."}'

List the MCP tools

curl -X POST https://certuai.com/api/v1/mcp \
  -H "Authorization: Bearer $CERTUAI_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

Acting on another account

A partner, an owner of more than one business or an admin of another account passes conta (query string, or in the body of a POST) to act on that account. GET /parceiro/clientes lists the accounts the key can reach. Without conta, the call acts on the key owner's account.

Webhooks

Outgoing webhooks live at /api/v1/webhooks (scope webhooks:ler / webhooks:escrever) and are part of the enterprise API, enabled per account. Events: mensagem.recebida, conversa.transferida_humano, contato.criado, negocio.criado, ligacao.concluida.

REST endpoints

All paths are relative to https://certuai.com/api/v1. Parameters, request bodies and schemas are in the OpenAPI spec.

More for agents and developers

• OpenAPI 3.1 spec
• llms.txt
• Connect Claude to CertuAI
• Pricing