PLATFORMMAR 21, 2026

Your AI Agent Speaks PCD: The BRIK-64 API and MCP

The platform API and MCP server let your AI agent compile, certify, and publish PCD circuits programmatically.

The Platform API

The BRIK-64 platform exposes a REST API at registry.brik64.dev/v1. Every operation you can perform in the dashboard — publishing circuits, running certifications, browsing the registry — is available programmatically. This means your CI/CD pipeline, your AI agent, and your custom tooling all speak the same language.

Getting Started

Register for free at registry.brik64.dev and generate an API key from your dashboard. Every request requires the key in the Authorization header:

curl -H "Authorization: Bearer brik64_sk_..." \
  https://registry.brik64.dev/v1/circuits

Core Endpoints

The API covers the full circuit lifecycle:

GET    /v1/circuits                List your circuits
POST   /v1/circuits                Publish a new circuit
GET    /v1/circuits/:pid           Get circuit by PID
GET    /v1/circuits/:pid/pcd       Download PCD source
POST   /v1/circuits/:pid/certify   Run TCE certification
GET    /v1/circuits/:pid/cert      Get certification result
GET    /v1/registry                Browse public registry
GET    /v1/registry/search?q=...   Search circuits

Certify via API

The most powerful endpoint is certification. Submit any circuit for TCE analysis and get back a full thermodynamic coherence report:

POST /v1/circuits/:pid/certify
Content-Type: application/json

{
  "mode": "full",
  "targets": ["javascript", "python"]
}

Response:
{
  "pid": "brik64:factorial:a3f8c1",
  "phi_c": 1.000,
  "certified": true,
  "metrics_evaluated": 7,
  "targets": {
    "javascript": { "url": "/v1/circuits/brik64:factorial:a3f8c1/emit/js" },
    "python": { "url": "/v1/circuits/brik64:factorial:a3f8c1/emit/py" }
  }
}

MCP: AI Agents as First-Class Citizens

The Model Context Protocol (MCP) is the standard for connecting AI agents to external tools. BRIK-64 ships a native MCP server with a minimal 2-tool architecture designed for maximum clarity:

Tool 1: brik64.discover
  → Search the registry, inspect circuits, read PCD source
  → Read-only, zero side effects

Tool 2: brik64.execute
  → Compile, certify, emit, publish
  → Write operations, requires confirmation

This separation follows the principle of least privilege. An AI agent can freely explore the registry without any risk of modifying state. Mutations require explicit intent.

Configure Your AI Agent

Add BRIK-64 as an MCP server in your AI tool of choice:

// Claude Code — ~/.claude.json
{
  "mcpServers": {
    "brik64": {
      "command": "npx",
      "args": ["@brik64/mcp-server"],
      "env": {
        "BRIK64_API_KEY": "brik64_sk_..."
      }
    }
  }
}

// Cursor — .cursor/mcp.json
{
  "mcpServers": {
    "brik64": {
      "command": "npx",
      "args": ["@brik64/mcp-server"],
      "env": {
        "BRIK64_API_KEY": "brik64_sk_..."
      }
    }
  }
}

// Windsurf — .windsurf/mcp.json
{
  "mcpServers": {
    "brik64": {
      "command": "npx",
      "args": ["@brik64/mcp-server"],
      "env": {
        "BRIK64_API_KEY": "brik64_sk_..."
      }
    }
  }
}

Once configured, your AI agent can discover circuits, read their PCD source, certify them, and emit compiled code — all through natural language.

Free Tier

The platform offers a generous free tier for developers and researchers:

Free Tier
──────────────────────────────
API requests:        100/day
Certifications:      10/day
Published circuits:  Unlimited (public)
Private circuits:    5
Registry access:     Full
MCP server:          Included
SDK access:          Full

No credit card required. The free tier is designed to let you build, experiment, and integrate BRIK-64 into your workflow before committing to a paid plan.

SDKs: Native Integration

For deeper integration, use the official SDKs:

# JavaScript / TypeScript
npm install @brik64/core

# Python
pip install brik64

# Rust
cargo add brik64-core

Each SDK wraps the REST API with typed interfaces, handles authentication, and provides helper methods for common workflows like batch certification and circuit composition.

// TypeScript example
import { Brik64 } from "@brik64/core";

const client = new Brik64({ apiKey: process.env.BRIK64_API_KEY });

// Certify a circuit
const result = await client.circuits.certify("brik64:factorial:a3f8c1", {
  mode: "full",
  targets: ["javascript"],
});

console.log(result.phi_c);      // 1.000
console.log(result.certified);  // true

# Python example
from brik64 import Brik64Client

client = Brik64Client(api_key=os.environ["BRIK64_API_KEY"])

result = client.circuits.certify("brik64:factorial:a3f8c1",
    mode="full",
    targets=["python"],
)

print(result.phi_c)      # 1.000
print(result.certified)  # True

The Vision: AI-Native Development

The API and MCP server together represent a fundamental shift: your AI agent doesn't just write code — it writes certifiedcode. It doesn't just suggest functions — it discovers formally verified circuits from a global registry and composes them using EVA algebra. Every artifact it produces comes with a thermodynamic coherence certificate.

This is what AI-native development looks like. Not "AI writes Python faster." But "AI writes programs that are provably correct by construction."