Restricted API access
The setup flow is intended for Binance reading and Spot trading access. Withdrawal permission is not part of the required workflow.
Security & API safety
Your keys stay limited. Your account stays yours.
AamirGrid AI is designed around a restricted Binance Spot connection, server-side credential protection, tenant isolation, and evidence-based order reporting. These controls reduce operational exposure; they do not remove market or provider risk.
How protection is applied
Controls that match the actual product.
Security statements should be specific. Here is what the platform can and cannot do within the current Binance Spot scope.
Server-side credentials
Binance credentials are handled on the server and are not placed in public HTML, the browser storage layer, or the anonymous activity feed.
Tenant isolation
Credentials, wallet ledger, grid settings, worker state, order history, and live private events are scoped to the authenticated tenant.
Order boundaries
Worker lifecycle identifiers distinguish bot orders from manual Binance activity. Manual trades are not intentionally changed or closed by the grid.
Evidence-based reporting
Socket.IO delivers fresh state quickly, while bounded REST reconciliation remains the final authority for live open orders and execution evidence.
Limited public visibility
The public feed uses masked identities and aggregate records. Private credentials, full usernames, and tenant dashboard data are not exposed publicly.
Before you connect Binance
Use a key you can safely revoke.
These are practical account-owner steps, not a replacement for reviewing Binance's current security guidance.
- Create a dedicated Binance API key for this workspace rather than reusing a key from another service.
- Enable only the permissions needed for the current workflow: account/market reading and Spot trading. Keep withdrawals disabled.
- Review the key permissions and account activity after setup. Revoke the key from Binance if you no longer want the connection active.
- Keep your Binance account protected with strong account security and never paste API secrets into public chat, tickets, or browser console logs.
Important risk notice
Restricted permissions lower the blast radius of a credential mistake, but they cannot eliminate trading risk. Prices can move against an open position, orders can remain pending, liquidity can vary, and Binance or network/API interruptions can delay reconciliation. Never treat a grid as a guaranteed-return product.
Understand the full execution path.
See how account setup, grid rules, verified fills, SELL targets, and worker recovery fit together.