ResourcesStatus

Status

As of 26 October 2026. Every claim elsewhere in these docs, on the site or in a deck resolves to a line here. If a line says planned, nothing about it is live, and no date is promised that is not written down.

The product

CapabilityStatusWhat it means for you
Sandbox organizations: test rail, practice budget, no identity checkLiveyou can try everything in ten minutes (Quick Start)
Production organizations: identity verification, passkey-signed termsLivereal rails, receipts labelled production
Decisions before money moves: allow / deny / escalate; limits per transaction, day, month; one currency per mandate; caps per sellerLiveevery payment is decided against terms a person signed
Human approval: escalation to the owner, in the console, by e-mail, as a card in the chatLivean agent above its limits waits for a person; nothing is charged meanwhile
Biometric step-up on approvals (optional, per organization)Livea face check with the identity provider above a threshold you set
Signed receipts, verified offline with public verifiersLivea third party checks a decision without Regent (Receipt)
Settlement confirmation signed by the counterparty, embedded in the receiptLive since October 2026the receipt says what the merchant, PSP or custodian says
Audit trail: hashed events, Merkle batches, signed checkpoints, epochs, Bitcoin timestampsLivea tamper-evident record with external witnesses
Anchoring on Solana: agent registry, mandate registry, audit anchorLive on devnetthe programs are deployed and used; mainnet follows the independent audit of the programs
Agent identity as did:webvhLivea resolvable identifier with a key log
AP2 v0.2 evidence per decisionLivemandate chains for an AP2 counterparty
Budget envelopes (AAuth Budgets)Live at get4agent.comnamed as in production in draft-hardt-aauth-budgets-00
Cloud Gateway in the official MCP registryLiveone URL for Claude, Claude Code and any MCP app

Rails

RailStatus
Stripe through the Cloud GatewayLive
Agentcard: the owner’s own card at US merchantsLive; sandbox cards in sandbox organizations
Any HTTP API through the gateway or the sidecarLive
Custody co-sign: a custodian signs only after a Regent decisionPilot with a custody provider
Card issuer or processor pre-authorizationPublished contract, no issuer wired yet: what an issuer would wire

Assurance

ItemStatus
Keys and secretssigning keys live in a cloud KMS and never on disk; every host secret is encrypted at rest; an agent’s key is its own or held in custody for it, and each receipt names which (key_custody)
Approvalsterms are signed with the owner’s passkey, with an optional biometric step-up; no API key can activate a mandate
Evidencereceipts verified offline by public verifiers; an audit chain with Bitcoin timestamps and Solana anchoring
Identity verificationthrough a third-party provider; Regent stores the verdict, never the biometric
Backupsencrypted, off-site, restore tested
Third-party assurancea SOC 2 audit and an independent penetration test are the next step, scoped for the US entity; the Solana programs are public and go to an independent audit before mainnet. Regent holds no certification today and claims none; its receipts support your SOC 2, GDPR and EU AI Act evidence

Operations

ItemStatus
RegionsOne: United States (Virginia). Regional endpoints: planned
Public status pagePlanned
LatencyMeasured weekly at the edge; the current figures are on Latency and failure

Packages

Current versions and what each one supports are on Versions; dated changes on the Changelog.