API Introduction

Overview

The GC AI External API allows you to integrate GC AI’s legal AI capabilities into your workflows and applications. Perfect for:

Workflow automation with tools like Zapier, Make, or n8n
Custom integrations in your internal tools
Batch processing of legal questions
Chatbots and assistants powered by legal AI

This is programmatic access with API keys. For connecting your own email, Slack, Drive, and other apps inside GC AI chat (with per-user OAuth and approval controls), see Agent Connectors.

Multi-turn Conversations

Conversations can span multiple turns. Pass the chat_id returned by a completion back on your next request to continue the same chat — see Multi-turn Conversations.

Current Limitations

Interactive clarification is not yet available: the model can’t pause mid-completion to ask you a follow-up question.

Base URL

All API requests should be made to:

https://app.gc.ai/api/external/v1

Authentication

All requests require an API key in the Authorization header:

Authorization: gcai_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

GC AI supports two scopes: organization and personal. Learn which to use and how to govern them.

Getting an API Key

Which scope you create depends on whether the integration belongs to the company or to a person (see API Keys). For a company-owned integration (organization key): an org admin opens Settings → API → Organization API Keys and clicks + Create API Key. This needs no org-wide policy change. For an individual’s own access (personal key):

An org admin opens Settings → API and enables Allow team to create personal API keys (User API Keys Policy).
Each user opens Settings → API → Personal API Keys and clicks + Create API Key.

Either way, copy and securely store the key. It is only shown once.

Keep your API key secure. Anyone with your API key can make requests on behalf of your organization.

Quick Start

Here’s a simple example using curl:

curl -X POST https://app.gc.ai/api/external/v1/chat/completions \
  -H "Authorization: gcai_your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "What are the key terms to look for in a software license agreement?",
    "file_ids": ["123e4567-e89b-12d3-a456-426614174000"]
  }'

Response:

{
  "job_id": "123e4567-e89b-12d3-a456-426614174000",
  "kind": "chat/completions",
  "status": "succeeded",
  "result": {
    "result": "When reviewing a software license agreement, key terms to examine include:\n\n1. **License Grant** - Understand the scope of rights granted...",
    "chat_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  },
  "error": null,
  "created_at": "2026-04-30T20:00:00.000Z",
  "completed_at": "2026-04-30T20:00:02.000Z"
}

Usage

Usage is tracked and viewable in the GC AI app under Settings → API → View Usage. The API is free to test.

Rate Limits

The API is rate-limited in two tiers: inference endpoints (chat completions, playbook runs) are capped at 60 requests per minute per organization (20 per API key), and all other endpoints at 600 requests per minute per organization (120 per API key). Exceeding a limit returns 429 Too Many Requests with a Retry-After header. See Rate Limits for the full breakdown.

Support

For API support, reach out to your account representative.

REST

MCP

CLI

API Introduction

Overview

Multi-turn Conversations

Current Limitations

Base URL

Authentication

Getting an API Key

Quick Start

Usage

Rate Limits

Support

​Overview

​Multi-turn Conversations

​Current Limitations

​Base URL

​Authentication

​Getting an API Key

​Quick Start

​Usage

​Rate Limits

​Support

Overview

Multi-turn Conversations

Current Limitations

Base URL

Authentication

Getting an API Key

Quick Start

Usage

Rate Limits

Support