The funding rate is a periodic payment exchanged between long and short positions in a perpetual futures market. It keeps contract prices near the underlying spot price by encouraging balance between buyers and sellers. Depending on market conditions, either longs or shorts pay, and the rate can affect trading costs over time.
Expanded Definition
A funding rate is the recurring cash flow that perpetual futures traders exchange to keep contract prices anchored to the underlying spot market. In market microstructure terms, it is not a fee charged by the venue in the usual sense, but a mechanism that transfers value between longs and shorts when the perpetual trades at a premium or discount.
Definitions vary across vendors on how the rate is calculated, how often it settles, and whether it is capped or smoothed. The core concept is consistent: when demand for long exposure dominates, longs may pay shorts; when short pressure dominates, shorts may pay longs. For risk teams, this matters because funding is part of total trading cost and can materially change position economics over time. The most common misapplication is treating funding rate as a fixed transaction cost, which occurs when traders ignore settlement frequency, leverage, and the directional bias of the position.
For a broader governance lens on price integrity and market risk, the NIST Cybersecurity Framework 2.0 remains useful as a control model even though it does not define funding rate itself.
Examples and Use Cases
Implementing funding-rate monitoring rigorously often introduces a timing and forecasting constraint, requiring organisations to weigh tighter cost control against more complex position management.
- A trader holds a leveraged long in a perpetual contract during a sustained premium and pays repeated funding charges that erode expected profit.
- A market maker tracks funding to decide whether to hedge with spot, futures, or a different venue when the implied carry becomes unattractive.
- A treasury team reviews funding alongside slippage and margin requirements before approving a multi-day directional strategy.
- A risk analyst uses funding spikes as a signal of crowded positioning and potential volatility compression or reversal.
- An internal controls team documents funding exposure in an exchange risk review, using the Ultimate Guide to NHIs only where automation, API keys, and bot-operated trading accounts require governance over non-human access.
In practice, venue methodology matters, so organisations often compare published rules against the exchange documentation and the NIST Cybersecurity Framework 2.0 for oversight patterns rather than assuming all perpetual markets settle funding the same way.
Why It Matters in NHI Security
Funding rate becomes relevant in NHI security when autonomous trading agents, bots, or API-driven treasury workflows initiate or maintain positions without continuous human oversight. If those systems do not account for periodic funding, they can turn a seemingly neutral strategy into a persistent loss, a margin drain, or an unintended liquidation path. That is a governance problem as much as a market-risk problem, because the agent’s execution authority, secret handling, and decision thresholds all affect how funding exposure is realised.
NHIMG research shows that 79% of organisations have experienced secrets leaks, with 77% of those incidents causing tangible damage, and only 5.7% report full visibility into service accounts, according to the Ultimate Guide to NHIs. For teams operating trading bots or settlement automation, that means the same identity controls used to protect APIs also govern whether a machine can silently accumulate funding costs across accounts, venues, and wallets. The strongest programmes treat funding awareness as part of operational resilience, not just a trader’s spreadsheet assumption.
Organisations typically encounter funding-rate risk only after an automated position underperforms or gets liquidated, at which point the term becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Agentic AI Top 10, CSA MAESTRO and OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0 and NIST AI RMF set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.OD-01 | Funding exposure is a governance and operational risk that must be identified and monitored. |
| OWASP Agentic AI Top 10 | Autonomous agents can incur funding costs when tool use and execution authority are not constrained. | |
| CSA MAESTRO | Agentic workflows need oversight when they can open or hold positions that generate recurring costs. | |
| OWASP Non-Human Identity Top 10 | NHI-01 | API-driven trading systems depend on non-human identities and their secrets for market access. |
| NIST AI RMF | MAP | AI systems that manage trades must account for financial harm from recurring market costs. |
Track funding-rate risk in governance reviews and link it to monitoring, escalation, and decision thresholds.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 27, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org