Agentic trading on PACH 1
Let an agent trade for you under limits you set. You define a strategy (the envelope: instruments, caps, budgets, trading hours), grant an agent a mandate inside it, and every order is checked against the mandate before it goes out. A refusal is final. It is the same machinery EACH 1 trading desks use; on PACH 1 you are the admin and your own portfolio manager.
The Trading switch
- Open Trading in the sidebar (/dashboard/trading) and click Enable trading. Turning the trading environment on costs nothing until you switch on your first trading agent.
- On the agent’s page, flip its Trading card on and confirm Enable trading for this agent? Adds $5/month while on. A mandate can only be granted to an agent whose switch is on.
Strategies
A strategy is your envelope: the instruments allowed, permitted order types and sides, the currency, a per-order cap, a budget for a time window that applies across the whole strategy, and trading hours in your timezone. A draft is editable; activating it freezes that version, so every order records exactly which envelope governed it. Activating a new version keeps existing mandates running on the version they were granted under; retiring a version stops its mandates at the very next order.
Mandates & the subset rule
A mandate binds one agent to the active version of a strategy. It may narrow anything: fewer instruments, buy-only, a lower cap, its own budget, tighter hours. It is always a subset of its strategy, checked when you grant it, with every violation reported at once. To change a mandate, revoke it and grant a new one. One agent has at most one live mandate per strategy.
Stopping and resuming
- Switch the agent off and its very next order is refused. Billing for that agent stops at the next sync. Switch it back on and the mandate resumes, with no re-granting.
- Revoke the mandate, let it expire, or retire the strategy, and the next order is refused.
- Nothing waits on a background job: every order is checked live against the mandate, the strategy and the switch.
Web execution
With web execution on (the toggle on the Trading page), your mandates also apply at web trading platforms through the eniyan-web browser gate, with the same limits and the same final refusals as at the API. The venue has to be on the agent’s website allowlist with the Pay / Transact ability, and turning the toggle off stops web orders at the gate’s next config sync. See Web access, shopping & trading for the allowlist.
Refusal codes
| Code | When |
|---|---|
| mandate_not_live: trading_agent_disabled | The agent's Trading switch is off. Switching it back on resumes the mandate. |
| mandate_not_live: <other reason> | The mandate lapsed: mandate_revoked, mandate_expired, strategy_retired, or agent_not_active. |
| instrument_not_allowed / side_not_allowed / order_type_not_allowed | The order is outside the mandate's instrument list, sides, or order types. |
| outside_trading_window | The order falls outside the mandate's (or strategy's) trading hours. |
| amount_exceeds_cap | The order is above the per-order cap. |
| mandate_budget_exceeded / strategy_budget_exceeded | The budget for the window is used up, for the mandate or across the whole strategy. |
Every refusal is written to your audit log with its reason. Integrating by API (minting order tokens, introspection, reporting fills)? The EACH 1 trading reference documents the full contract, which is the same on both products.