Skip to main content
A connection gets the permissions you tick on the consent screen. An API key gets the scopes you set when you create it in the dashboard. The MCP server lists only the tools those permissions open (tools/list), and every call is checked again on the server.

Spending that runs by itself (recurring)

Some tools do not spend at the moment of the call but switch on spending that continues later: auto-refill, auto bandwidth, Smart Mode, Energy Resale, a broadcast URL, Node API auto-renewal. For a connected app, creating or changing them needs recurring on top of the product’s permission. Switching off and deleting never need it. Pausing Smart Mode does, because the same tool also resumes it.
Spending that runs by itself is outside the daily cap and keeps running after you disconnect the app. Switch it off on its page in the dashboard.

Before the first top-up

Until the account’s top-ups total 100 TRX, the consent screen grants view and deposit_view only, and shows how much is left to top up. After the top-up, connect the app again and tick more permissions — the same connection is updated.

Team accounts

On the consent screen you choose which account the app works on: your own or a team account where you manage API keys. A team member can grant only the permissions their role has, cannot grant staking or node_api_plan, and cannot remove the daily cap (OAUTH_UNCAPPED_OWNER_ONLY).

API key or connected app

API keys are issued after the account’s top-ups total 100 TRX — see Authentication.