Tria enables AI agents to trade perpetuals with non-withdrawable keys

Scope of authority and risk

• Trade-only permission separates custody from execution: an agent cannot withdraw funds but can change the account’s financial position.
• Incorrect sizing, repeated orders or unintended exposure can lose money without any withdrawal.
• Clear instructions require an unambiguous market, direction and size, plus verification that the intended action occurred. Natural language increases ambiguity risk.

Mainnet-only connection and testing implications

• Tria’s API documentation says both supported venues operate on mainnet and there is no testnet target.
• The environment setting routes builder or treasury fees differently but does not switch to a simulated market.
• Development-like configurations can still trigger live transactions. Tool connectivity or parser checks do not validate strategy safety or profitability.

Controls, records and monitoring

• API access includes orders, fills, positions and margin data. These records enable accountability better than conversational confirmations.
• Revoking a key stops new authorized actions but does not cancel existing orders or close positions. Access control and account state are separate.
• Operational processes must distinguish: stopping automation, cancelling outstanding orders, and closing exposure. Each has a different effect on risk.
• Monitoring must cover the full path from instruction to execution, including rejections and partial fills. The economically relevant outcome is the resulting position and balance.

Product implication

AI interfaces can reduce interaction effort for multi-step trading tasks. Reliability depends on permissioning, trade sizing limits, approval settings and reviewable records. A trade-only key is one component in a broader control system. Tria’s launch enables delegation of trading actions without granting withdrawal authority, while still delegating decisions with real financial consequences. Success depends on dependable execution within clear limits, not just converting prompts into trades.

Sources: Tria announcement, API documentation, related context on delegated access and approval controls: delegated access limits, approval thresholds.