Fordefi API

Name: Fordefi API API
Brand: Fordefi API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingbearer43 EndpointsREST

For Agents

Manage MPC vaults, sign and submit blockchain transactions, look up assets, and configure webhooks across the Fordefi institutional web3 platform from agent code.

Quickstart

Get started with Fordefi API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list Fordefi vaults"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Fordefi API API.

Create and inspect MPC vaults that hold institutional digital assets

List vault assets and their balances across supported blockchains

Submit transactions for MPC signing through Fordefi's policy engine

Manage end users and user groups for role-based access

Issue and rotate authorization tokens used by automated systems

GET STARTED

Start building with Fordefi API API

Explore with Jentic

View OpenAPI Document

Use for: I need to submit a transaction from a Fordefi vault for MPC signing, I want to list all vaults in this Fordefi tenant, Find the assets held in a specific vault, Get suggested fees for a blockchain before signing

Not supported: Does not handle fiat banking, accounting, or DeFi protocol-specific actions — use for Fordefi MPC vault, transaction signing, user, and webhook operations only.

Jentic publishes the only available OpenAPI document for Fordefi API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Fordefi API, keeping it validated and agent-ready. Fordefi is an institutional MPC wallet platform and web3 gateway used by builders, traders, and operators to self-custody private keys, connect to dApps across blockchains, and apply granular policies to digital asset operations. The API exposes endpoints for transactions, vaults, assets, end users, user groups, blockchains, webhooks, and authorization tokens. Authentication is bearer-token based.

Use Cases

Patterns agents use Fordefi API API for, with concrete tasks.

★ Programmatic Treasury Operations

Automate institutional treasury workflows by submitting transactions through Fordefi's MPC signing pipeline. Use POST /api/v1/vaults to provision vaults, list assets via /api/v1/vaults/{id}/assets, and submit signing requests through the transactions endpoints under policy controls. Suits crypto-native businesses that need auditable, policy-bound on-chain operations rather than hot-wallet scripts.

List vaults via GET /api/v1/vaults, pick the one named 'Treasury USDC', and submit a signing request for a USDC transfer to a specified destination address.

End User and Permission Management

Provision teammates and partner users via /api/v1/users and group them through /api/v1/user-groups so each role only touches the vaults it should. This is critical for institutions that need separation of duties between traders, operators, and approvers. Each user and group is referenced by ID elsewhere in the API for policy attachments.

Create a user with the supplied email and add them to the 'Trading' user group via /api/v1/user-groups.

Asset and Fee Discovery

Read /api/v1/blockchains and /api/v1/blockchains/suggested-fees before constructing a transaction so the agent picks an appropriate gas or fee setting per chain. Combined with /api/v1/vaults/{id}/assets, this gives a complete view of what a vault holds and what it will cost to move it. The endpoints are read-only and safe to call frequently.

Call GET /api/v1/blockchains/suggested-fees for the 'ethereum' chain and return the suggested gas tip and base fee.

Webhook-Driven Operations

Register webhooks via the webhooks endpoints so Fordefi notifies your systems when transactions enter signing, complete, or fail policy checks. Useful for ops dashboards, compliance archives, and chat notifications. Webhooks receive structured event payloads and reference the transaction or vault ID for cross-lookup.

Create a webhook subscription that posts transaction-completed events to a specified HTTPS endpoint.

AI Agent Treasury Integration via Jentic

Agents use Jentic's intent search to find Fordefi operations, load the schema for vault listing or transaction submission, and execute calls under a scoped credential. This is the recommended pattern for assistants used by treasury teams to inspect balances or queue transfers — Jentic keeps the bearer credential isolated and out of the agent's context.

Use Jentic to search 'list Fordefi vaults', load the GET /api/v1/vaults schema, and return the names and IDs of vaults that hold the asset the user named.

Key Endpoints

43 endpoints — jentic publishes the only available openapi specification for fordefi api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/vaults

List vaults in the tenant

GET

/api/v1/vaults/{id}

Retrieve a vault by ID

GET

/api/v1/vaults/{id}/assets

List assets in a vault

GET

/api/v1/blockchains

List supported blockchains

GET

/api/v1/blockchains/suggested-fees

Read suggested fees for a chain

GET

/api/v1/users

List users

GET

/api/v1/user-groups

List user groups

GET

/api/v1/vaults

List vaults in the tenant

GET

/api/v1/vaults/{id}

Retrieve a vault by ID

GET

/api/v1/vaults/{id}/assets

List assets in a vault

GET

/api/v1/blockchains

List supported blockchains

GET

/api/v1/blockchains/suggested-fees

Read suggested fees for a chain

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Fordefi bearer token is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution token and never see the raw token, which is essential when the API can move institutional digital assets.

Intent-based discovery

Agents search by intent (e.g. 'list Fordefi vaults') and Jentic returns the GET /api/v1/vaults operation with its query schema, so the agent inspects the right vaults without browsing Fordefi docs.

Time to first call

Direct Fordefi integration: 1-2 weeks for auth, transaction submission, policy handling, and webhook plumbing. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Plaid API

Bank account data for fiat-side treasury operations alongside Fordefi's crypto custody.

Use alongside Fordefi when a treasury needs both bank balance visibility and on-chain MPC custody in a single workflow.

Complementary

Stripe API

Fiat payments to pair with Fordefi's crypto-side custody and signing.

Use alongside Fordefi when revenue is collected in fiat through Stripe and the treasury settles or holds reserves on-chain through Fordefi.

Complementary

Auth0 API

Identity provider that can front Fordefi's end-user provisioning.

Use alongside Fordefi when an institution wants Auth0 to handle user authentication and SSO before users are provisioned into Fordefi groups.

FAQs

Specific to using Fordefi API API through Jentic.

Why is there no official OpenAPI spec for Fordefi API?

Fordefi publishes reference docs but the only structured OpenAPI specification has been generated and maintained by Jentic so AI agents and developers can call Fordefi API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Fordefi API use?

The Fordefi API uses HTTP bearer authentication with a long-lived API token issued from the Fordefi console. Jentic stores the token encrypted in the MAXsystem vault and constructs the Authorization: Bearer header on outbound calls.

Can I list vault balances with the Fordefi API?

Yes, GET /api/v1/vaults/{id}/assets returns the assets held in a specific vault, and GET /api/v1/vaults lists vaults so you can resolve the right ID first. Combine with /api/v1/blockchains for chain metadata.

What are the rate limits for the Fordefi API?

The OpenAPI spec does not declare explicit rate limits. Fordefi applies tenant-level throughput controls in production — back off on 429 responses and avoid polling vault balances at sub-second intervals.

How do I submit a transaction for MPC signing through Jentic?

Search Jentic for 'submit a Fordefi transaction', load the relevant POST schema under /api/v1/transactions, and execute with the source vault, destination address, asset, and amount. Fordefi's policy engine then approves or rejects the signing request.

Does the Fordefi API support webhooks for transaction events?

Yes, the webhooks endpoints let you register HTTPS subscribers that receive transaction lifecycle and policy events. Use this to drive ops dashboards or to archive every signing decision for audit.