REST vs MCP
REST and MCP expose the same treasury operations and share one policy engine. Developer keys (frtfi_hu_*) and agent keys (frtfi_ag_*) work on both surfaces. Writes use propose_* then confirm; MCP tools mirror the same flow.
| Surface | Transport | Auth | Best for |
|---|---|---|---|
| REST v1 | HTTPS + OpenAPI 3.1 | Bearer frtfi_hu_* or frtfi_ag_* | Human developers, curl, SDKs, dSaaS backends |
| MCP | JSON-RPC 2.0 (tools/list, tools/call) | Bearer frtfi_hu_* or frtfi_ag_* | Agent runtimes, Claude Desktop, tool-calling stacks |
Create a developer key in the Developer portal (frtfi_hu_*) or onboard an autonomous agent via x402 (frtfi_ag_*). Both key types authenticate REST and MCP.
Quick start
- Get an API key (developer portal or x402 agent onboard).
- Paste it in the API key field in the interactive section below.
- Try
GET /walletsfirst, then explore propose + confirm flows.
curl -sS "https://fortfiapp.com/api/v1/wallets" \
-H "Authorization: Bearer YOUR_API_KEY"Interactive reference
OpenAPI-powered explorer (Swagger UI under the hood). Endpoints are grouped by action type — portfolio, sends, swaps, yield, security, etc. Writes use propose_* then POST /proposals/{id}/confirm. Money moves may require passkey approval in the app.
Paste your key once — every Try it out request sends Authorization: Bearer … automatically. Stored in this browser tab only.No Authorize modal needed.
Loading API reference…