Exchanges
Exchange integrations must use official APIs only with scoped credentials. Mattheus will not collect exchange passwords, automate web sessions, bypass venue controls, or use shared credentials.
Onchain protocols
Uniswap and Aave integrations need verified contracts, ABIs, supported chain IDs, quote and simulation paths, approval and revoke flows, event decoding, accounting rules, exit routes, and emergency stop procedures.
Infrastructure partners
Data, monitoring, wallet, and compliance partners need documented data rights, rate limits, failure modes, privacy posture, and support contacts before public launch references.
Intake checklist
- Partner name, primary contacts, official API, SDK, contract, or protocol documentation
- Supported and restricted regions, legal/compliance approval status, and commercial approval status
- Credential model, permission scopes, revoke paths, rate limits, error semantics, and incident contacts
- Read, quote, simulate, approve, execute, manage, exit, cancel, revoke, reconcile, and monitor lifecycle support
- Sandbox or canary account access, production evidence plan, webhook or event support, and reconciliation model