1. Connect provider
Create a provider connection for Fireblocks, BitGo, Copper, or Safe/self-hosted with scoped credentials and environment state.
Developers
One wallet operations API, provider escape hatches intact.
Alloy's developer surface should make provider portability boring: connect providers, map wallet objects, submit transaction intents, subscribe to canonical events, attach policy and risk decisions, and export reconciliation evidence.
In brief: Alloy is REST-first and OpenAPI-oriented. It is not a custody provider and should not hide provider-specific behavior when engineering teams need an escape hatch.
API model
A simple mental model for the first docs and sandbox.
2. Normalize objects
Read canonical wallet, address, asset, chain, account, and balance objects while preserving provider references.
3. Submit intent
Create transaction intent before provider-specific signing, approval, or transfer workflows begin.
4. Attach controls
Call policy, risk, compliance, and reconciliation hooks before and after transactions move.
5. Subscribe to events
Receive normalized webhooks for state changes while keeping raw provider events available for debugging.
6. Export evidence
Export audit, policy, compliance, and ops evidence for internal teams and external review.
Shape, not final docs
The first public developer page should promise clarity, not fake completeness.
Until the product API is final, the website should show integration shape and invite design partners into the API review. Avoid pretending full docs exist before the surface is validated.
{
"provider": "fireblocks",
"wallet": "canonical_wallet_id",
"intent": {
"asset": "USDC",
"amount": "25000.00",
"destination": "counterparty_wallet"
},
"hooks": ["policy", "risk", "reconciliation"]
}Engineering trust
Developer trust comes from explicit boundaries.
What Alloy owns
Canonical models, provider adapters, transaction intent/state, events, policy/risk/reconciliation hooks, audit evidence, and workflow consistency.
What providers own
Custody, signing semantics, raw transaction execution, provider-specific constraints, asset support, chain support, and operational limits.
Developer preview
Want the API reviewed against your current provider workflow?
Share your provider, transaction states, webhook pain, and reconciliation requirements. Alloy will prioritize design partners who can pressure-test the API surface.