Private preview · commercial traffic disabled

One ledger for model access.

Route authorized API resources through a controlled gateway. Enforce budgets before dispatch, account for every token, and settle verified usage with a transparent 10/90 split.

Explore the console Read the security model

REQUEST / 8D31-F2SETTLED

ProviderApproved pool / AP-04

Input128,440 tokens

Output18,206 tokens

Consumer debit$3.420000

Supplier earning · 90%$3.078000

Platform fee · 10%$0.342000

CREDENTIAL BOUNDARY

Supplier secrets are encrypted with per-record keys and are never exposed to consumers or the web application.

Control before traffic. Evidence after.

The gateway refuses requests when identity, price, balance, or quota cannot be verified. Availability never bypasses accounting.

01
Authorize supply
Submit a dedicated, least-privilege provider key. Every resource is reviewed before it can receive traffic.
02
Set hard limits
Define model scope, token budgets, concurrency, and expiry. Reservations prevent concurrent overspend.
03
Settle verified use
Usage is priced from an immutable version. The platform retains 10%; the serving supplier earns 90%.

Security architecture

Designed around what must never leak.

Review threat controls

Envelope-encrypted supplier keys

Database access alone cannot decrypt credentials. Web and billing workloads have no bulk secret-read path.

Scoped consumer credentials

Platform keys carry model, budget, expiry, and optional network policy. Only hashes are retained.

Atomic reservation and ledger

Funds and quota are reserved before upstream dispatch; uncertain attempts reconcile instead of being silently released.

The preview is open for architecture review.

No real provider credential, payment, or commercial request is accepted yet. Explore the interface and review the operating model.

Open preview console