Mattheus developer docs
Build with Mattheus REST APIs, SDKs, and MCP tools for market research, monitoring, reproducible strategy tests, portfolio context, and approval-first trading workflows.
Short answer
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. Read-only requests can retrieve supported market and account context. Execution-capable requests use referenceId idempotency and remain gated by entitlement, signer readiness, policy checks, and approval.
Read-only examples
Market data, funding, yield, portfolio, and MCP research examples are read-only unless a page explicitly labels a preview or execution-capable request.
Execution examples
Execution-capable examples require referenceId idempotency, wallet readiness, protocol certification, policy clearance, and either an exact interactive approval or an active scoped API-key agent session.
Who This Is For
Developers building multi-asset trading research tools, monitoring workflows, SDK integrations, or AI assistants.
Before You Begin
- A platform account
- An mt_ API key from settings
- Node 18+ for TypeScript or Python 3.10+ for Python
- Wallet and approval setup only for execution-capable flows
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.
export MATTHEUS_API_KEY="mt_your_key"
curl $MATTHEUS_API_BASE_URL/api/v1/data/perps/funding/HYPE \
-H "Authorization: Bearer $MATTHEUS_API_KEY"Common errors
- 401 Unauthorized: the mt_ API key is missing, malformed, revoked, or not scoped to the request.
- 429 Too Many Requests: back off and retry after the rate limit window.
- 502 or 5xx: the control plane or upstream market data adapter is unavailable. Retry with jitter and do not treat stale data as a trade signal.
Safety note
Read-only examples do not move funds. Execution-capable examples must stay behind explicit user approval, protocol certification, feature flags, wallet readiness, and policy checks.