Get an API Key

Each user runs against their own isolated Talonic workspace. Your documents and schemas are private to you.

1. Sign up at app.talonic.com. Free tier: 50 extractions per day, no credit card.
2. Settings → API Keys → Create New Key.
3. Copy the tlnc_ value into your MCP client config (snippets below).

The API key authenticates every tool call the MCP server makes on your behalf. It is passed as a TALONIC_API_KEY environment variable in the local npx setup, or as a Bearer token in the Authorization header for the hosted server. The key is never sent to the AI agent itself — it stays within the MCP server process.

Keep your API key private. Do not commit it to version control or share it in public MCP config examples. If a key is compromised, revoke it immediately in the Talonic dashboard under Settings → API Keys and generate a new one.

The free tier includes 50 extractions per day, which is enough for development and testing. For production workloads or higher volume, upgrade your plan in the Talonic dashboard. All plans share the same API — the key determines your rate limits and quota.

{
  "mcpServers": {
    "talonic": {
      "command": "npx",
      "args": ["-y", "@talonic/mcp@latest"],
      "env": {
        "TALONIC_API_KEY": "tlnc_your_key_here"
      }
    }
  }
}

{
  "mcpServers": {
    "talonic": {
      "url": "https://mcp.talonic.com/mcp",
      "headers": {
        "Authorization": "Bearer tlnc_your_key_here"
      }
    }
  }
}

After adding your API key to the config, verify the connection by asking your agent to call talonic_list_schemas. If the key is valid, the tool returns your saved schemas (or an empty list if you have not saved any yet). If the key is invalid or missing, the server returns a clear authentication error that tells the agent the key needs to be checked. This is the fastest way to confirm your setup is working end-to-end.

Each API key is scoped to a single workspace. If you work across multiple Talonic workspaces — for example, separate environments for development and production — you will need a different API key for each. You can create multiple keys within the same workspace for different team members or applications, and revoke them independently without affecting other keys.