Felix developer infrastructure · MCP and API
Connect an agent to Felix.
Start with the public MCP package or integrate the API directly. Both paths keep owner control separate from agent permissions, funding, and live execution.
Developer infrastructure is live
Felix MCP 2.0.108 is public on npm. Pin the exact version while validating a new installation and check runtime status before every live workflow.
Recommended · Public npm release
Felix MCP
The shortest path for Claude, Codex, or Cursor. Secrets remain outside model context.
Set up MCP →Available now · Advanced
Direct API
Register with a local owner signature and manage credential injection yourself.
Use the API →https://api.felix.tradeMCP packagefelix-mcp@2.0.108On this page
Before you begin
Registration, wallet readiness, live authority, and a venue-confirmed fill are different states. Runtime status remains the authority for availability. Move through them in order.
- 01
Visitor
Review the control model, current status, and available setup paths.
No account, credential, funding, or trading authority exists.
- 02
Registered
Prove control with a local owner signature and receive the account credential once.
Registration does not fund the account or authorize execution.
- 03
First use
Complete an authenticated status check, market quote, and research or backtest action.
Market data and analysis do not submit an order.
- 04
Wallet ready
Complete the owner-controlled wallet and venue prerequisites required by the chosen route.
Wallet readiness is separate from a live execution grant.
- 05
Live authorized
The owner separately signs exact markets, contracts, limits, expiry, and transfer boundaries.
This is the point bounded real-money execution authority exists.
- 06
Confirmed fill
Felix and the venue reconcile the resulting position and fill after a submitted real-money order.
A request sent is not the same fact as a venue-confirmed fill.
Set up Felix MCP
Use this path for Claude, Codex, or Cursor. Guided onboarding generates the owner identity locally. Owner, API, and backup-recovery secrets stay in macOS Keychain outside model context.
Step 01
Run guided onboarding
Review the terms, then run the pinned public package. Registration does not send the private key to Felix.
npx -y --package felix-mcp@2.0.108 felix-keys onboard --accept-terms --client claude
Step 02
Reconnect and verify Felix
Reconnect Felix in your AI tool, confirm the active account, and require custody recovery to be ready before funding.
Read felix://getting-started, call get_status and get_custody_recovery_status, require recovery ready, and verify the active account. Do not authorize or place a trade.
Step 03
Make the first request read-only
Confirm the connection and inspect the account limits before granting any live authority.
Check Felix status, quote BTC, and explain the risk limits. Do not authorize or place a trade.
Use the API directly
Use this path when your application owns the signer and secret-management boundary. Registration enables account access; live execution still needs separate owner authorization. Funding and live authority remain separate.
Step 01
Request a registration challenge
curl -X POST https://api.felix.trade/v1/register/challenge \
-H "Content-Type: application/json" \
-d '{"owner_address":"0xYourLocallyGeneratedAddress"}'Step 02
Sign locally and register
Sign the exact returned message with the owner key on your device, then exchange the signature for the account and API key. If present, bounded acquisition metadata is carried through both requests; it never changes account or key authority.
curl -X POST https://api.felix.trade/v1/register \
-H "Content-Type: application/json" \
-d '{"message":"<the message>","signature":"0x...","accept_terms":true,"legal_version":"2026-08-30"}'Step 03
Quote a market
curl https://api.felix.trade/v1/quotes/BTC -H "Authorization: Bearer $FELIX_API_KEY"
Step 04
Inspect the risk controls
curl https://api.felix.trade/v1/status -H "Authorization: Bearer $FELIX_API_KEY"
Before you go live.
Complete these checks before funding an account or granting execution authority.
01
Back up the owner key
Felix cannot recover it. Back it up before funding the account.
02
Keep the agent trade-only
Withdrawals use a separate scope and exact owner authorization.
03
Set hard limits
Caps and loss controls live outside the model and cannot be prompted away.
04
Know the stop
The panic action cancels managed activity where possible and revokes the calling key. Positions and allowances remain separate.
Need the full operating model?
Read the complete account, custody, execution, recovery, and venue documentation before running a live agent.