PERMIXA DOCUMENTATION
Dashboard guide
Know what each part of your workspace tells you, and which actions change a setting.
Home: the quick picture
Home shows agents with budgets, independently verified payments and requests that may need attention. Recent activity lets you open the story behind an outcome.
The payment counts cover the latest 100 payment records, not an all-time financial statement. A registered Signer is not proof that it is online or ready to execute.
Agents: decide what may be spent
Create a named agent, set its daily USD budget and maximum per purchase, then choose its supported test networks. Follow the access method shown for your workspace. The hosted pilot uses an assisted dedicated connection; self-managed API-key mode may show a key once.
Edit spending limits, manage access and connect additional wallets from the agent controls. These are administrative changes, not payments. Read the agent guide →
Treasury: see funds and targets
Review connected Bitcoin, EVM and Solana accounts alongside registered accounts with balance sources and health. Use Add a wallet to connect another account. The manual allocation planner includes BTC, ETH, SOL and USDC; connected EVM and Solana accounts show separately queried testnet balances when Treasury opens. Use Refresh balances to retry an unavailable or older observation. Bitcoin testnet4 shows confirmed address holdings only; pending transactions, Signet, Lightning and mainnet holdings are not shown. Targets express where you would like funds held; saving a target does not move funds.
Plans to review are recommendations. Transfers and conversions have their own approval and execution states. Missing or stale balance information is not a zero balance. Understand treasury approval →
Activity: open the evidence
Search by merchant website, agent or transaction. Open a row to see:
- Request: what the agent asked for and the recorded website.
- Spending approval: what Permixa allowed, including network, amount and expiry.
- Payment: execution state, network reference and independent evidence when available.
- Receipt: what the customer-local Signer reported.
Technical IDs connect these records; they are not blockchain transaction hashes. Merchant origins omit private paths and URL parameters. “Not recorded” means the evidence is absent, not that the action failed.
Explorer links use the matching test network. Lightning is off-chain and has no public transaction explorer link.
Settings: understand the connection
Settings lets you verify browser-wallet ownership and lists registered Signers and connected accounts. It explains the agent → Permixa → Signer boundary. Wallet enrollment and secret configuration still use the customer-local operator workflow; there is no wallet-import form here.
Read status carefully
| What you see | What it means |
|---|---|
| Submitted / awaiting verification | A submission is recorded, but completion still needs evidence. |
| Independently verified | Independent settlement evidence is recorded. |
| Rejected | A check denied this request. Inspect the reason before deciding what to do. |
| Reconciliation required | The outcome is uncertain. Investigate the existing transaction; do not send again. |
| Refunded conversion | A refund outcome was recorded. It is not successful delivery of the requested destination asset. |
For completed capabilities, assisted setup and remaining work, see the current roadmap.