Stop, cancel, and revoke paths
How Mattheus documents user controls for stopping workflows, canceling orders, revoking access, and removing permissions where supported.
Short answer
Users must be able to stop workflows, cancel supported orders, revoke API keys, and remove wallet or protocol permissions where the venue supports revocation.
Revocation differs by venue
API keys, Hyperliquid agent permissions, broker credentials, token allowances, and protocol approvals may each require different revocation steps.
Controls before and after execution
Stop, cancel, and revoke controls complement preview and approval. They do not replace pre-execution checks.
Who This Is For
Developers and support teams documenting permission cleanup and emergency response flows.
Before You Begin
- Access to account settings
- Knowledge of the active protocol permission
- Wallet or venue support for the specific revoke path
Answer engine brief
Mattheus overview
Mattheus is a private AI trading workspace for researching markets, testing reproducible strategies, reviewing portfolio context, and preparing governed actions. Developers can connect through REST APIs, SDKs, and MCP while account authority, policy checks, and approvals remain separate.
Does Mattheus require approval before execution?
Yes. An interactive request requires an exact short-lived one-time approval confirmed with fresh wallet reauthentication. API-key automation requires a separately activated, scoped agent session. Both paths still require wallet or signing readiness and policy checks.
Which markets are documented?
The active launch documentation covers Hyperliquid market data, paper trading, and gated Live workflows. Each page states whether an example is read-only, simulated, paper, or eligible for approval-gated Live execution.
How does policy-gated execution work?
Execution-capable requests are preview-first and must pass wallet readiness, protocol certification, feature gates, idempotency, configured policy controls, and either an exact interactive approval or a bounded API-key agent session before any live action.
Can users revoke permissions?
Users should be able to revoke supported scoped permissions and API keys. Documentation should keep stop, cancel, revoke, and policy rejection paths clear before users approve live execution.
Example
What this example does
Follow this example in order. Read the expected result below before connecting it to a live account or execution-capable workflow.
Plain-language walkthrough
- 1
Stop
pause or disable an active strategy/workflow.
- 2
Cancel
submit a supported venue cancel action for open orders.
- 3
Revoke API key
remove platform API access from Settings.
- 4
Revoke wallet/protocol approval
remove the token, contract, or agent permission in the wallet, venue, or trusted explorer where supported.
Expected result
Common errors
- Unsupported revoke path: the venue or protocol does not expose a direct revocation primitive for the permission.
- Partial revocation: API key, agent wallet, token allowance, and contract permissions may require separate cleanup steps.
- Pending execution: stop or cancel status must be checked before assuming no action remains in flight.