Disclaimer: This article is general information for token teams. It is not legal, financial, security or investment advice. Exchange account features, permissions and regulatory treatment differ by venue and jurisdiction, so check current exchange documentation and review any setup with your own advisers.
Quick answer
How do market maker custody and API keys work? In a market-making engagement, crypto custody comes down to two questions: who holds the tokens and stablecoins, and what the keys given to the market maker can do. The most common control point is a trading-only API key on an account the project owns, with withdrawals disabled. Whatever the setup, the agreement should state who holds what, how balances are reconciled and how access ends.
Why founders ask about crypto custody first
When a token team hires a market maker, one of the first questions is almost always about custody. That is reasonable. The engagement involves real inventory, often a meaningful share of the project's liquid tokens and some stable assets, sitting on exchanges where the market maker trades. Founders want to know whether those assets stay under their control and what happens if something goes wrong.
Crypto custody is a broad subject that covers wallets, institutional custodians and regulated storage. This article stays in a narrower lane: custody in the context of a market-making engagement. Here the practical issues are account ownership, key permissions, inventory tracking and offboarding. Getting those right gives the team clarity and lets the market maker focus on its actual job of quoting and managing liquidity.
The main custody setups
There is no single correct model. Each of the setups below is used in practice, and each places custody and responsibility in a different place. The right one depends on your venues, your internal controls and the commercial model you agree.
Project-owned accounts with trading-only keys
The project opens and owns the exchange accounts, deposits the inventory and creates API keys for the market maker with trading permissions only. The market maker can place and cancel orders but cannot withdraw funds. The project keeps custody of the assets and can see every balance and trade directly. The trade-off is that the project has to manage the accounts, handle exchange onboarding and move funds when rebalancing is needed.
Sub-accounts
Many exchanges allow a master account to create sub-accounts. The project can hold the master account and assign a sub-account to market making, with its own API keys and balances. This separates market making inventory from treasury funds on the same venue and makes reporting cleaner. Permissions still matter: the sub-account keys given to the market maker should be limited to trading.
Token loan to the provider's accounts
In some engagements, the project lends tokens to the market maker, which holds them in its own accounts and trades from there. In this setup custody moves to the provider for the term of the loan, and the agreement becomes the main control. It should define the amount, the term, how and when tokens are returned, reporting duties and what happens at the end. How loans and retainers appear in proposals is a separate topic, covered in our article on how a retainer market maker works.
What trading-only permissions mean
Most centralized exchanges let account owners choose what an API key can do. Typical options include reading account data, trading spot or derivatives, and withdrawing funds. A trading-only key allows the holder to read balances and place or cancel orders, but not to move assets off the exchange.
For a project-owned account, this is the usual control point. Withdrawal permission should stay disabled for any key the market maker uses. Where the exchange supports it, restricting the key to known IP addresses adds another layer. The project should keep a record of every key issued, who it was issued to, its permissions and when it was created, and should be able to revoke any key quickly.
It is also good practice to review the key list regularly. Remove keys that are no longer used, and rotate keys when people change roles on either side. These are routine housekeeping steps, not signs of distrust, and a professional provider will expect them.
How inventory is tracked and reconciled
Whatever the custody model, both sides need the same view of the inventory. Start with an opening statement: the balances of each asset on each account or venue when the engagement begins, confirmed by both parties.
From there, agree a reconciliation schedule. Many teams reconcile on the same cycle as the regular market making report, comparing exchange balances with the provider's records and explaining any difference. Rebalancing between venues, deposits and withdrawals by the project, and any changes to the loan amount should each be logged with dates and amounts.
When a token trades on several venues, tracking gets harder because inventory moves between exchanges as the market maker keeps quotes balanced. Our guide on multi-venue market making inventory explains how teams keep balances aligned across exchanges.
What the agreement should say about custody and offboarding
The written agreement is where custody becomes enforceable. It should state which custody model applies, which accounts are in scope and who owns them. It should describe the API permissions the market maker will receive and confirm that withdrawal access is not included where the project owns the accounts. It should set out reporting and reconciliation duties.
Offboarding deserves its own clause. At the end of the engagement, open orders should be cancelled, keys revoked by the account owner and a final balance statement prepared and confirmed by both sides. For a token loan, the agreement should set the return timeline and the method. Our article on the market making agreement and SLA covers these and other contract terms in more detail.
Questions to ask before you hand over access
A few direct questions make custody arrangements clear from the start. Which custody model do you propose, and why does it fit our venues? Which API permissions do you need, and can you work with trading-only keys and IP restrictions? How do you report balances, and how often do we reconcile? Who on your side has access to the keys, and how is that access controlled? What happens to orders, keys and balances on the last day of the engagement?
If you are still choosing a provider, our guide on how to choose a crypto market maker lists further questions to cover. Teams preparing for a first listing can also look at our pre-TGE support page, where account and inventory setup is part of the early work.
Conclusion
Market maker custody and API keys are less complicated than they first seem once each piece is written down: who owns the accounts, what the keys can do, how balances are reconciled and how access ends. Trading-only permissions on project-owned accounts are the usual starting point, and the agreement covers every model. If you would like to discuss how a custody setup could work for your token, the EasyMM team can help from our market making page.
FAQ
What does crypto custody mean when you work with a market maker?
It means who holds the tokens and stable assets used for market making, and what access the market maker has to them. In many setups the project owns the accounts and the market maker gets trading-only keys.
Does a market maker need withdrawal access?
Not on accounts the project owns. A market maker can quote and manage orders with trading-only permissions. Moving funds between venues can be handled by the account owner.
What are trading-only API keys?
They are exchange API keys that allow reading balances and placing or cancelling orders, but not withdrawing assets. Many exchanges also let you restrict them to specific IP addresses.
Can a market maker withdraw funds from my exchange account?
Not if the keys you issue have withdrawal permission disabled. Check the permissions on every key, keep a record of them and revoke any key that is no longer needed.
Whose accounts does a market maker trade from?
It depends on the model. It can trade from project-owned accounts or sub-accounts using trading-only keys, or from its own accounts under a token loan defined in the agreement.




