Safety & Permissions
Understand how permissions, confirmations, and exchange-level limits constrain what Airavat can do, and where control and responsibility remain with you.
Airavat is designed to be powerful, predictable, and constrained.
It can only act within the permissions you grant, the limits enforced by your exchange, and the confirmations you explicitly provide. This page explains where authority lives, how permissions work, and what boundaries Airavat cannot cross.
The Permission Model
Airavat does not have blanket access to your exchange account.
Every action is constrained by three layers:
API permissions you configure on the exchange
Exchange-level rules and limits
Explicit confirmations inside Airavat
If a permission does not exist at any layer, Airavat cannot act.
API Key Permissions
When you connect an exchange, you decide exactly what Airavat can and cannot do.
Recommended permissions
Read account information
Place and manage trades
Strongly discouraged
Withdrawal permissions
Airavat does not require withdrawal access to function. Enabling withdrawals materially increases risk and is not recommended.
If an API key cannot place a certain order, access a market, or modify a position, Airavat cannot do so either.
Exchange-Level Enforcement
Your exchange is always the final authority.
Rules that Airavat cannot bypass include:
Margin requirements
Liquidation logic
Risk limits
Leverage caps
Market availability
Order size constraints
Airavat submits requests. The exchange decides whether they are accepted or rejected.
Confirmation as a Safety Boundary
Before any live action is executed, Airavat requires explicit confirmation.
You are shown a clear summary of the action it is about to take, typically including:
Instrument
Side (buy / sell)
Size
Order type
Price (if applicable)
Execution only proceeds if you explicitly confirm.
No confirmation means no trade.
This confirmation step is intentional. It exists to reduce accidental execution, misinterpretation, and impulse-driven actions.
Automation & Ongoing Permissions
Any automation, scheduling, or recurring execution must be explicitly enabled by you.
Automation does not grant new permissions. It only operates within:
The API permissions you have already granted
The limits enforced by the exchange
Automation can be paused or disabled at any time.
User Control & Revocation
You remain in control at all times.
You can immediately stop Airavat from acting by:
Disabling execution within Airavat
Revoking or rotating API keys on the exchange
Revoking API access immediately prevents Airavat from taking further action.
What Airavat Cannot Protect You From
While Airavat enforces execution safety, it cannot eliminate trading risk.
Airavat does not protect against:
Market volatility
Slippage
Liquidations
Poor strategy design
Incorrect assumptions
Clearly confirmed instructions with unintended consequences
Decision quality and risk management remain your responsibility.
Responsibility & Accountability
Every action executed by Airavat:
Originates from your instruction
Is explicitly confirmed by you
Is executed on your exchange account
Airavat is the execution mechanism. Decision-making and outcomes remain with you.
What’s Next
The next sections cover:
How intent and confirmations work in detail
Supported order types and execution mechanics
Automation and scheduled workflows
Common mistakes and failure modes
Safety in Airavat is enforced through clarity, constraints, and control.
Last updated