Your AI Agent Now Controls Any Website.
With a Full Audit Trail.

Claude Code

Drop into yourCLAUDE.md. Claude Code will use Solace Browser for any web automation task automatically.

OpenAI Codex

Drop into yourAGENTS.md. OpenAI Codex and ChatGPT agents read this file to understand available tools and capabilities.

Cursor

Drop into your.cursorrules. Cursor will reach for Solace whenever you ask it to interact with a website.

Windsurf

Drop into your.windsurfrules. Windsurf (Codeium) picks up Solace capabilities exactly like Cursor — same format, zero friction.

GitHub Copilot

Drop into.github/copilot-instructions.md. Copilot will suggest Solace API calls for browser tasks.

Aider

Pass as a system prompt with--system-prompt solace-aider.md. Aider will route all web interactions through Solace Browser automatically.

Continue.dev

Add to your.continue/config.jsoncontext providers. Continue will surface Solace browser automation as a native tool in VS Code and JetBrains.

Cline

Drop into your.clinerules/directory. Cline reads project rules at session start — Solace capabilities load automatically for every conversation.

RooCode

Place in.roocode/rules/. RooCode (formerly Roo-Cline) inherits Solace browser capabilities alongside its agentic coding modes.

Google Gemini CLI

Add toGEMINI.mdin your project root. Google's open-source agent CLI picks up Solace instructions the same way it reads Claude'sCLAUDE.md.

Google Jules

Jules readsAGENTS.mdbefore acting on GitHub issues. Solace instructions appear automatically when Jules handles any web-related task in your repo.

Zed Editor

Place rules in.rulesat your project root. Zed's AI panel reads these natively — Solace becomes available to the Zed AI assistant instantly.

Amazon Q Developer

Add to.amazonq/rules/solace.md. Amazon Q Developer reads markdown rule files from this directory for every coding session in your project.

JetBrains AI

Add to.idea/ai-guidelines.md. JetBrains AI Assistant reads this file across IntelliJ, PyCharm, WebStorm, and all JetBrains IDEs.

Sourcegraph Cody

Place context in.cody/context/solace.md. Cody includes this file in its retrieval context — Solace instructions appear in every Cody conversation.

Tabnine

Configure via.tabnine/personalization. Tabnine's personalization file lets you teach it your team's toolchain — including Solace browser automation.

Replit AI

Add to your.replitfile's[ai]section. Replit AI reads project context from here — Solace becomes available in every Replit workspace.

Devin

Place in.devin/playbooks/. Devin reads project playbooks before starting long-horizon tasks — Solace browser tools are available for any web workflow.

Factory Droid

Factory readsAGENTS.md and .factory/configs. Droid agents inherit Solace capabilities when automating software development workflows.

Kilo Code

Add to.kilocode/rules/. Kilo Code follows the same project rules pattern as Cline — Solace instructions load for every agentic coding session.

llms.txt

Jeremy Howard standard for LLM-readable site descriptions. Drop in your project root for any LLM to understand Solace.

📷 See the Page

Screenshot any page at full resolution. Capture DOM snapshots and ARIA accessibility trees. Your agent gets structured visual + semantic data — not just raw HTML.

📄 Extract Structured Data

Run /api/evaluateto execute JavaScript and return structured JSON. Extract tables, prices, form values, or any page data directly into your agent's context.

🔒 Scoped Permissions

Request only what you need. OAuth3 tokens are scoped (browser.navigate, browser.click, browser.fill), time-bounded, and revocable. Fail-closed by design.

📋 Automatic Evidence

Every agent action is automatically logged, hash-chained, and sealed. Your agent produces an audit trail without writing a single line of logging code.

♾ Recipe Memory

Solace remembers successful workflows as recipes. On replay, your agent skips the LLM entirely and runs the cached path for $0.001 — 99% cheaper than rediscovery.

💸 Budget Enforcement

Set per-session spending limits. Pass"budget_usd": 0.05in your token request and Solace hard-stops the agent when the budget is hit — no runaway costs.

🔎 Evidence Search

Query past runs with/api/evidence/search. Agents can look up what happened in previous sessions — useful for incremental tasks like "triage emails not seen since last run."

🌎 Session Persistence

Browser sessions survive between agent calls. Log in once, reuse the session. No re-authentication overhead. Cookies, local storage, and auth tokens persist across tasks.

⚡ Parallel Tabs

Open multiple browser contexts simultaneously. Your agent can scrape 10 pages in parallel, compare results, and merge findings — all with independent evidence trails.

🤖 Multi-Agent Swarms

Spawn multiple independent Solace Browser instances. Scout agents explore; coder agents act; skeptic agents verify. Each instance has its own session, budget, and evidence chain. Orchestrate from any scheduler (cron, Cloud Run, GitHub Actions).

🛈 E-Sign & FDA Part 11

Every approved action can be e-signed: the user records “I (Phuc) reviewed and approved this action on [timestamp]”. The signature is SHA-256 sealed into the hash chain. Compliant with FDA 21 CFR Part 11 §11.100 electronic signatures.

✅ Screenshot Before You Click

Always call/api/screenshotbefore a click action. This creates an evidence record of what the agent saw before acting — critical for audit trails and debugging failed runs.

POST /api/screenshot {"full_page": false}
POST /api/click {"selector": "#submit-btn"}

🔎 Snapshot for Structure, Screenshot for Vision

Use /api/aria-snapshot(ARIA accessibility tree, JSON) when your agent needs to understand page structure. Use/api/snapshotfor raw HTML. Use/api/screenshotfor visual layout and images.

GET /api/aria-snapshot  # returns ARIA JSON tree
POST /api/snapshot      # returns raw HTML
POST /api/screenshot    # returns PNG filepath

🔒 Request Minimal Scopes

Only request the OAuth3 scopes your task needs. A read-only research task should never havebrowser.fillscope. Narrow scopes prevent accidental side effects and satisfy compliance audits.

POST /oauth3/token {
  "user_id": "local-agent",
  "scopes": ["browser.navigate",
             "browser.screenshot"],
  "ttl_seconds": 300
}

♾ Check for Existing Recipes First

Before running a workflow with LLM tokens, call/api/recipes/match. If a recipe exists for the task, replay it at $0.001. Save the LLM call for genuinely new workflows.

POST /api/recipes/match {
  "task": "gmail inbox triage"
}
# → {"hit": true, "recipe_id": "gmail-v3"}

💸 Set a Budget on Every Session

Never let an agent run without a budget ceiling. Passbudget_usdin your token request. Solace will hard-stop the session when the limit is reached rather than silently overspending.

POST https://solaceagi.com/api/v1/oauth3/token {
  "api_key": "sw_sk_..."
}
# → {"access_token":"..."}

POST https://solaceagi.com/api/v1/oauth3/tokens
Authorization: Bearer sw_sk_...
{
  "scopes": ["files.read", "files.write"]
}
# → {"token":"o3_..."}
# Use header: X-OAuth3-Token: o3_...

🌎 Reuse Sessions for Authenticated Sites

Log in once and store the session token. Pass"session_id"in subsequent API calls to reuse cookies and auth state. Eliminates login flows from every agent run.

POST /api/navigate {
  "url": "https://app.example.com/inbox",
  "session_id": "sess_abc123"
}

AEO: Agent Engine Optimization

Just as SEO optimized for search crawlers, AEO optimizes for AI agents. Solace is the first platform built with agents as first-class users — not an afterthought.

Evidence Your Agents Can't Fake

Every agent action produces a SHA-256 hash-chained receipt. Your CISO can audit what the AI did. Your board can see the evidence. No black boxes.

Recipes That Make Agents Smarter

When an agent completes a task, it becomes a recipe. Next time: $0.001 replay — no LLM tokens consumed. Agents using Solace get faster and cheaper over time.

📷 750 bytes → Full Page

The Wayback Machine stores 100KB+ raw HTML per page (100,000 TB total). Solace stores a 750-byte semantic skeleton and reconstructs an equivalent page locally. 133x smaller. Zero centralized dependency.

# Reconstruct any indexed page locally:
python3 prime_wiki_render.py \
  --url https://github.com
# → prime-wiki-renders/github-com.html

🏛 Appstore-Focused Index

Unlike Wayback Machine (entire web), Solace focuses onappstore sites— the sites that have Solace automation recipes. GitHub, Gmail, LinkedIn, Substack, Notion, and more. Quality beats coverage.

GET /api/v1/prime-wiki/search?q=github
# Returns all indexed GitHub pages

GET /api/v1/prime-wiki/stats
# {"count": 7, "rtc_verified_count": 7}

🔒 Pro: Full Community Access

Free:collect snapshots from your own browsing.
Pro ($28/mo):instantly access the full community index — semantic memory for every appstore site. Skip LLM re-discovery. Save $10–50/month in tokens.

# Download all appstore codebooks once:
GET /api/v1/prime-wiki/assets?appstore_only=true
# Store at ~/.solace/pzip/assets/
# Decompress locally, forever — offline capable

▲ Top Rail — Always Visible

A 32px bar pinned to the top of every page. Shows:[☯ Solace home]→ back to browser home with one click. Plus real-time state (IDLE / EXECUTING / PREVIEW_READY / DONE), current app name, and rotating value stats (pages visited, LLM calls, cost saved, session duration).

# Push a state update to the top rail:
POST /api/yinyang/notify
{"type": "state_update",
 "state": "EXECUTING",
 "app_name": "Gmail Triage"}

▼ Bottom Rail — Chat & Approve

A 36px collapsed chat panel at the bottom of every page. Auto-expands when state reachesPREVIEW_READY(your agent has prepared an action),BLOCKED(needs clarification), orFAILED. User clicksApprove or Decline— your agent receives the decision via WebSocket.

# WebSocket for real-time agent ↔ Yinyang:
ws://localhost:8888/ws/yinyang

# Push preview for user approval:
{"type": "bottom_rail_update",
 "payload": {
   "state": "PREVIEW_READY",
   "preview_text": "Reply to Li Li about...",
   "show_approve_reject": true,
   "run_id": "run-abc123"
 }}

🔔 Push Alerts — 3 Channels

Agents can push notifications to the user without interrupting their current page. Three channels:toast(3s bottom-right popup),popup(modal with action buttons),takeover(full-screen for critical approvals). All channels are FSM-gated — no alert fires without a valid state transition.

POST /api/yinyang/notify
{"type": "push_alert",
 "channel": "toast",
 "message": "Gmail triage complete: 12 sorted",
 "priority": "low"}

# channel: "toast" | "popup" | "takeover"
# priority: "low" | "high" | "critical"

📤 Inbox — Drafts Awaiting Review

Every draft your agent prepares (email reply, Substack post, LinkedIn comment) lands here before it’s sent. The inbox shows: sender context, agent-written draft, confidence score, estimated send time. Review and approve with one click — or edit before approving.

GET /api/v1/inbox
# {"items": [{
#   "id": "draft-abc",
#   "app": "gmail-inbox-triage",
#   "type": "email_reply",
#   "to": "li.li@...",
#   "subject": "Re: Solace user case",
#   "preview": "Hi Li Li, thanks for...",
#   "confidence": 0.91,
#   "status": "awaiting_approval"
# }]}

📥 Outbox — Sent & Scheduled

Approved items flow to the outbox. See what was sent, when, by which app, and with what evidence hash. Scheduled items show their next trigger time. Every outbox entry links to its full Part 11 evidence bundle.

GET /api/v1/outbox
# {"items": [{
#   "id": "sent-xyz",
#   "app": "gmail-inbox-triage",
#   "sent_at": "2026-03-03T14:30:00Z",
#   "to": "li.li@...",
#   "evidence_hash": "sha256:abc...",
#   "status": "sent"
# }]}

📅 Schedule & Calendar

Recurring tasks (morning brief, weekly digest, nightly archive) appear on the schedule. See next run time, last run result, and budget consumed this period. Agents can add to the schedule via API; users can pause, skip, or reschedule from the home page.

GET /api/v1/schedule
# {"items": [{
#   "app": "morning-brief",
#   "cron": "0 7 * * *",
#   "next_run": "2026-03-04T07:00:00Z",
#   "last_status": "DONE",
#   "budget_used_7d": "$0.12"
# }]}

📚 History — Recipe Run Log

Every recipe run is logged: app name, duration, tokens used, cost, outcome. Successful runs build the recipe cache for future $0.001 replays. Failed runs show where they broke and why — perfect for debugging app recipes.

GET /api/v1/history?limit=20
# {"runs": [{
#   "run_id": "run-abc",
#   "app": "gmail-inbox-triage",
#   "started": "2026-03-03T14:00:00Z",
#   "duration_s": 18,
#   "tokens": 1247,
#   "cost_usd": 0.00073,
#   "outcome": "DONE",
#   "recipe_replayed": false
# }]}

📷 FDA Part 11 Evidence

Every approved action generates a tamper-evident screenshot sequence. Accessible from the history panel: see exactly what the browser showed before your agent acted, what the agent proposed, and what was actually executed. SHA-256 hash-chained. E-signature ready.

GET /api/v1/evidence/{run_id}
# {"run_id": "run-abc",
#  "screenshots": [
#    {"step": 1, "url": "...", "sha256": "..."},
#    {"step": 2, "url": "...", "sha256": "..."}
#  ],
#  "seal": {"hash": "sha256:...",
#           "signed_at": "..."}}

📄 Prime Wiki Snapshots

When your agent visits a new site, it creates a Prime Wiki snapshot: an indexed map of all interactive elements (DOM selectors, ARIA roles, action paths). These snapshots power future recipe replay at $0.001. Accessible from the home page — browse, search, or export as Prime Mermaid FSM diagrams.

GET /api/v1/prime-wiki/list
# {"snapshots": [{
#   "domain": "mail.google.com",
#   "captured_at": "2026-03-03",
#   "selectors": 847,
#   "recipes": 3,
#   "mermaid_url": "/prime-wiki/gmail.md"
# }]}

📝 How It Works

1. Agent writes draft→ lands in Inbox withstatus: awaiting_approval
2. User edits draft→ Solace diffs original vs edited text, extracts the delta
3. User approves→ delta is stored as astyle preferencetagged to the app + recipient
4. Next run→ agent receives style preferences in its system prompt:“User prefers: shorter sign-off, no exclamation marks, always mention the reference number”
5. Score improves→ fewer edits needed over time. Convergence tracked in the history panel.

📊 Preference API

Agents can read style preferences before generating drafts. Preferences are stored per-app, per-recipient, and globally. Captured automatically when users edit — or manually teachable via API.

# Read preferences before drafting:
GET /api/v1/preferences?app=gmail-inbox-triage
# {"global": ["concise, 3 sentences max"],
#  "recipient:li.li@...": [
#    "mention reference number",
#    "no exclamation marks"
#  ]}

# User edit automatically captured:
POST /api/v1/preferences/signal
{"app": "gmail-inbox-triage",
 "original": "Hi Li Li! Thanks for...",
 "edited": "Hi Li Li, thanks for...",
 "recipient": "li.li@..."}