Agents & access

Start with a small USD budget

In Agents, choose Add an agent. Give it a recognizable name, such as “Research assistant.” Set a daily budget and maximum per purchase. For a small demonstration, the interface starts with $5 per day and $0.25 per purchase in test USD.

These are limits, not a guarantee of funding or a quoted exchange rate. Every request still needs a permitted route, current pricing where required, available funds and the Signer's approval.

Choose one, several or all test networks

The creation form can record policy choices for Base Sepolia, Solana devnet and Lightning Signet. Hosted agent creation may require assisted setup. A selectable network is not proof that its execution path is ready; the current hands-free pilot supports approved Base Sepolia USDC x402 purchases. Choose All supported test networks, or Choose networks and select a subset.

All saves an explicit snapshot of today's three networks. It does not add future networks, Bitcoin mainnet, arbitrary Bitcoin sends or automatic treasury conversion. Existing agents are not silently expanded. The current spending-limit editor does not edit their network list.

Use the access method your workspace supports

The hosted pilot uses a dedicated agent connection credential with assisted setup. In Agents, open the access instructions to use an existing saved connection or arrange setup. A missing API key cannot be recovered by pressing Replace API Key in this mode; that action does not create or rotate a hosted connection.

Self-managed deployments that support API keys show a new key once. Store it in a private secret manager or protected local environment. Only those deployments can replace it through the API-key controls.

For Codex, Claude terminal or another MCP-capable agent, use the local connector configured for your agent's dedicated connection. Keep credential values out of prompts, source control, URLs, logs and screenshots. Administrator and Signer credentials must never be used as agent access.

What agent access can and cannot do

An agent credential can submit typed intents and read its own budget and request/transaction status. It cannot change budgets, edit policy, administer Signers, obtain wallet keys, approve treasury actions or request arbitrary signatures.

Where API-key replacement is supported, replacing a key revokes the old access. Revocation stops new requests; it does not cancel an already-issued authorization. If execution must stop, use the separate customer-local emergency lock.

Connect your agent

The invited macOS companion preview includes Agent access. Download the public agent setup file from dashboard Settings, choose it in the companion, check the workspace, then follow the local Permixa sign-in and authenticator prompts. Never enter a wallet password or seed phrase.

After the connection is saved, copy its non-secret MCP settings into your existing connector configuration. The credential stays in a private local folder. Installing the connector, provisioning a hosted connection slot, and making the Signer ready to purchase remain separate setup steps. If acknowledgement is unfinished, resume the saved connection. If recovery is required, preserve its files and contact the operator.

Use the Intent API & SDK guide. A successful API response is not necessarily a settled purchase. Follow the returned intent and transaction IDs through to their final evidence.