Mattheus Python SDK
Use the Mattheus Python SDK for typed Hyperliquid, Alpaca, Uniswap, and Aave reads, portfolio data, and gated execution helpers.
Short answer
The target Python package is mattheus==0.1.1, but public PyPI publishing is pending. During controlled beta, install from the repository checkout and start with read-only methods.
Package status
Public PyPI publishing is pending. During controlled beta, install from the repository checkout and start with read-only methods.
SDK execution helpers
The SDK exposes create_execution_approval, decide_execution_approval, and execute for interactive access-token flows. API-key execution uses the same execute method but requires an active bounded agent session.
Who This Is For
Python developers building research scripts, notebooks, services, and monitoring jobs.
Before You Begin
- Python 3.10+
- An mt_ API key
- Local repository checkout until PyPI publication passes smoke tests
- Wallet address only for portfolio methods
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.
# Public PyPI package publishing is pending.
# Install from the repository checkout during controlled beta:
# cd packages/sdk-python && python3 -m pip install -e .
import asyncio
import os
from mattheus import MattheusClient
async def main():
async with MattheusClient(api_key=os.environ["MATTHEUS_API_KEY"]) as client:
price = await client.get_price("HYPE")
funding = await client.get_funding_rate("HYPE")
print(price.mid_px, funding.funding_rate)
asyncio.run(main())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
Access-token clients must create an exact execution approval, approve it with fresh wallet reauthentication, and pass its one-time approvalId to execute. API-key clients require an active scoped agent session. Neither credential mode bypasses certification, launch, signer, venue, or policy checks.