Launch protocols
Protocol documentation for the current launch and its controlled certification surfaces.
Short answer
Hyperliquid market data and paper trading are public. Hyperliquid Live remains approval-, eligibility-, policy-, and certification-gated; HyperEVM is deferred to a future release.
One full-launch gate
No integration is a public live venue while the full-launch verdict is NO_GO. Staging, testnet, and canary actions require explicit certification and allowlisting.
Certification matters
Internal certification can be canary, feature-flagged, needs setup, disabled, or blocked. Failed certification blocks live submission.
Who This Is For
Developers and operators building protocol-aware AI execution workflows.
Before You Begin
- A Mattheus account
- Protocol/action support
- Policy settings
- Manual approval for live execution
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
Hyperliquid
/docs/protocols/hyperliquid
- 2
HIP-3
/docs/protocols/hip-3
- 3
Alpaca
/docs/protocols/alpaca
- 4
Uniswap
/docs/protocols/uniswap
- 5
Aave
/docs/protocols/aave
Expected result
Common errors
- Preview rejected: balances, allowance, liquidity, route, simulation, policy, or approved-address checks did not pass.
- Approval required: an interactive request has no approved, unexpired, exact one-time approval artifact, or an API-key request has no active scoped agent session.
- Approval mismatch: execution must reject if the payload changed after the preview was approved.
- Approval unavailable: approval state could not be verified or consumed atomically, so execution remains blocked.
- Policy blocked: configured limits blocked the action before signing or broadcast.