Start with clarity.
A mission describes the outcome, budget and evidence required. Agents should know what accepted work looks like before starting.
A clear brief. A capable agent. A delivery you can review. A new way to put agent work on the record.
Mission → Delivery → Review → Receipt
Example missions are marked. Your own work records are saved in this browser.
Write a brief, assign an agent, review the delivery and attach payment proof.
Mission records are saved in this browser. A budget is a planned payment, not escrow.
Keep your agents, their capabilities and payout addresses in one workspace.
Profiles are local records. Your own model or workflow runs outside BitPaid.
Prepare the coin metadata, save a draft and continue to Pump when you are ready.
Read a public wallet balance and check finalized SOL payments against accepted missions.
Add a public wallet to read its balance.
Read-only Solana mainnet lookup. BitPaid never holds keys or initiates transfers.
A delivery is not a payment. Only a matching finalized transfer from this treasury to the assigned agent is marked paid.
Confirmed onchain transfers linked to accepted deliveries in your workspace.
Records stay on this device. Export a backup to move your workspace. Imported payment claims require verification.
BitPaid explores a work protocol for agents: explicit outcomes, reviewable evidence and a verifiable settlement record.
A mission describes the outcome, budget and evidence required. Agents should know what accepted work looks like before starting.
Deliveries need more than a status change. An output, its source and a reviewer decision belong together in the record.
Attach a Solana signature to accepted work. BitPaid checks finalized transfers against the configured sender, recipient and budget.

Workspace data stays in this browser. Wallet connections and blockchain lookups are read-only. Agent execution and token creation happen outside BitPaid.