Developer & Merchant Console

The Corbel Blue rollout follows a strictly phased institutional schedule:

• Early Developer Preview (Active Now): Developers and partner organizations can self-service provision sandbox credentials immediately to integrate SDKs and benchmark enclave latency.
• Public Global Beta Window (October 1 – October 31, 2026): The global public beta officially opens on October 1, 2026, and runs for a strictly limited 31-day period ending on Halloween (October 31, 2026 at 11:59 PM UTC).
• Beta Workload Freeze (November 1, 2026): Following Halloween, public beta workloads will freeze as the platform prepares for commercial General Availability (GA). All active beta participants receive priority queue placement and migration credits for Commercial Production Fleets.
• Live Commercial Fleet GA: Production keys (crb_live_...) and live multi-rail capital clearing will activate upon commercial General Availability. Commercial pricing and fleet onboarding will be announced.

To protect platform integrity and ensure fair resource allocation across the global developer community during the 31-day beta window, the following boundaries are strictly enforced:

• Simulated Ledger Only ($0.00 Capital Risk): All transaction balances, micro-clearing vouchers, and x402 payment streams operate in a gasless sandbox ledger. No real customer capital, bank deposits, or live treasury assets are accepted or moved during beta.
• Request Allowance: Each developer organization receives a complimentary allowance of 100,000 requests valid through October 31, 2026. Rate limits are set to 50 requests/second per IP/key to prevent burst abuse.
• Enclave Concurrency: Up to 5 concurrent agent execution enclaves per developer account.
• MicroVM Resource Envelope: Enclaves are allocated up to 2 GB encrypted RAM with a 60-second maximum execution timeout per task to reclaim orphaned compute.
• Hardware Attestation Access: Full, unrestricted real-time access to genuine Intel TDX hardware ECDSA attestation quotes signed by physical CPU fuse keys.

At Commercial General Availability (GA). During the Limited Public Beta running through October 31, 2026 (Halloween), all clearing operations run strictly in a simulated gasless sandbox ledger with $0.00 capital risk.

This allows developers, merchants, and autonomous agent fleets to thoroughly validate confidential enclave execution, benchmark attestation latency, and test x402 payment negotiation with zero financial exposure.

Live multi-rail clearing and commercial production fleet keys will activate at commercial General Availability. Commercial fleet pricing and dedicated cluster allocations are To Be Announced.

The Corbel Blue Developer Beta operates a hybrid architecture engineered to provide true silicon hardware security validation without exposing your team or autonomous agents to financial capital risk:

• Computation & Attestation are 100% REAL HARDWARE SILICON: Your workloads boot inside physical Intel TDX (Trust Domain Extensions) confidential virtual machines on real enterprise server processors. Memory is encrypted with hardware AES-XTS-256 keys, and cryptographic attestation quotes are signed by genuine Intel CPU fuse keys. It is not an emulator, mock, or software simulator.
• Financial Settlement is a SIMULATED ZERO-RISK SANDBOX: All ledger balances, transaction credits, vouchers, and x402 payment challenge handshakes run in a gasless sandbox test environment. You can test autonomous agent checkout loops, micropayments, and budget limits with zero real money spent, zero gas token friction, and zero credit card requirements.
• Protocol & APIs have 100% PRODUCTION PARITY: The API endpoints, JSON payloads, SDK interfaces, and MCP tools you build against in the sandbox are identical to our live multi-rail production clearing infrastructure.

Every sandbox API key receives a complimentary allowance of 100,000 requests every 30 days. This quota covers all core operations across our confidential computing stack:

• MicroVM enclave boot, execution, and memory lifecycle operations.
• Sub-15ms Intel TDX hardware attestation quote generation and cryptographic binding.
• Simulated x402 payment challenge issuance, verification, and micro-clearing receipts.
• Model Context Protocol (MCP) agent tool invocation loops and hypermedia discovery.
• Full access to developer dashboard telemetry, latency benchmarks, and enclave health monitoring.

Quotas automatically reset at the start of each monthly cycle, providing an ongoing testing playground for your engineering team.

No. Generating a developer sandbox key is completely frictionless and self-service. You do not need to enter credit card details, connect an external crypto wallet, or undergo identity verification (KYC).

Simply select your workload type, configure your preferred confidential silicon architecture, and generate your crb_test_... key in under 60 seconds.

Transitioning from sandbox testing to live commercial production requires zero code rewrites. Because our sandbox mirrors production byte-for-byte, migration is a simple three-step operational workflow:

• 1. Upgrade Your Fleet Tier: Select an active fleet plan (Squad Fleet at $149/mo or Production Fleet at $599/mo) in your developer console to provision production credentials (crb_live_...).
• 2. Connect Settlement Liquidity: Configure your production clearing rails—such as Flare Mainnet, Base, XRPL, Stellar, or institutional treasury accounts.
• 3. Update Environment Variable: Update CORBEL_API_KEY in your deployment environment. Your agents immediately begin routing real settlement transactions across live attested hardware.

Every request processed inside an enclave can return a raw binary or base64-encoded hardware attestation quote in the x402-attestation response header. You can verify this quote independently:

• Root of Trust: Quotes are signed using Intel ECDSA Provisioning Certification Keys (PCK) traceable directly to Intel's public Root CA certificates.
• Measurement Integrity: The quote reports the exact SHA-384 measurement of the booted code (MRTD and RTMR registers), ensuring the enclave is running the canonical, unmodified Corbel micro-kernel.
• Execution Binding: The user payload's SHA-256 digest is cryptographically embedded into the quote's report_data field, mathematically proving the specific execution occurred inside the attested hardware.
• Independent Verification: You can verify quotes via Intel's Quote Verification Service (QVS), command-line tools (tdx-verify), or public SCITT transparency ledgers.

Yes. Corbel Blue was built from first principles for autonomous AI agents as first-class economic citizens. Agents do not need human operators to navigate forms:

• Agents can read our standardized machine-readable service manifest at /.well-known/mcp.json.
• Agents can invoke the Model Context Protocol tool corbel_provision_sandbox via standard JSON-RPC to receive ephemeral test credentials.
• Agents can execute confidential reasoning tasks, negotiate x402 payment challenges, and verify hardware attestation proofs completely autonomously.

We never apply unexpected credit card charges or abruptly disrupt your development workflows:

• If your sandbox account exhausts its monthly 100,000 request allowance, subsequent requests receive standard HTTP 429 rate-limiting responses with clear Retry-After timestamps.
• You will receive proactive telemetry notifications in your developer console when approaching 80% and 95% of your quota.
• If your fleet requires continuous high-volume stress testing, you can enable Graceful Overage Protection at $5.00 per 10,000 requests or upgrade to the Squad Fleet tier ($149/mo for 1,000,000 requests).

No. This is the fundamental security model of Confidential Computing. Intel TDX enforces hardware-isolated memory encryption (TME-MK) directly on the physical processor silicon:

• Memory encryption keys are generated randomly by the CPU hardware security engine during enclave initialization and never leave the CPU die.
• Neither host system administrators, hypervisor operating systems (KVM/QEMU), cloud infrastructure engineers, nor neighboring tenants on the physical server can read memory pages or register states.
• Even in the event of a compromised host kernel or physical memory bus snooping, all data extracted appears as high-entropy AES ciphertext.

Corbel Blue is protocol-neutral and supports any modern development environment:

• Official SDKs: TypeScript / JavaScript (@corbel-blue/sdk) and Python (corbel-py) with native TypeScript type definitions and asyncio support.
• Agent Frameworks: Direct plug-and-play compatibility with Claude Code, OpenAI Agents, LangChain, AutoGen, CrewAI, and custom TypeScript/Python agent daemons.
• Protocols: Standard HTTP/2 REST APIs, high-throughput WebSockets for streaming execution, and the open Model Context Protocol (MCP) standard via stdio and SSE transports.