Cold Wallet for your Agent
Give your AI agent a wallet with signing under your control. Keep the Co-Signer in your own environment, activate it for a signing session, and stop it when the session is complete.
Give these instructions to your AI agent.
The agent will install the official BroSettlement skills, review their source, and start an interactive setup flow from account access to the first testnet wallet.
Three steps to start
- 01Copy the ready-to-use prompt on the right.
- 02Paste it into Codex, Claude Code, Cursor, or another AI agent that supports skills.
- 03The agent will confirm the skills directory, install both packages, and activate guided onboarding.
Install both BroSettlement Agent Skills from https://github.com/BroLabel/brosettlement-agent-skills.
Clone or download the repository and inspect both `SKILL.md` files and the bundled scripts. Ask me which skills directory this AI agent supports, then install `brosettlement-onboarding` and `brosettlement-api` as sibling folders without overwriting existing skills. Verify that both skills are available, then activate `$brosettlement-onboarding` and guide me through setting up a new BroSettlement organization. If automatic installation is not supported, report the exact destination directory and next action instead of claiming success.Your agent can act. You control when it signs.
Separate the agent’s ability to request a transaction from the ability to sign it. Your Co-Signer and configured rules determine which requests proceed.
Co-Signer active only when needed
Keep your MPC share in protected storage on infrastructure you control. Start the Co-Signer for a signing session and stop it afterwards.
Two shares for every signature
The 2-of-3 MPC model requires two distributed shares to participate in signing. A single share cannot produce a valid signature.
Distributed DKG shares
DKG creates three distributed key shares. Keep operational signing and recovery material in separate trust boundaries.
Secrets stay outside model context. Keep API private keys, encryption keys, and MPC shares outside prompts, chat history, logs, and tool output. Give the agent only the permissions needed for its workflow.
From an agent request to a controlled signature.
Prepare API access, validate the request, and activate the Co-Signer for signing. Follow the transaction through the ledger and WebSocket events after the signing session ends.
Configure API access
Register your organization and create an API key with only the permissions required for the agent’s tasks.
Prepare the Co-Signer
Deploy the Co-Signer in your environment with protected persistent storage. Keep its credentials and MPC share outside the agent’s context.
Submit an intent
The agent requests a transaction with a wallet, network, asset, amount, destination, and idempotency key.
Activate and check
Start the Co-Signer through your controlled runtime. Check the request against limits, allowed destinations, and any required approval.
Sign, stop, and track
Complete MPC signing, then stop the Co-Signer after the session finishes. Track network delivery and confirmations through the API and WebSocket events.
Start with an agent. Scale with your product.
The Agent plan includes $200K in monthly volume. Overage applies above that limit, with Starter available when you need more capacity.
Agent plan pricing
Network gas, validator fees, routing costs, and third-party service fees are separate unless a specific offer explicitly includes them.
Put your agent to work with controlled access.
Use the wallet for supported asset operations, with signing policy and Co-Signer activation controlled by your infrastructure. Available networks and assets depend on your plan.
Stablecoin payments
Let the agent prepare payments to supported destinations for services, APIs, or compute, within the budgets you define.
Treasury operations
Manage wallet balances and prepare transfers between approved destinations with explicit limits on assets and amounts.
Reserve funds under your control
Keep the Co-Signer inactive between signing sessions. Activate it when an authorized transfer needs your MPC share.
Ledger records
Connect deposits, withdrawals, transfers, balances, and transaction states in one operating record.
Lifecycle events
Follow supported deposit and transaction events through WebSocket, and reconcile against REST resources.
Operator-controlled rules
Apply your own spending limits, allowed destinations, and approval rules before the Co-Signer participates in signing.
How your agent wallet works.
No. In the documented threshold model, BroSettlement holds only the server-side MPC share and cannot produce a valid signature without participation from the customer-hosted Co-Signer.
Give your agent a cold wallet. Keep signing under your control.
Register for the Agent plan: 30 MPC wallets and $200K included monthly volume for $30/month.