Dfns · Rate Limits

Dfns Rate Limits

The Dfns API enforces per-application and per-organization rate limits to protect the signing and wallet infrastructure. Limits are applied per API path/method class and are heavier on read (list/get) endpoints than on sensitive mutating endpoints that require User Action Signing (transfers, signature generation, policy changes). Specific per-endpoint request-per- second/minute values are governed by the commercial agreement and are not publicly reconciled in this artifact.

Dfns Rate Limits is the machine-readable rate-limit profile for Dfns on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and signatures.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Wallets, MPC, Key Management, Digital Assets, and Web3.

4 Limits Throttle: 429
WalletsMPCKey ManagementDigital AssetsWeb3Rate LimitingQuotasThrottling

Limits

Requests Per Application application
requests
see provider documentation
Aggregate request limit per registered Dfns application, varies by tier.
Requests Per Organization organization
requests
see provider documentation
Aggregate request limit across an organization's applications and users.
Signature / Transaction Throughput organization
signatures
see provider documentation
Throughput of signing and transaction-broadcast operations; may be shaped per blockchain network and commercial tier.
Read Endpoints application
requests
see provider documentation
List/get endpoints (wallets, transfers, transactions, events) carry higher limits than mutating endpoints.

Policies

Tiered Limits
Rate limits scale with the commercial agreement and deployment model (SaaS vs. dedicated).
User Action Signing Gate
Sensitive mutations (transfers, signature generation, key/policy changes) require a User Action Signing challenge/complete flow, which naturally throttles automated abuse of those endpoints.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/dfns-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.