Skip to main content
PERSONA 3 - WEB3 AUTOMATION TEAMS

Wallet infrastructure for teams running many agents.

You run 20 bots for 15 clients. Each one needs its own wallet, its own limits, its own audit trail, and per-client visibility for the client.

THE PAIN

The bottleneck is not the agents. It is the wallet management.

If you run a Web3 automation agency, a market-making team, a yield-strategy operation, or any production deployment with many concurrent agents, the agents themselves are the easy part. You have battle-tested code and infrastructure to keep them running. What slows you down is everything around them: spreadsheets of wallet addresses, manual per-client reconciliation, scattered transaction logs, no clean way to give a client visibility into their own agent's activity without leaking another client's data, no enforced per-agent spending limits.

Most teams build this themselves at first - one shared multisig per client, per-agent ledgers in a Notion database, a Discord channel for transaction notifications. It works for the first three clients. By client ten it is a part-time job. By client twenty something will go wrong, an embarrassing mix-up that costs the relationship.

Blockchain0x gives every agent its own wallet, its own policy, its own log, its own seat access. You manage them all from one workspace, billed under one Stripe customer, with the right operators on the right agents. The ops layer is the entire product; you keep running the agents.

AGENCY WORKSPACE SETUP

How an agency provisions its first workspace.

Five-step walkthrough that gets a typical agency from signup to managing 5-20 client agents with proper isolation, billing, and observability.

  1. 01

    Provision the workspace

    Sign up once under the agency's email or shared ops account. Workspace name reflects the agency identity (the workspace name appears on per-agent invoices). Workspace seats default to 1; add more for the operators who need cross-client visibility.

  2. 02

    Create one agent per client (or per strategy)

    Each client engagement gets its own agent record: separate slug, separate wallet address, separate spend policy, separate verification badges. The agent record is the unit of isolation - one client's transactions never touch another's, even when both run under the same workspace.

  3. 03

    Assign agent-level seats to the right operators

    On Business, each agent includes 3 agent-level seats. Invite the operators who work on that specific client. They see and manage only that agent, never the others in the workspace. This is the seat model that makes per-client isolation feel correct: an operator cannot accidentally leak Client A's activity to Client B.

  4. 04

    Configure per-agent spend policies

    Set daily caps, per-payment caps, and (on Business) the allowed-counterparties allowlist for each agent based on what the client engagement actually permits. The same operator on the same workspace might run an agent with $10/day cap for one client and $5,000/day cap for another - the per-agent policy isolates the two cleanly.

  5. 05

    Wire your monitoring and on-call

    Set up webhook delivery for the events that matter operationally (payment.failed, agent.verified, policy.exceeded). Point them at your incident system or Slack/Discord. Audit-log events stream to your SIEM. The dashboard becomes the daily-driver view; alerting hits Slack when something breaks.

The setup typically takes 1-2 hours for the first workspace and 10-15 minutes per additional client agent. By the time you have 5 clients onboarded, the marginal cost of adding the sixth is mostly the conversation with the client, not the provisioning.

BILLING RECONCILIATION ACROSS AGENTS

One workspace, one Stripe customer, N agents.

The billing model is built around how agencies actually keep books: per-agent line items on a single invoice, exportable per agent or workspace-wide, with a webhook stream that lands in your accounting system in real time.

DimensionHow Blockchain0x handles itWhy agencies care
Workspace structure1 workspace, N agents, 1 consolidated Stripe customerEasy to find any payment across all clients
Invoice formatPer-agent subscription line + per-agent transaction-fee lineMaps cleanly to per-client billing if you re-invoice clients
ExportsCSV/JSON per agent, or workspace-wide; filterable by date rangeDrop into accounting tool or per-client P&L
Webhook to accountingaudit.* and payment.* events to your AP/AR system in real timeNo batch reconciliation; ledger stays current
CurrencyFees billed in USD by default; settable to other currencies via StripeMatch your accounting base currency
Records retained7 years on Business (configurable)Exceeds SOC 2 and most jurisdictional minimums

The pattern most agencies land on: the Blockchain0x invoice goes to the agency. The agency re-invoices each client for their agent's subscription line + a management fee. The audit log makes it defensible if a client questions a specific charge - you can show exactly which transactions in which window drove the line item. No agency has ever asked us to remove a charge after producing the audit trail.

COMPLIANCE POSTURE

What you can tell your clients (and their auditors).

Compliance is where most agency engagements fail before they start. The client's legal team wants to know: who holds the funds, who can see what, how are records kept, what happens if there is an incident. Here is what you can tell them, in writing, supported by the product.

Custody - we are non-custodial

Funds stay in client (or agency) wallets, not on Blockchain0x. We never have private keys. If we got compromised tomorrow, the attacker could not move USDC because we do not have the means to. This is the strongest custody claim a payment platform can make; written into the terms.

Access control - per-agent seat scoping

Operators see only the agents they have been granted seats on. Workspace-level visibility is a separate, more privileged seat. Every seat add, role change, and removal is recorded in the audit log with full attribution. Two-factor authentication is required for workspace seats.

Audit trail - tamper-evident, exportable, long-retention

Every action that affects an agent is logged with previous_hash chaining. The chain makes after-the-fact tampering detectable; combined with our infrastructure controls, it satisfies "evidence of the controls" requirements in most SOC 2 reports we have walked through. 7-year retention by default; longer on negotiated contracts.

Acceptable use policy - binding on every agent

Every workspace agrees to an acceptable-use policy at signup: no sanctions evasion, no money laundering, no fraud, no agents engaged in clearly illegal activity. Violations result in workspace suspension. The policy is publicly versioned; we will produce a current-and-historical version for any client legal review.

Incident response - documented runbook

Security incidents have a public runbook: notification within 24 hours of discovery, root-cause analysis within 7 days, post-mortem within 30 days. The runbook is available on request for compliance review. We have not had a notifiable incident at the time of writing; if and when we do, the runbook is the contract.

AUDIT LOG FIELDS

Every field on every audit-log entry.

The audit log is the artifact your client's auditor wants to see. Below is the full schema. Each entry is append-only and hash-chained to the previous entry; export to JSON/CSV/NDJSON or stream to your SIEM in real time.

FieldTypeDescription
audit_idstringULID, sortable by time, unique.
timestampISO 8601UTC, microsecond precision.
agent_idstringWhich agent this action affected.
actionenumpolicy.evaluated, payment.requested, settings.updated, member.added, allowlist.updated, key.rotated, plan.changed, etc.
actor_typeenumhuman, api_key, system, webhook.
actor_idstringUser ID, API key ID, or 'system'.
request_ipstringSource IP (for human or api_key actors).
request_idstringCorrelates with API request logs and webhook deliveries.
before / afterjsonState snapshots flanking the change.
outcomeenumsuccess, failure, rejected, partial.
previous_hashsha256 hexHash of the previous audit entry; chain makes tampering detectable.

Export modes: dashboard (JSON/CSV/NDJSON), API (GET /v1/agents/{id}/audit-log with cursor pagination + filters), or webhook stream (audit.* event family, compatible with Datadog, Splunk, ELK pipelines). Audit log is a Business-plan feature; basic transaction logs are available on Pro.

WHAT PLAN FITS

Business for the agency workspace, mixed plans for the agents.

Web3 automation teams almost always need at least one Business agent (for the audit log + team seats). Many run a mix: Business for high-volume client engagements with compliance requirements, Pro for smaller clients where audit logs are not contractually required, Free for experimental or dormant agents. Per-agent pricing is what makes the mix work without overpaying.

  • Free: experiments, dormant agents you may revive, demo agents for prospect conversations.
  • Pro ($9/agent/mo): active client agents at sub-$2k/month volume without strict compliance requirements.
  • Business ($29/agent/mo): client agents at scale, with audit logs, allowlists, and per-agent team seats. The default for production engagements.
  • Workspace seats: $5/seat/month per additional workspace seat for cross-client operator visibility.
See full pricing
FREQUENTLY ASKED

Five agency-specific questions.

What if a client wants to bring their own wallet rather than have us manage it?

Both patterns work. If you (the agency) connect your wallet, payments land in your control and you pay the client out separately; this fits engagement models where you bill the client a fixed monthly fee. If the client brings their own wallet, you sign them up under your workspace, connect their wallet via RainbowKit, and grant your operator agent-level seats on that client's agent; payments land in their wallet directly, you handle ops, billing flows through your Stripe subscription per agent. We see both shapes about equally.

Can we re-invoice clients for the Blockchain0x subscription as part of our fee?

Yes, and it is the most common agency pattern. Treat the $29 Business subscription per agent as a pass-through cost line in your client invoice, alongside your management fee. Some agencies bundle it (one all-in monthly fee that covers infra plus operator time); others itemize it. The audit log shows exactly which agent generated which costs, which makes either invoicing pattern defensible.

How do we handle compliance reviews when a client's auditor wants to see records?

Export the agent's audit log to JSON or CSV via the dashboard. The hash chain (previous_hash field on every entry) lets the auditor verify the log has not been tampered with after the fact. For higher-trust reviews, you can give the auditor read-only agent-level seat access on the specific agent under review, scoped to that one agent only - they see everything that happened, see nothing about other clients. This pattern has cleared SOC 2 Type 2 audits at customer engagements we have walked through.

What happens if our agency relationship with a client ends?

Transfer the agent ownership. From the dashboard, you can transfer an agent to a different workspace - the new workspace becomes the billing owner, the wallet address and history transfer intact, your operators lose access. If the client does not have a workspace yet, they sign up and you transfer to it. If the relationship ended badly, you can also revoke your operators' agent-level seats while keeping the workspace ownership; the wallet remains under your control until both sides agree on next steps.

Do you support white-label or co-branded ops for agencies?

Not at MVP. Co-branding means client-facing pages that show your agency's logo instead of Blockchain0x branding; we do not offer that today and have explicitly scoped it out of MVP. The reason: white-label fragments trust, and our public-page model is built around buyers trusting the verified Blockchain0x identity. If you absolutely need a white-label option for a major engagement, talk to us - we may build it as a custom Business-plus tier if the volume justifies the engineering.

Run an agency, not a wallet spreadsheet.

Per-agent wallets, per-client visibility, per-engagement audit logs. Business at $29 per agent per month.