Corbel Blue Developer Documentation
Corbel Blue provides the missing infrastructure for sovereign digital commerce: hardware-isolated execution enclaves (Intel TDX, AMD SEV-SNP, NVIDIA Confidential Computing) coupled with sub-millisecond x402 gasless micro-clearing.
Whether you are building autonomous AI agents that pay per inference query, confidential quantitative trading strategies that must run with zero host inspection, or machine-to-machine micropayment channels, Corbel gives your software first-class economic citizenship.
Zero-Trust Enclaves
Memory encrypted via AES-XTS-256. Invisible to cloud hosts and hypervisors.
Sub-ms Clearing
Direct HTTP 402 clearance with zero blockchain gas fees ($0.00 gas overhead).
Native MCP Protocol
Native Model Context Protocol server for Claude, Cursor, and Python agents.
📦 1. SDK Installation
Install the official client SDKs for TypeScript or Python. Both libraries include automated silicon attestation quote verification and native x402 payment headers.
🔑 2. Authentication & Keys
Every request to Corbel Blue requires an API key passed via the standard HTTP Authorization: Bearer <key> header or supplied to the client SDK constructor.
| Key Prefix | Environment | Monthly Quota | Rate Limit | Billing |
|---|---|---|---|---|
crb_test_... |
Developer Sandbox | 100,000 requests | 60 req/min | $0.00 (Free Forever) |
crb_live_... |
Dedicated Production | 10,000,000+ requests | Custom high-velocity | Usage-based micro-clearing |
You can provision an immediate sandbox key with 1 click in the Developer Console or via the MCP tool corbel_provision_sandbox.
🔒 3. Executing Attested Enclave Workloads
Confidential enclaves provide memory encryption at the physical CPU silicon level. Code executes in an isolated environment that even the cloud provider host OS, hypervisor, or root administrators cannot inspect or tamper with.
import { CorbelClient } from '@corbel-blue/sdk';
const client = new CorbelClient({
apiKey: process.env.CORBEL_API_KEY,
silicon: 'intel-tdx' // or 'amd-sev-snp' | 'nvidia-cc'
});
async function main() {
// 1. Spawn an isolated execution session inside physical silicon
const session = await client.enclaves.createSession({
region: 'us-central1',
workload: 'portfolio-optimization'
});
// 2. Dispatch confidential inputs directly into encrypted memory
const result = await session.execute({
inputData: { targetExposure: 0.85, maxDrawdownPct: 2.5 }
});
// 3. Inspect the cryptographic attestation quote
console.log('Hardware MRTD:', result.attestation.mrtd);
console.log('TCB Status:', result.attestation.tcbStatus); // "UpToDate"
console.log('Output:', result.data);
}
main();
🛡️ 4. Silicon Attestation & Verification
Every enclave session generates an ECDSA P-256 silicon attestation quote signed by the CPU manufacturer's root key. Clients verify three cryptographic invariants before trusting any computation:
- MRTD (Measurement of Root of Trust Domain): Cryptographic hash of the initial enclave image, ensuring untampered code.
- RTMR0–3 (Runtime Measurement Registers): Real-time event log tracking OS kernel boot, libraries, and application state.
- Mutual Remote Attestation TLS (RA-TLS): Ephemeral P-256 certificate binding the TLS handshake directly to the silicon quote.
🧠 5. Confidential AI Inference
Dispatch private prompts directly to open-weights LLMs hosted inside hardware enclaves. Weights and activations remain encrypted in memory, prompts are never logged or used for model training, and requests are settled on-the-fly via fractional-cent micro-clearing ($0.0001 per query).
const response = await client.inference.complete({
model: 'llama-3.3-70b-enclave',
messages: [
{ role: 'system', content: 'You are a sovereign verification agent running in hardware isolation.' },
{ role: 'user', content: 'Verify transaction batch 0x7f... for settlement compliance.' }
],
attestSilicon: true
});
console.log('Private Response:', response.content);
console.log('Silicon Quote:', response.attestationQuote);
console.log('Settlement Fee:', response.settlement.amountUsd); // "$0.0001"
🤖 6. Model Context Protocol (MCP) Deep Dive
Corbel Blue implements the Model Context Protocol (MCP), the universal open standard created to bridge large language models with external tools, isolated runtime environments, and sovereign payment rails.
Through Corbel MCP, autonomous AI agents in Claude Desktop, Cursor IDE, Gemini SDK, LangChain, and custom agent loops act as first-class economic citizens: they can provision their own compute keys, spawn hardware enclaves, verify vendor attestation, and clear micro-payments automatically.
Dual Transport Architecture
Corbel MCP supports both standard transport protocols:
CLI Sub-Process Mode
Ideal for desktop AI copilots (Claude Desktop, Cursor). The IDE spawns npx @corbel-blue/mcp as a local background process communicating via standard input/output streams.
npx -y @corbel-blue/mcp
Cloud Edge Gateway
Ideal for serverless agents, cloud workers, and multi-agent platforms. Connects over HTTP JSON-RPC 2.0 with Bearer authentication and streaming event feeds.
https://corbel.blue/api/mcp
🛠️ 7. The 6 Core Agent MCP Tools
The Corbel Blue MCP server exposes 6 high-precision tools designed specifically for autonomous agent workflows:
1. corbel_provision_sandbox
ZERO-FRICTIONAllows an agent to autonomously self-provision a free developer sandbox API key in real-time. Instantly registers 100,000 monthly hardware-attested execution requests without human intervention.
| Parameter | Type | Required | Description |
|---|---|---|---|
agentName |
string | YES | Identifier for the agent or bot (e.g. "trading-scout-v2") |
useCase |
string | OPTIONAL | Workload category: autonomous-agent, micro-payments, or confidential-compute |
{ status: "provisioned", apiKey: "crb_test_...", quotaMonthly: 100000, publicBetaLaunch: "2026-10-01" }
2. corbel_enclave_spawn
HARDWARE ISOLATIONProvisions a dedicated hardware-isolated enclave environment with cryptographic memory encryption. Protects proprietary code, secrets, and weights from host observation.
| Parameter | Type | Required | Description |
|---|---|---|---|
enclaveType |
enum | YES | Target silicon: "intel-tdx", "amd-sev-snp", or "nvidia-cc" |
payloadHash |
string | OPTIONAL | SHA-256 measurement root for reproducible build verification |
region |
string | OPTIONAL | Target compute region: "us-central1", "eastus", "europe-west3" |
{ status: "spawned", sessionId: "enc_tdx_...", mrtd: "8f3c4b12...", memoryGuard: "AES-XTS-256" }
3. corbel_enclave_attest
ECDSA P-256 QUOTEFetches and validates the cryptographic hardware quote for an active enclave session. Allows an agent to independently verify physical CPU provenance before sending secrets.
| Parameter | Type | Required | Description |
|---|---|---|---|
sessionId |
string | YES | Active session identifier returned by corbel_enclave_spawn |
{ verified: true, tcbStatus: "UpToDate", hardwareRoot: "Intel TDX v4", quoteSignature: "3045022100..." }
4. corbel_micro_clear
SUB-MS x402Executes sub-millisecond x402 payment authorization for machine-to-machine commerce with zero blockchain gas fees ($0.00 gas overhead).
| Parameter | Type | Required | Description |
|---|---|---|---|
rail |
string | YES | Supported settlement rail: "flare-mainnet", "base", "xrpl" |
amountUsd |
string | YES | Amount in USD formatted as decimal string (e.g. "0.001" for a micro-query) |
recipient |
string | YES | Recipient agent or merchant destination address |
{ status: "cleared", txHash: "0x7a2f...", latencyMs: 1.18, gasCostUsd: 0.00 }
5. corbel_check_quota
TELEMETRYInspects real-time remaining monthly attested execution requests, rate limits, and latency telemetry for an agent key.
| Parameter | Type | Required | Description |
|---|---|---|---|
apiKey |
string | YES | Corbel API key (crb_test_... or crb_live_...) |
{ remainingRequests: 99420, totalAllocated: 100000, p99LatencyMs: 1.42, rateLimitPerMin: 60 }
6. corbel_evidence_verify
PORTABLE EVIDENCE
Validates portable evidence reference tokens (x402ev/1) against on-chain and cryptographic roots to verify task settlement and attestation history.
| Parameter | Type | Required | Description |
|---|---|---|---|
evidenceRef |
string | YES | Evidence URI (e.g. "x402ev/1:sha256:d8b2...7a4f") |
{ valid: true, timestamp: "2026-09-19T22:00:00Z", issuer: "Corbel Enclave Node #04", digestVerified: true }
🎮 8. Interactive Live MCP Simulator
Test the Model Context Protocol tools in real-time. Select any tool below to inspect its live JSON-RPC 2.0 request payload and simulated enclave response:
⚙️ 9. Client Setup: Claude Desktop & Cursor IDE
Connect Corbel Blue to your local developer workflow in seconds. Copy the appropriate configuration snippet into your local editor settings:
A. Claude Desktop (`claude_desktop_config.json`)
Located at ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"corbel-blue": {
"command": "npx",
"args": ["-y", "@corbel-blue/mcp"],
"env": {
"CORBEL_API_KEY": "crb_test_your_key_here"
}
}
}
}
B. Cursor IDE (`.cursor/mcp.json`)
Place in your project root at .cursor/mcp.json or configure in Cursor Settings → Features → MCP:
{
"mcpServers": {
"corbel-blue-remote": {
"url": "https://corbel.blue/api/mcp",
"headers": {
"Authorization": "Bearer crb_test_your_key_here"
}
}
}
}
💻 10. Autonomous Agent Loop Implementations
Integrate Corbel Blue directly into custom Python and TypeScript agent orchestration loops:
Python AsyncIO Agent Loop
import asyncio
from corbel_sdk import CorbelAgentClient
async def run_agent_cycle():
client = CorbelAgentClient(api_key="crb_test_...")
# 1. Provision hardware enclave
enclave = await client.enclaves.spawn(silicon="intel-tdx")
# 2. Verify silicon attestation quote before passing model weights
is_valid = await enclave.verify_attestation()
assert is_valid, "Hardware attestation failed!"
# 3. Authorize instant micro-clearing payment for inference
receipt = await client.clearing.authorize(
rail="base",
amount_usd="0.001",
recipient="0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7"
)
print(f"Settled: {receipt.tx_hash} in {receipt.latency_ms}ms")
asyncio.run(run_agent_cycle())
cURL Direct JSON-RPC Invocation
curl -X POST https://corbel.blue/api/mcp \
-H "Content-Type: application/json" \
-H "Authorization: Bearer crb_test_your_key" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "corbel_check_quota",
"arguments": { "apiKey": "crb_test_your_key" }
}
}'
📦 11. Official Client SDKs
Node.js / TypeScript
Full async client with zero-dependency quote validation, automatic retries, and typed MCP schemas.
npm i @corbel-blue/sdk
Python 3.10+
AsyncIO client suited for AI agents, LangChain/LlamaIndex tools, and algorithmic quantitative systems.
pip install corbel-sdk
🌐 12. OpenAPI 3.1 Discovery Catalog
For automated API clients, SDK generators, Postman, and agent routers, Corbel Blue serves dynamic machine-readable discovery specifications:
https://corbel.blue/.well-known/openapi.json
https://corbel.blue/.well-known/mcp.json
🛡️ 13. Security & Compliance Architecture
Corbel Blue is engineered under non-custodial architectural principles. Corrente Labs, Inc. does not hold user funds, cannot inspect private keys inside enclaves, and enforces cryptographic attestation proofs across every physical node.
Hardware Enclave Boundaries
Memory pages encrypted via hardware-isolated AES-XTS-256 engines. CPU registers scrubbed upon enclave exit.
Multi-Rail Neutrality
All settlement networks operate on equal institutional footing with sub-millisecond x402 gasless clearing.
Need dedicated enclave capacity or enterprise SLA?
Connect directly with the Corrente Labs cryptography and infrastructure engineering team.
CONTACT ENGINEERING DESK →