Your account.
Your bots.
Sign in, choose what your app can do, and download its API connection. Your account stays in control of transaction approvals.
Sign in to get started.
01 / Sign in
Use your email, phone, social account, or an existing wallet.
Sign in to create or manage API access.
02 / API access
A bot is a program with its own key. Choose what it can do below. Each permission level includes the earlier ones; your wallet keeps control of signing transactions.
Registered bots
- Sign in to view your connections.
Optional: keep transaction funds in a separate wallet
Give your transactions a separate wallet, controlled by your signed-in account. Keep funds apart from your personal balance, share approvals with other owners, or approve a bot to act within exact limits on supported networks. API access only needs sign-in; this setup is optional.
Set up your transaction wallet
Use the same owners and approval rule on the networks you choose. Review the wallet address on each network before creating it. Balances and network fees stay separate.
Sign in to see the supported networks.
Review and send transactions
Use the connected wallet on the current network to prepare an action and test it without sending funds (a simulation). Add each prepared action to your review list. You can include actions from several networks before approving and sending them.
Each network has its own fees, approvals and confirmation status. Transactions can finish at different times. A failure on one network does not undo transactions confirmed on another.
Load the bot key downloaded during registration. The key stays in this page's memory and is never sent to the service.
Choose an operation from the API guide and enter its input. The resulting calls are shown before signing.
Fill from bot permissions
For ERC-20 payments, the owner must separately approve how many tokens the payment contract (terminal) may spend. This limit is an allowance.
Use one plan step at a time to verify payment or cash-out amounts. Several calls sent together can confirm without proving each financial result.
Choose specific plan steps
All planned calls are selected by default.
Send this operation on its own
Use this flow for a single transaction, including one covered by an approved bot permission.
Additional owner signatures
Transactions to review
Add a prepared action from each wallet you want to use. This list uses owner approvals; you review the exact action on every network before signing.
Optional bot permissions
Allow a registered bot to repeat one action for 7 or 30 days. This permission is called a session. Moving funds still needs fresh owner approval unless you approve the exact payment budget below. Bot permission guide.
The bot’s API access must include relay and remain valid for the whole session.
Required limits on sponsored network costs
Use the sponsor contract (paymaster) reviewed by this service. Enter exact integers in gas units and wei, as required by each field. These limits cover the whole session; the wallet cannot pay its own session network costs.