Product changelog

What changed.

Verified updates to Felix infrastructure, integrations, and documentation. Runtime availability remains authoritative on the status page.

August 27, 2026API 2.0.136 / MCP 2.0.86

Deterministic account activation and recovery

Interrupted account creation now resumes the same account, including accounts created during the UUID compatibility incident.

New deterministic child accounts use stable UUIDv4-compatible identifiers accepted by every activation and risk-policy path.
Existing deterministic UUIDv5 child accounts remain recoverable without rebuilding their Safe or venue identities.
Hyperliquid onboarding failures now name MCP-native recovery tools instead of raw REST endpoints or HTTP headers.

A previously blocked UUIDv5 account reactivated with its cached live key and all three venue capabilities available.
A fresh non-custodial account completed Safe, Polymarket, and Derive onboarding in 104.9 seconds and passed 36 of 36 account checks.
Replaying the exact creation request returned the same account in 3.0 seconds without creating a duplicate.

August 26, 2026API 2.0.135 / MCP 2.0.85

Trading authority is clearer, withdrawal recovery is immediate, and operational controls no longer depend on hidden call-count limits.

Documented the authority hierarchy: the owner-signed wallet policy is the account ceiling, while every API key remains subordinate to it.
Clarified that a manage-scoped launcher key may prepare a policy change, but only the local owner key can authorize a higher on-chain limit.
Removed the withdrawal waiting period. A valid owner-authorized withdrawal can execute immediately.
Removed the fixed daily call-count ceilings from Safe withdrawals and owner policy updates.
Simplified the emergency panic request to an explicit boolean confirmation instead of a hidden phrase.

Production API health and focused withdrawal, policy, and panic regressions passed.
The private MCP release build passed package-install, tool-count, resource, public-health, and no-key fail-closed checks.
API keys still cannot raise their own authority or bypass the owner signature required by the wallet policy.

August 25, 2026Public release surface

The public site now separates product availability, runtime health, and integration guidance into surfaces that humans and agents can verify.

Published a dedicated customer-visible status page without exposing account data or infrastructure topology.
Reworked the documentation around owner-controlled accounts, live authorization, recovery, market research, backtesting, and reconciliation.
Added explicit infrastructure and trading-app release dates across the public launch surface.
Added machine-readable references for AI integrations alongside the human documentation.

Public routes, canonical metadata, documentation controls, article code regions, and machine-readable references passed semantic verification.
The production build completed with the status and documentation routes included.