Documentation Index
Fetch the complete documentation index at: https://home.1151.to/llms.txt
Use this file to discover all available pages before exploring further.
1151 provides a managed wallet layer for Bitcoin, Ethereum, and Tron via the public API at https://api.1151.to. The platform maintains addresses, signatures, and broadcasts so your teams only have to orchestrate when wallets are created, queried, or spend funds.
Supported networks and assets
| Network | Capabilities |
|---|
Bitcoin (btc) | A single receiving address per wallet, automatic UTXO management, and BTC spends. |
Ethereum (eth) | EOAs that can transfer native ETH, supported ERC-20s (USDC/USDT), or custom ERC-20s via contract address. |
Tron (tron) | Mainnet or Nile testnet wallets that support native TRX and TRC-20 USDT. |
testnet: true during creation. Ethereum wallets use Sepolia, Tron wallets use Nile, and Bitcoin wallets target testnet3 (with testnet4 support coming soon).
Lifecycle at a glance
- Create a wallet with
/wallet/create and receive its ID (w_<uuid>) plus the on-chain address.
- Retrieve metadata through
/wallet/get using the ID, address, or wallet name.
- Transact via
/wallet/send to broadcast native or token transfers.
- Inspect Bitcoin spendable outputs with
/wallet/utxos.
- Delete a wallet through
/wallet/delete when it is no longer needed.
Each API enforces plan limits and account ownership so wallets stay isolated per customer.
Plan limits
| Plan | Included wallets | Notes |
|---|
standard | 5 | Hard cap. Creating a fourth wallet returns HTTP 403. |
scale | 100 | Additional wallets stay active and are billed as add-ons. |
large | 1000 | Same behavior as scale with a larger included quota. |
Wallet data model
| Field | Description |
|---|
id | Wallet identifier (w_<uuid>). |
wallet_name | Human-readable name provided during creation. |
address | Blockchain address associated with the wallet. |
network | btc, eth, or tron. |
testnet | Indicates whether the wallet targets a test network. |
created_at | Unix timestamp (seconds) when the wallet was created. |
last_used | Updated when a successful send is recorded. |
metadata | Optional JSON object you attach on creation or send. Returned on every wallet read. |
Next steps
