Autonomous Agents (MCP + x402)

What this is

MCP gives agents reach. FortFi gives them limits. Agents can read balances, PnL, and holdings and propose sends and swaps on the same vault your team uses, but the policy engine checks every action before execution: caps, allowlists, co-sign, and audit. Agents get budgets, not raw keys.

This page documents the agent path, for software that runs on its own schedule (MCP clients, trading bots, treasury automation). If you want to connect Cursor or another tool to your passkey account, use Developer API keys (Stripe) or the public REST API reference.

Two integration paths

Who	Billing	Login	Start here
You (passkey account)	FortFi Personal or Startup (USD via Stripe), or Free at published limits	FortFi sign-in required	Developer: create scoped API keys
Autonomous agent	Personal $49 or Startup $499 USDC / 30 days on Base (x402)	No FortFi login: payment wallet is the billing identity	GET /api/mcp?plan=… → POST /api/mcp/onboard?plan=… (below)

Agent subscription (x402 · not Stripe)

Plan	USDC / 30 days	Vaults	Sigs / mo
Personal	$49	5	100
Startup	$499	50	1,000

Use matching ?plan=personal or ?plan=startup on discovery and onboard. Introductory alpha pricing, may increase as MCP tools and tier limits expand.
Renew with the same payment wallet: same FortFi agent wallets, fresh API key
Default policy caps (Personal tier): $500 USDC per transaction; $2,500 USDC rolling daily cap; $10,000 USDC rolling monthly cap
Allowlists, co-signers, and governance signatures apply. Agents cannot loosen policy without your wallet

Agent MCP access is billed in USDC on Base through the x402 protocol, not charged to a credit card and not processed by Stripe.
Introductory alpha pricing, may increase as MCP tools and tier limits expand.
FortFi software subscriptions (Personal / Startup) are a separate product for human passkey accounts; see /pricing.
On-ramp, off-ramp, swap, and network fees are third-party or on-chain costs, not part of the x402 subscription.

Onboard an agent (x402)

Choose a plan: personal ($49 / 5 vaults / 100 sigs per month) or startup ($499 / 50 vaults / 1,000 sigs per month).
Discover payment terms: GET /api/mcp?plan=personal or GET /api/mcp?plan=startup (HTTP 402 with x402 descriptor and PAYMENT-REQUIRED header).
Sign an EIP-3009 USDC authorization on Base for the subscription amount (x402 exact scheme, gas paid by the CDP facilitator).
Onboard: POST /api/mcp/onboard?plan=<same-plan> with JSON body (include contactEmail for dashboard access) and X-PAYMENT / PAYMENT-SIGNATURE header. FortFi provisions an agent wallet and returns an API key (shown once).
Check contactEmail for a claim link (72h), or MCP resend_claim_link (agent API key, keys:manage) if it expired.
Fund the FortFi default wallet address returned in the response. That wallet executes sends and swaps under policy.
Connect MCP: POST /api/mcp with Authorization: Bearer <apiKey> (JSON-RPC 2.0 tools/list, tools/call).

Discovery (unauthenticated)

GET https://fortfiapp.com/api/mcp?plan=personal
GET https://fortfiapp.com/api/mcp?plan=startup

Onboard (after x402 payment signature — plan must match discovery)

POST https://fortfiapp.com/api/mcp/onboard?plan=personal
Content-Type: application/json
X-PAYMENT: <x402-signed-payload>

{
  "displayName": "My treasury agent",
  "contactEmail": "[email protected]"
}

MCP JSON-RPC (authenticated)

POST https://fortfiapp.com/api/mcp
Authorization: Bearer <apiKey-from-onboard>
Content-Type: application/json

{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }

All API examples use the production host https://fortfiapp.com. Clients using @x402/axios can auto-pay from the PAYMENT-REQUIRED header on discovery. Exact amount and treasury address are always returned live from GET /api/mcp.

Two wallets, don't confuse them

Payment wallet (yours, external): pays the x402 subscription to FortFi's treasury. Also signs governance changes (allowlist, co-signer rules). Never holds the agent's spending balance.
FortFi default wallet (provisioned at onboard): executes sends and swaps under policy. Fund this with USDC after onboard.

Availability

Agent MCP onboarding is live in production when enabled on our servers. There is no separate waitlist for x402. If discovery returns HTTP 402 with payment terms, onboarding is open. Questions or enterprise agent limits: [email protected].

Human subscriptions: /pricing
Passkey API keys: /developer (sign-in required)
Billing note: Agent MCP access is billed in USDC on Base through the x402 protocol, not charged to a credit card and not processed by Stripe.