I will build secure exchange API integration where your keys stay yours

I will not ask you for your exchange API keys. That is the point of this gig.

You deploy this on your own infrastructure with your own API keys. I never receive, hold, or have access to your funds or your exchange account. What I build is the integration layer: the code that signs requests, separated from the code that decides what to send, with limits enforced before a signature exists.

I have done this on live venues: Binance, OKX, KuCoin and Bybit over HMAC, Hyperliquid and Asterdex over EIP-712, all from one signing path. The details that break most integrations are the ones I have already hit: canonical field ordering that silently recovers the wrong address, per-venue minimum notionals, contract-size conversion that has to reject instead of round.

What I build:

• exchange REST and WebSocket API integration with correct request signing
• key management infrastructure that keeps credentials out of your application code and out of logs
• policy checks (size caps, allowed symbols, allowed operations) enforced before a signature is created
• clear failure modes, so a rejected request tells you why
• optional: signing isolated in a separate service, using a secure key storage pattern (enclav