Hands-off signing for the flows you predefine
Machine-speed approvals, human-set rules
High-volume operations cannot wait for a tap per transfer. Your automated co-signer authenticates with HMAC-signed requests, joins signing sessions automatically, and signs exactly what your policies allow — everything above threshold still waits for a human.
Share the Trust, Guard the Keys
Machine-speed operations still need a human-set boundary
High-volume flows cannot wait for a tap, and giving a service unlimited signing authority is how a compromised key becomes a company-ending incident. API signing runs the flows you predefine, authenticated per request and bounded by the same policy engine your people answer to.
- Signed, timestamped requestsEvery call carries an HMAC signature over its payload and a timestamp, so a replayed or tampered request is rejected before it reaches business logic.
- Automation inside the rulesAutomated operations clear the same governance evaluation as manual ones. Below your threshold they flow; above it they wait for people.
- Keys that are governedCreating or changing an API key is an approval-gated action, recorded like any other sensitive change.
How it works
Authenticated, bounded, logged
Every request is HMAC-SHA256 signed and timestamped against replay. The signer holds one share of three — compromising the machine yields a share that cannot sign alone, and policies bound what it could ever have signed.
- ✓Withdrawal queues drain themselves within limits
- ✓Deposit sweeps sign without a human tap
- ✓Every automated signature lands in the same audit trail
Integration specification
Everything your integration engineer will ask in the first hour.
Frequently asked questions
Get answers to commonly asked questions.
Is it a hot wallet?
No — one MPC share of three, policy-bound. There is no key on the server to steal.
Who controls the rules?
You do, and rule changes are approval-gated — automation cannot widen its own mandate.
Which plans?
Standard, Business and Enterprise.
