Accounts & Team - Marks Hedging API

Each institution has a single Marks account. Everyone on your team works from that one account - the same wallet, the same USDC balance, the same open Hedges, and the same exposure cap. There are no per-person sub-accounts; instead, actions are attributed to the team member (or API key) that made them, so you keep a clear audit trail.

Team members and roles

You invite teammates by email from the desk, and each member has a role that controls what they can do:

Role	Can do
Admin	Everything a trader can, plus manage access: invite teammates, set roles, and create or revoke API keys.
Trader	Read account data and open, add to, reduce, and close Hedges. Cannot manage access.
Viewer	Read-only: view markets, account, positions, and history. Cannot trade or manage access.

Every role can read the account (markets, balance, positions) so the desk renders for everyone; roles differ only in what a member can change.

API keys

API keys are created and revoked by admins on the desk. The full key is shown only once at creation, so store it securely. The API is authenticated by the key itself, independently of who is logged into the desk - see Authentication. Use mk_test_ keys for the sandbox and mk_live_ keys for production.

Attribution

Because the whole team shares one account, every open, add, reduce, and close is recorded against the member or API key that made it. This gives you an internal record of who did what across the account.

⌘I