Introduction

The Sybill API provides programmatic access to your Sybill workspace — conversations, insights, and AI-powered analysis — via standard REST endpoints and an MCP interface for AI assistants.

Alpha Notice

The Sybill API is currently in alpha. Endpoints, request/response schemas, rate limits, and behavior may change at any time without prior notice. We recommend against building production-critical integrations until the API reaches a stable release.

Base URL

https://api.sybill.ai

Quick start

  1. Create an API key from the Sybill dashboard (Settings → Integrations → API Keys).
  2. Make your first request:
curl -H "Authorization: Bearer sk_live_YOUR_KEY" \
  https://api.sybill.ai/v1/health

A successful response looks like:

{
  "status": "ok",
  "org_id": "your-org-id",
  "scopes": ["read"]
}

Available interfaces

InterfaceURLDescription
REST APIhttps://api.sybill.aiRead organization-visible conversations, deals, accounts, messages, rows, and documents, and import your own records via standard HTTP
MCPhttps://mcp.sybill.ai/mcpModel Context Protocol server for AI assistants (Claude, Cursor, etc.)

Data visibility and processing

REST API keys operate with organization-level context rather than as a specific Sybill user. Read endpoints return records that are visible to the organization; they do not return private records owned by individual users. The MCP server uses the signed-in user's Sybill access.

Records imported through POST endpoints are private by default and require at least one valid ownerEmails entry. Set public: true when the record should be visible through REST read endpoints.

An import response confirms that Sybill stored the record and accepted it for asynchronous processing. Transcription, document conversion, summaries, and other derived fields may not be available immediately.

Next steps