Protect Solana agents with verified onchain guardrails.

Oculus watches autonomous wallets on Solana in real time, verifies every spend against your policy on-chain, and pushes structured alerts the moment a limit is crossed — without forcing you to rewrite your agent stack.

Introduction

Autonomous agents move fast on Solana: they swap, bridge, pay invoices, top up tooling, and execute workflows around the clock. The problem is not activity, it is unchecked activity. One bad loop or compromised tool permission can turn a healthy treasury into a live incident.

Oculus sits alongside your Solana wallet operations and enforces the guardrails you define: per-transaction limits, rolling budget windows, recipient and program allowlists, and structured webhook alerts on every breach.

Quickstart

Most teams are live in under ten minutes. You need a Solana treasury wallet and access to a webhook endpoint or the SDK to receive alerts.

1. Create a workspace

   Open your Oculus workspace, register the agent, and connect the Solana wallet that funds its transactions.

2. Define policy guardrails

   Set hard caps for per-transaction, hourly, and daily spend. Add allowlists for approved programs, tokens, and recipient wallets.

3. Fund your reserve

   Point Oculus at the agent wallet(s) you want to watch. Every transfer, swap, and program interaction is streamed into the policy engine.

4. Attach monitoring

   Connect your webhook endpoint so every Solana transfer, swap, and program interaction gets logged in real time against the active policy.

5. Start routing agent activity

   Use the SDK, API, or CLI to register agents under a policy. From there Oculus handles on-chain verification and alert routing.

Enforcement flow

Oculus is designed to be operational, not ceremonial. Each spend event runs through the same pipeline so your team can trace what happened and why.

Policies

A policy is a signed configuration that tells Oculus how an agent is allowed to spend on Solana. It stays consistent whether the agent acts through a backend service, a cron job, or an internal operator tool.

{
  "workspace_id": "ws_base_01",
  "agent_id": "ag_marketmaker_7",
  "chain": "base-mainnet",
  "wallet": "0x8A13...D4c1",
  "limits": {
    "per_tx_usd": 150,
    "per_hour_usd": 1200,
    "per_day_usd": 6000
  },
  "allowed_contracts": [
    "0xContractRouterA",
    "0xApprovedVendorB"
  ],
  "alert_channel": "webhook://ops.example.com/oculus",
  "reserve_asset": "USDC",
  "alert_channel": "ops-wallet-alerts"
}

Spending limits

Limits are denominated in USD and evaluated at the time of verification so the same policy works across volatile onchain activity.

• Per-transaction cap — stops oversized one-off spends before they become a treasury event
• Rolling hourly and daily windows — catches loops, drip attacks, and runaway automation
• Contract allowlists — restricts execution to approved Solana programs and internal contracts
• Recipient allowlists or denylists — keeps funds away from unknown destinations
• Rate limits — alerts you when an agent's tx frequency crosses your safe threshold

Incidents

Incidents are created when a verified spend breaches an active policy. Oculus records the triggering transfer, the policy snapshot at the moment of the breach, the calculated breach amount, and the routing decision (which channels were notified).

Every incident is written to your workspace as a structured record: triggering transfer, policy snapshot at breach time, breach amount, and the alert channels notified. Incidents can be queried via API, streamed via webhook, or exported for treasury reconciliation.

TypeScript SDK

The SDK helps you register Solana activity, validate policies, and attach agent metadata from your application layer without building your own control plane.

// npm install @oculus/sdk viem
import { createPolicyClient } from "@oculus/sdk";
import { createWalletClient, http } from "viem";
import { base } from "viem/chains";

const wallet = createWalletClient({
  chain: base,
  transport: http(process.env.BASE_RPC_URL)
});

const policyClient = createPolicyClient({
  apiKey: process.env.BASEBOT_API_KEY,
  workspaceId: "ws_base_01",
  agentId: "ag_marketmaker_7",
  walletClient: wallet
});

const result = await policyClient.verifyAndRecord({
  category: "vendor_payment",
  expectedUsd: 72.4,
  recipient: "0xApprovedVendorB"
});

Webhooks

Webhook delivery is the fastest way to pipe Oculus decisions into Slack, email, your incident system, or another internal agent supervisor. Events are signed with X-Oculus-Signature.

POST /your-webhook HTTP/1.1
X-Oculus-Signature: t=1779296400,v1=3b52...

{
  "event": "claim.created",
  "agent_id": "ag_marketmaker_7",
  "tx_hash": "0xf5d9...eb42",
  "breach_type": "per_day_usd_exceeded",
  "claim_amount_usd": 214.90,
  "reserve_asset": "USDC"
}

CLI

The CLI is useful for provisioning workspaces, applying policies from JSON, backfilling Solana activity, or inspecting active claims from ops terminals.

# install
npm install -g @oculus/cli

# authenticate
oculus login

# apply a policy file
oculus policy apply ./policy.base.json

# replay the last hour of Solana activity
oculus events sync --agent ag_marketmaker_7 --since 1h

# inspect open claims
oculus claims list --status open

REST API

Base URL: https://api.basewire.app/v1. Every request is authenticated with a workspace-scoped bearer token issued from Settings → API keys.

Errors

The API returns JSON with code, message, and optional details. These are the cases you will hit most often in Base-only setups.

FAQ