Felix.trade

Product changelog

What changed.

Verified updates to live Felix developer infrastructure, integrations, and documentation. The trading app launches September 17, 2026. Runtime availability remains authoritative on the status page.

API 2.0.178 / MCP 2.0.110 public npm release

Clean install graph and synchronized agent setup

The npm client now installs without known production advisories, while every current setup surface pins the same reviewed release.

Changed

  • Updated the MCP dependency graph to fast-uri 3.1.6 or newer and removed an unused legacy Ethers dependency chain declared by the Polymarket client.
  • Preserved the reviewed Polymarket signing runtime in Felix with its upstream MIT notice and byte-for-byte signing compatibility tests.
  • Added a clean-consumer audit to the release gate so a fresh npm install must have zero known production vulnerabilities.
  • Synchronized the homepage, docs, start guide, machine-readable agent references, category pages, and blog setup examples to MCP 2.0.110.

Verified

  • A fresh registry install exposes 125 tools and seven resources, fails closed without a key, and installs no legacy Ethers or upstream Polymarket package tree.
  • Core security, signing, recovery, funding, withdrawal, artifact, tool-classification, and read-purity checks passed before and after publication.
  • npm exposes only latest: 2.0.110; the stale next tag was removed.
API 2.0.178 / MCP 2.0.108 public npm release

Fund before activation and autonomous recovery setup

Empty live-account reservations stay off-chain, guided recovery is automatic, Hyperliquid dust no longer freezes returns, and withdrawal assets are explicit.

Changed

  • Separated gas-free registration, API-key minting, and account reservation from the paid Safe deployment boundary.
  • Added a $5 Polygon USDC/USDC.e funding preflight before wallet activation begins.
  • Made unfunded onboarding return only actionable deposit and retry instructions.
  • Replaced process-level metrics with a client-observable request timing contract.
  • Authorized Hyperliquid returns against the venue-confirmed withdrawable balance while reconciling residual dust positions.
  • Added an explicit Polygon USDC.e destination warning to withdrawal preparation and agent documentation.
  • Made guided onboarding create, authenticate, and register its encrypted recovery file without a follow-up terminal step.
  • Added a read-only recovery-status tool that proves the file matches the installed identity without exposing custody material.

Verified

  • Unfunded requests start no deployment, move no money, and resume the same reserved account with the same idempotency key.
  • Activation abuse controls remain enforced after funding verification.
  • A sub-minimum reduce-only Hyperliquid dust close reaches the venue path, while new positions still enforce the venue minimum.
  • A real existing identity was reused unchanged while automatic recovery setup and the independent MCP status check both returned ready.
API 2.0.175 / MCP 2.0.102 hardening

Final public-boundary and secret-hygiene pass

Public health surfaces now expose only the service information an integrator needs.

Changed

  • Reduced public /v1/status to service health, API/MCP compatibility, and bounded freshness fields.
  • Removed infrastructure diagnostics from public status responses.
  • Added repeatable redacted hardcoded-secret scans to backend and MCP release checks and removed a legacy embedded monitoring credential.
  • Hardened the restore drill against archive links, devices, FIFOs, path traversal, and arbitrary health-probe destinations.

Verified

  • Backend security, privacy, authorization, webhook, stream, legal, restore, and fee tests passed as a clean release candidate.
  • MCP build, security, secret-manifest, tool-guardrail, read-purity, resource, and production-dependency audits passed.
  • The secret scanners report locations and detector names only; suspected values are never printed.
Documentation and policy contract

Immutable account trading ceilings

Account-level trading ceilings are now documented consistently as a security boundary fixed at account creation.

Changed

  • Clarified that update_wallet_policy supports pause, resume, renew, and lockdown, but cannot change per-operation, daily, or lifetime ceilings.
  • Documented that existing live-key caps are changed by revoking and minting a replacement inside the same account ceiling.
  • Documented that limits above an account ceiling require a new account and ordinary withdrawal/deposit migration.

Verified

  • The public human docs, machine-readable agent docs, MCP guide, API reference, quickstart, and SDK guides now state the same limit model.
  • No runtime policy, account, key, or money behavior changed in this documentation release.
API 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.

Changed

  • 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.

Verified

  • 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.
API 2.0.135 / MCP 2.0.85

Owner control and immediate account recovery

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

Changed

  • Documented the authority hierarchy: the owner-signed wallet policy is the account ceiling, while every API key remains subordinate to it.
  • Clarified that policy actions require the local owner key; a manage-scoped launcher key cannot authorize them alone.
  • 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.

Verified

  • 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.
Public release surface

Launch documentation and customer-visible status

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

Changed

  • 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.

Verified

  • 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.