Business Automation

Playbooks

Complete business automation blueprints. Each playbook maps how to replace a traditional company with AI agents.

Available Now

PaymentsHigh

Agent Payments & Spend-Policy Control Plane

Enroll a card, cap the mandate, hand the agent a payment capability — not the PAN

Operator recipe for letting an agent buy mid-task without giving it a raw unbounded card. Enroll and tokenize the card once, attach a spend policy (cap, clock, merchant/API scope), issue a scoped payment capability, allow x402-style mid-task purchases inside that mandate, then revoke. Pair the payment plane with Know-Your-Agent identity (Ant International, Mastercard, and Visa interoperability work is in progress as of 2026-09-10 — not a finished shared standard) and with credential Connections that distinguish agent-owned vs caller-owned secrets. Primaries: Nevermined Pay; LangChain “Agents That Pay”; PR Newswire KYA collaboration; LangChain Connections. Related catalog tools: Nevermined, LangChain Managed Deep Agents, Stripe Link (Wallet for Agents).

2Agents
6Workflows
n/aRevenue
View Blueprint →
ComplianceMedium

Deployer Assurance Checklist (CA IVO Voluntary)

SB 813 Ch.179 is a voluntary IVO path — not a California operating license

Operator checklist for California deployers who may later want an Independent Verification Organization assessment. Senate Bill 813 (McNerney) was approved by the Governor and filed with the Secretary of State on 2026-09-09 as Chapter 179, Statutes of 2026. It directs the Government Operations Agency, on or before 1 January 2028, to develop IVO application requirements, designation criteria, and suspension procedures. Government Code §8898.4(a)(3) states the chapter does not require any person that develops, deploys, or operates an AI system or model to engage an IVO or undergo a covered AI audit as a condition of operating in California. Do not treat unsigned bills as law. Companion context from the same 2026-09-09 Governor Newsom signing post: Assembly Bill 1405 (Bauer-Kahan) creates a state registry for AI auditors — registry/independence standards, not an IVO-to-operate mandate. Primaries: LegInfo SB 813 chaptered text; Governor Newsom 2026-09-09 AI safeguards post.

1Agents
6Workflows
n/aRevenue
View Blueprint →
SecurityHigh

Harness: Permission Outside the Agent

The agent proposes; a host authority grants connectors, egress, and spend

Operator recipe from Meta’s Muse Secure VM pattern: keep permission outside the model. Sentinel (or an equivalent host authority) is the sole grantor of connector actions and network egress. The agent proposes; it does not approve. Credentials live in a vault; the runtime sees only surrogates until the host inserts the real token at an authorized boundary. Human approvals are scoped capabilities (one use, session, task, window, or standing grant) — not a chat “yes.” Treat behavioral evals and egress allowlists as acceptance tests before widening autonomy. Purchase path: single-use scoped cards (Muse partners with Stripe Link at launch; Stripe’s agent wallet issues a one-time card or shared payment token after a spend request). Primaries: Meta AI Muse security blog; Meta “Introducing Muse” (about.fb.com / Meta Newsroom); Stripe “Giving agents the ability to pay.” Related catalog tools: Stripe Link, METR Inspect Hawk, OpenAI Agents SDK (in-app harness, not the managed Agents API).

2Agents
6Workflows
n/aRevenue
View Blueprint →