# Naïve > The AI-native cloud for apps and agents. Naïve unifies software infrastructure (compute, databases, storage, model routing) and real-world capabilities (51 primitives across 9 categories) — verified identity, spend-limited cards, inbox, phone, and governed permissions — in one API and one credit balance. ## Core - [Naïve homepage](https://usenaive.ai): Product overview - [Pricing](https://usenaive.ai/pricing): Plans, pricing, and credits - [Templates](https://usenaive.ai/templates): Pre-built autonomous companies and AI employees - [Solutions](https://usenaive.ai/solutions): Agent-native solution pages (identity, wallet, cloud, …) - [Docs](https://usenaive.ai/docs): Full primitives + platform reference - [Docs LLMs.txt](https://usenaive.ai/docs/llms.txt): Full doc index for LLM crawlers - [Security](https://usenaive.ai/security): Secure by design, encryption, controls - [Open source](https://usenaive.ai/licenses): Open-source licenses - [Agent manifest (skill.md)](https://usenaive.ai/skill.md): **Read this first.** The onboarding manifest for a coding agent — the current noun set, the worked `naive.config.ts`, and exactly what this control plane serves today. It is canonical; where this index and https://usenaive.ai/skill.md disagree, skill.md wins. ## Concepts (Organization → Project → Child project → Team → Agent → Brain → Primitive) - **Organization** — the billing and policy root, addressed as `company` on the wire (`/v1/organization` is the canonical route, `/v1/company` the retired spelling of the same one). Not a legal entity and not a runtime; a Naïve-formed US LLC is one thing an organization can OWN (via the formation primitive), not what it is. - **Operator** — the human who holds the account and writes `naive.config.ts`. - **Project** — a scope inside the organization holding its account kits and child projects. Selected by `/v1/projects//…`, the `X-Naive-Project-Id` header, or a key's pinned project. Every organization has a DEFAULT project and a request that names none resolves to it, so the layer is opt-in: `naive projects list` / `naive projects use ` on the CLI, `.forProject(id)` in the SDK. - **Child project** — the operator's end customer, a `tenant_user` on the wire. Every primitive acts on one: `naive use ` / `--tenant ` on the CLI, `.forTenant(id)` / `.forProject(p).forChild(id)` in the SDK. Created with `naive users create`; nothing creates one implicitly. - **Team** — a named group of agents with exactly one **lead**, on one runtime. `runtime.durable()` is **Vetta**, ours, and is current; `runtime.hermes()` runs the Hermes harness instead and is marked deprecated in the SDK, though existing hermes teams keep working. - **Agent** — one governed worker identity. Declared as a **role** with `agent({…})`; not a person and not a process. - **Brain** — an organization's knowledge store, declared with `scope: "project"` where it is partitioned per DEPLOYMENT namespace (the `project:` key of `naive.config.ts`), which is a different object from the `projects` layer above. An organization may declare several and exactly one is the default. Replaces the `memory` primitive. - **Primitive** — one governed capability lane an agent can call (incorporation, banking, email, browser, payments, …). 51 primitives across 9 categories. ## Primitives (canonical pages) - [Primitives directory](https://usenaive.ai/developers/primitives): Browse all primitives by category - [/verification — Verification](https://usenaive.ai/developers/primitives/verification): Hosted identity verification (KYC) for founders. · [docs](https://usenaive.ai/docs/getting-started/verification) - [/formation — Formation](https://usenaive.ai/developers/primitives/formation): A real US company — KYC to EIN. · [docs](https://usenaive.ai/docs/getting-started/formation) - [/domains — Domains](https://usenaive.ai/developers/primitives/domains): Auto-provisioned and custom domains with agent DNS editing. · [docs](https://usenaive.ai/docs/getting-started/domains) - [/email — Email](https://usenaive.ai/developers/primitives/email): Custom-domain inboxes — send and receive. · [docs](https://usenaive.ai/docs/getting-started/email) - [/phone — Phone](https://usenaive.ai/developers/primitives/phone): Provision US numbers — send and receive SMS. · [docs](https://usenaive.ai/docs/getting-started/phone) - [/profile — Profile](https://usenaive.ai/developers/primitives/profile): The agent's own profile — email and name. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/cards — Cards](https://usenaive.ai/developers/primitives/cards): Scoped virtual cards with hard spend limits. · [docs](https://usenaive.ai/docs/getting-started/cards) - [/payments — Wallet](https://usenaive.ai/developers/primitives/payments): A per-agent crypto wallet with x402 stablecoin payments. · [docs](https://usenaive.ai/docs/getting-started/payments) - [/trading — Trading](https://usenaive.ai/developers/primitives/trading): Connect brokerage accounts, place orders, and stream market data. · [docs](https://usenaive.ai/docs/getting-started/trading) - [/billing — Billing](https://usenaive.ai/developers/primitives/billing): One credit balance for every primitive — top up once. · [docs](https://usenaive.ai/docs/getting-started/billing) - [/browser — Browser](https://usenaive.ai/developers/primitives/browser): Autonomous signup and login — credentials vaulted. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/mobile — Mobile](https://usenaive.ai/developers/primitives/mobile): Cloud mobile emulators and devices via Mobilerun. · [docs](https://usenaive.ai/docs/getting-started/mobile) - [/connections — Connections](https://usenaive.ai/developers/primitives/connections): Let agents connect Gmail, calendars, and any OAuth account. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/images — Images](https://usenaive.ai/developers/primitives/images): Generate AI images and pull licensed stock photos. · [docs](https://usenaive.ai/docs/getting-started/images) - [/video — Video](https://usenaive.ai/developers/primitives/video): Generate AI video with Kling, Minimax, and Wan. · [docs](https://usenaive.ai/docs/getting-started/video) - [/clips — Clips](https://usenaive.ai/developers/primitives/clips): Create short-form video clips. · [docs](https://usenaive.ai/docs/getting-started/clips) - [/media — Media library](https://usenaive.ai/developers/primitives/media): One library for every image, video, and clip your agent makes. · [docs](https://usenaive.ai/docs/getting-started/media) - [/audio — Audio](https://usenaive.ai/developers/primitives/audio): Transcription, speech, and native audio conversations through one router. · [docs](https://usenaive.ai/docs/getting-started/audio) - [/social — Social](https://usenaive.ai/developers/primitives/social): Post and schedule across 10+ social platforms. · [docs](https://usenaive.ai/docs/getting-started/social) - [/llm — LLM](https://usenaive.ai/developers/primitives/llm): Chat completions across 300+ models through one router. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/search — Search](https://usenaive.ai/developers/primitives/search): Real-time web search, URL extraction, and deep research. · [docs](https://usenaive.ai/docs/getting-started/search) - [/brain — Brain](https://usenaive.ai/developers/primitives/brain): Company knowledge base + memory with grounded answers and provable deletion. · [docs](https://usenaive.ai/docs/getting-started/brain) - [/seo — SEO](https://usenaive.ai/developers/primitives/seo): Keyword research, backlinks, and competitor analysis. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/aeo — AEO](https://usenaive.ai/developers/primitives/aeo): AI search optimization and LLM response tracking. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/app-data — App data](https://usenaive.ai/developers/primitives/app-data): App rankings, reviews, and metadata from app stores. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/business — Reviews & listings](https://usenaive.ai/developers/primitives/business): Reviews, reputation, and place intelligence — from two providers. · [docs](https://usenaive.ai/docs/getting-started/business-places) - [/ecommerce — E-commerce](https://usenaive.ai/developers/primitives/ecommerce): Product listings, pricing, and sellers from Google and Amazon. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/company-data — Company data](https://usenaive.ai/developers/primitives/company-data): Company firmographics, funding, investors and tech stack. · [docs](https://usenaive.ai/docs/getting-started/company-data) - [/people — People](https://usenaive.ai/developers/primitives/people): B2B people search and work-contact enrichment. · [docs](https://usenaive.ai/docs/getting-started/people) - [/social-data — Social data](https://usenaive.ai/developers/primitives/social-data): Public posts from X, Reddit, Instagram, TikTok, YouTube, Bluesky and Hacker News. · [docs](https://usenaive.ai/docs/getting-started/social-data) - [/apps — Apps](https://usenaive.ai/developers/primitives/apps): Ship fullstack Next.js apps with a managed backend built in. · [docs](https://usenaive.ai/docs/getting-started/apps) - [/database — Database](https://usenaive.ai/developers/primitives/database): Managed Postgres — SQL, CRUD, and migrations. · [docs](https://usenaive.ai/docs/getting-started/database) - [/storage — Storage](https://usenaive.ai/developers/primitives/storage): File storage buckets for every app your agent ships. · [docs](https://usenaive.ai/docs/getting-started/storage) - [/functions — Edge functions](https://usenaive.ai/developers/primitives/functions): Ship backend logic to the edge — no separate platform. · [docs](https://usenaive.ai/docs/getting-started/functions) - [/auth — Auth](https://usenaive.ai/developers/primitives/auth): Drop-in sign-in for the apps your agent builds. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/compute — Compute](https://usenaive.ai/developers/primitives/compute): Run containers and long-running workloads that scale on demand. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/queue — Queue](https://usenaive.ai/developers/primitives/queue): Durable message queues (SQS) for agent pipelines. · [docs](https://usenaive.ai/docs/getting-started/queue) - [/sandbox — Sandbox](https://usenaive.ai/developers/primitives/sandbox): Disposable code sandboxes agents can spin up in seconds. · [docs](https://usenaive.ai/docs/getting-started/sandbox) - [/agents — Agents](https://usenaive.ai/developers/primitives/agents): Long-horizon agents that wake on a schedule, spend a budget, and deliver. · [docs](https://usenaive.ai/docs/agents/overview) - [/approvals — Approvals](https://usenaive.ai/developers/primitives/approvals): Human-in-the-loop enforcement at the primitive boundary. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/vault — Vault](https://usenaive.ai/developers/primitives/vault): Per-user encrypted credentials — retrieved at runtime, never in prompts. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/sessions — Sessions](https://usenaive.ai/developers/primitives/sessions): Revocable MCP sessions — identity and policy travel with every call. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/logs — Logs](https://usenaive.ai/developers/primitives/logs): Per-user activity audit trail. · [docs](https://usenaive.ai/docs/getting-started/logs) - [/jobs — Jobs](https://usenaive.ai/developers/primitives/jobs): Track every async job — renders, formations, deploys — in one API. · [docs](https://usenaive.ai/docs/getting-started/introduction) - [/webhooks — Webhooks](https://usenaive.ai/developers/primitives/webhooks): Real-time events from every primitive, pushed to your backend. · [docs](https://usenaive.ai/docs/getting-started/introduction) ## Primitives (DEPRECATED — frozen orchestration runtime, do not build new work on these) - [/memory — Memory](https://usenaive.ai/developers/primitives/memory): DEPRECATED. Use instead: the **brain**: `naive brain remember` / `naive brain attach`, or `self.brain` in-agent - [/ceo — CEO](https://usenaive.ai/developers/primitives/ceo): DEPRECATED. Use instead: a `team({ lead })` on `runtime.durable()`; work is submitted with `naive teams submit` - [/employees — Employees](https://usenaive.ai/developers/primitives/employees): DEPRECATED. Use instead: declare a role with `agent({…})` inside `team({ lead, agents })`, then `naive up` - [/objectives — Objectives](https://usenaive.ai/developers/primitives/objectives): DEPRECATED. Use instead: no direct replacement yet — a goal is submitted per run, not stored as a standing object - [/tasks — Tasks](https://usenaive.ai/developers/primitives/tasks): DEPRECATED. Use instead: `naive teams submit --tenant `; read the board with `naive teams board` - [/cron — Cron](https://usenaive.ai/developers/primitives/cron): DEPRECATED. Use instead: recurring work on a team (`naive teams schedule`) — declared, and refused today; see *What is served today* ## Blog - [Blog index](https://usenaive.ai/blog) - [Introducing Vetta: the most efficient harness for long-horizon tasks](https://usenaive.ai/blog/introducing-vetta): Vetta is our agent harness for work measured in hours. With the model held fixed and only the wrapper changed, it costs $0.2232 per task against $0.5995 for the next-best harness — 2.7x cheaper, while completing more of them. - [Sole-proprietor phone numbers: provision SMS without an LLC](https://usenaive.ai/blog/sole-proprietor-phone-numbers): The /phone primitive now supports a sole-proprietor tier — provision a carrier-registered US number with passed KYC and an SMS OTP, no LLC formation or EIN required. - [defineProject: strict, honest agent infrastructure as code](https://usenaive.ai/blog/defineproject-strict-agent-infrastructure): naive.config.ts gets a strict entrypoint. defineProject refuses any declared field nothing consumes, kits: becomes the canonical declare-now-instantiate-later block, and every team runs durable by default — hermes only when you say so. - [Introducing /sandbox: Disposable micro-VMs for every agent](https://usenaive.ai/blog/introducing-sandbox): Give any agent an isolated Linux micro-VM in one call — run shell commands, read and write files, expose ports at public URLs, checkpoint the whole machine, and fork copies of it. Billed only for the CPU, memory, and disk it actually uses; sleeping and parked sandboxes are free. No cloud account, no Docker, no infra. - [What Is AI Agent Infrastructure? Governed Profiles, Primitives, and Policy](https://usenaive.ai/blog/what-is-ai-agent-infrastructure): AI agent infrastructure is the governed real-world layer agents need to act — per-tenant identity, primitives, cloud when needed, and policy at the tool boundary. How Naïve fits. - [What Is an AI-Native Cloud? The Hosting Slice Agents Can Call](https://usenaive.ai/blog/what-is-an-ai-native-cloud): An AI-native cloud is the hosting and data-plane slice agents can provision by API — apps, Postgres, storage, functions, compute, queues — under the same governed identity as other primitives. Not a hyperscaler replacement. - [Introducing /audio: give your agent ears and a voice](https://usenaive.ai/blog/introducing-audio): Transcription, speech synthesis, and native audio conversations across a managed catalog of speech models — one endpoint, automatic routing with fallbacks, exact-cost billing in Naïve credits, and no speech-provider accounts to manage. - [Build a Gusto payroll and onboarding readiness agent](https://usenaive.ai/blog/how-to-build-a-gusto-payroll-and-onboarding-readiness-agent): Multi-tenant Gusto readiness on Naïve: read-only payroll blockers and onboarding status, Account Kit tool allowlists, full connect lifecycle, client.llm summaries. - [Introducing /payments: let your AI agent pay for x402 resources in USDC](https://usenaive.ai/blog/introducing-payments): Give each agent its own crypto wallet and let it settle x402 paywalls autonomously — quote the price, pay in USDC on Base, and reconcile every receipt, with the spend cap enforced inside the custody plane. - [Introducing /wallet: a per-agent crypto wallet with a custody-plane spend cap](https://usenaive.ai/blog/introducing-wallet): Give each agent its own onchain crypto wallet — read its address and balance, and, as an operator, fund it, transfer, set the spend policy, and sweep it. The private key never enters the agent runtime and the spend cap is enforced inside the custody plane. - [Governed HR agents in your customers' existing Gusto companies](https://usenaive.ai/blog/naive-supports-gusto-for-agent-hr): Connect each customer's Gusto company to a governed agent profile on Naïve — read-only payroll and onboarding readiness today, with kit-level tool policy and audit. - [How Agents Run SEO Keyword Research Loops](https://usenaive.ai/blog/how-agents-run-seo-keyword-research-loops): Run a governed SEO keyword research loop per tenant with AgentSEO — volume, SERP competitors, and Labs insights via forUser, plan-metered and audit-logged. - [How Agents Track Brand Mentions in AI Search](https://usenaive.ai/blog/how-agents-track-brand-mentions-in-ai-search): Track how ChatGPT, Claude, Gemini, and Perplexity mention your brand with AgentAEO — LLM responses, mention search, and AI keyword volume per tenant. - [How to Build a Usage-Metered AI SEO SaaS](https://usenaive.ai/blog/how-to-build-a-usage-metered-seo-saas): Build a multi-tenant AI SEO/AEO SaaS with Customer Billing: plans enforce quotas at execution time — 429 on overage, forbidden when a primitive is off-tier. - [Audit Logging for AI Agent Actions](https://usenaive.ai/blog/audit-logging-for-ai-agent-actions): Audit logging for AI agent actions: one immutable trail per tenant user — who acted, what ran, approval outcome, and spend — from the gateway. - [How Agents Manage Subscription Spend With Virtual Cards](https://usenaive.ai/blog/how-agents-manage-subscription-spend-with-virtual-cards): Issue per-tool virtual cards for AI agents buying SaaS subscriptions — monthly caps on the card network, approval gates, and instant revocation on churn. - [How Agents Receive 2FA Codes With a Phone Number](https://usenaive.ai/blog/how-agents-receive-2fa-codes-with-a-phone-number): Give each tenant agent a dedicated US phone number for inbound SMS — 2FA codes scoped per customer and readable through the governed Naïve /phone API. - [How Agents Use Virtual Cards for Event Bookings](https://usenaive.ai/blog/how-agents-use-virtual-cards-for-event-bookings): Give each event agent a spend-capped virtual card for venue deposits, tickets, and vendor payments — hard limits and approval gates enforced at execution time. - [How AI Employees Work: The Specialized Workforce Behind an Autonomous Company](https://usenaive.ai/blog/how-ai-employees-work): AI employees are specialized agents scoped to one Company — own identity, inbox, and primitive whitelist. How a Naïve workforce is structured and dispatched. - [How to Give an AI Agent a Virtual Card With a Spend Limit](https://usenaive.ai/blog/how-to-give-an-ai-agent-a-virtual-card-with-a-spend-limit): Give an AI agent a virtual card with a spend limit: issue per tenant user, cap in the Account Kit, and enforce every charge at the gateway. - [How to Set a Budget Cap on an AI Agent](https://usenaive.ai/blog/how-to-set-a-budget-cap-on-an-ai-agent): How to set a budget cap on an AI agent: combine agent-profile budget with Account Kit card limits so spend is enforced server-side, not in the prompt. - [Naïve Inside Your Agent Framework (Governed Tools, Any Orchestrator)](https://usenaive.ai/blog/naive-inside-your-agent-framework): Naïve as the governed tool layer under any agent framework — keep your orchestrator; add identity, connections, caps, and approvals via agentTools() or MCP. - [Naïve supports Browserbase for Agent Browser Automation](https://usenaive.ai/blog/naive-supports-browserbase-for-agent-browser-automation): Naïve supports Browserbase for agent browser automation — cloud browser sessions via /browser on one governed identity, with signup, login, and vault-backed credentials. - [Naïve supports Doola for Agent Incorporation](https://usenaive.ai/blog/naive-supports-doola-for-agent-incorporation): Naïve supports Doola for agent incorporation — US LLC formation through /formation on one governed identity, filed via Doola after KYC and checkout. - [Naïve supports Resend for Agent Email](https://usenaive.ai/blog/naive-supports-resend-for-agent-email): Naïve supports Resend for agent email — real inboxes and send/receive through /email on one governed identity, with domain verification and deliverability built in. - [OAuth for AI Agents: Per-User Connections](https://usenaive.ai/blog/oauth-for-ai-agents-per-user-connections): OAuth for AI agents should be per-user: each tenant connects their own apps — scoped by Account Kit, stored as connections, not shared tokens. - [Tenant Isolation in a Multi-Agent SaaS](https://usenaive.ai/blog/tenant-isolation-in-a-multi-agent-saas): Tenant isolation in a multi-agent SaaS: every resource attaches to one tenant user — verify forUser scoping and cross-tenant tests before production. - [What Is an AI Agent Identity?](https://usenaive.ai/blog/what-is-an-ai-agent-identity): An AI agent identity is the governed record an agent acts as — tenant user, Account Kit, resources, and audit trail — not the model or the API key alone. - [What Is an MCP Session?](https://usenaive.ai/blog/what-is-an-mcp-session): An MCP session is a short-lived, per-user credential that scopes an agent runtime to one tenant's governed tools — not your workspace API key. - [Why Consolidate Agent Infra on One Governed Identity](https://usenaive.ai/blog/why-consolidate-agent-infra-on-one-governed-identity): One governed identity per tenant beats a stitched vendor stack — cards, email, vault, connections, and KYC on the same account, enforced at execution time. - [Delegated, Revocable Access with Per-User MCP Sessions](https://usenaive.ai/blog/delegated-revocable-mcp-sessions-for-ai-agents): Per-user MCP sessions give AI agents delegated, revocable access — short-lived, kit-scoped credentials instead of your workspace key. Here's the pattern. - [Hosted vs Bring-Your-Own Runtime for AI Agents](https://usenaive.ai/blog/hosted-vs-bring-your-own-runtime-for-ai-agents): Hosted vs bring-your-own runtime for AI agents: Naïve is runtime-agnostic — governance applies at the tool-call boundary either way. Compare both paths. - [How to Add Human Approval to an AI Agent](https://usenaive.ai/blog/how-to-add-human-approval-to-an-ai-agent): How to add human approval to an AI agent: gate sensitive actions on your Account Kit, surface pending approvals, and replay on approve. A step-by-step guide. - [How to Revoke an AI Agent's Access Instantly](https://usenaive.ai/blog/how-to-revoke-ai-agent-access-instantly): How to revoke an AI agent's access instantly: suspend the agent profile or revoke an MCP session so the governance gateway denies all further tool calls. - [Spend Caps, Approvals & Revocation for AI Agents](https://usenaive.ai/blog/spend-caps-approvals-revocation-for-ai-agents): Spend caps, human approvals, and instant revoke for AI agents must be enforced server-side — Naïve's governance gateway applies all three on every call. - [The Governed Agent Profile: End-to-End Control for AI Agents](https://usenaive.ai/blog/the-governed-agent-profile): A governed agent profile is an AI agent with identity, spend limits, approvals, audit, and instant revoke — enforced on every action. Here's the full lifecycle. - [Build an Agentic Collections Platform (Dunning That Runs Itself — Under Permission)](https://usenaive.ai/blog/how-to-build-an-agentic-collections-platform): Build a multi-tenant collections agent on Naïve: cron runs dunning on schedule, memory tracks each debtor's stage, and Account Kits gate every action. - [How to Build a Multi-Tenant AI Brand-Protection Agent](https://usenaive.ai/blog/how-to-build-a-brand-protection-agent): Build an agentic domain-defense platform that watches for lookalike and typosquat domains, investigates live impersonation with OpenRouter's web-search server tool, and registers defensive domains — where no registration ever spends money without passing an execution-time approval gate. Full build on the Naïve SDK: per-tenant identity, AccountKit capability tiers, and the /domains primitive. - [Build an Agentic Mobile QA Platform: Isolated Cloud Phones, Approval-Gated Provisioning, and Metered Per-Tenant Billing](https://usenaive.ai/blog/how-to-build-an-agentic-mobile-qa-platform): Build a multi-tenant AI mobile-QA platform on Naïve: each customer gets isolated cloud phones, agents run plain-English test flows on real devices, provisioning and runs are approval-gated, and every device-minute is metered per tenant — without ever holding a Mobilerun key. - [Build an Agentic Data-Pipeline Platform (Where the Agent Can't Run Code Without Sign-Off)](https://usenaive.ai/blog/how-to-build-an-agentic-data-pipeline-platform): Build a multi-tenant data-pipeline platform on Naïve where an LLM writes the transform and runs it in a per-tenant isolated container — but spinning up compute and opening a shell freeze for a human at execution time, and no agent ever holds a cloud key. - [AI Agent Permissions, Enforced at Execution Time](https://usenaive.ai/blog/ai-agent-permissions): AI agent permissions should be enforced server-side at execution time, not prompted. Here's how policy templates gate primitives, apps, and approvals. - [Building AI Agents Into Your SaaS: The Multi-Tenant Playbook](https://usenaive.ai/blog/building-ai-agents-into-your-saas): Building multi-tenant AI agents into your SaaS means giving each customer an isolated, governed agent. Here's the full architecture and how to ship it. - [How to Build an Agentic Appointment Reminder & No-Show Recovery Agent](https://usenaive.ai/blog/how-to-build-an-agentic-appointment-reminder-agent): Build a two-way SMS agent that texts appointment reminders, reads replies, and reschedules no-shows automatically — on a real US number your agent legally can't fake. Full build with Naive's phone, identity, and LLM primitives, with execution-time permission enforcement shown at every step. - [How to Store API Keys for AI Agents Safely](https://usenaive.ai/blog/how-to-store-api-keys-for-ai-agents): How to store API keys for AI agents safely: keep the key out of the prompt, encrypt it per user, and let the agent use it server-side. A step-by-step guide. - [Multi-Tenant AI Agents: One Agent Per Customer, Isolated by Default](https://usenaive.ai/blog/multi-tenant-ai-agents): Multi-tenant AI agents give every customer their own isolated agent. Here's the operator, tenant-user, and Account Kit model behind per-user isolation. - [Secrets Your AI Agent Can Use but Never Sees](https://usenaive.ai/blog/secrets-management-for-ai-agents): Secrets management for AI agents means letting an agent use a credential without exposing it to the model. Here's the per-tenant vaulting pattern that fixes it. - [What Is an Account Kit?](https://usenaive.ai/blog/what-is-an-account-kit): An Account Kit is a reusable policy template that governs what a tenant user's AI agents can do — which primitives are enabled and which apps they can connect. - [Build an Agentic Ad-Buying Platform (Where Every Agent Gets a Card With an Issuer-Enforced Ceiling)](https://usenaive.ai/blog/how-to-build-an-agentic-ad-buying-platform): Build a multi-tenant ad-buying platform on Naïve where each client's agent gets its own funded virtual card with a hard, issuer-enforced ceiling — the spend cap the prompt can't cross. - [Build an Agentic Operator for Tools with No OAuth (Where the Agent Uses a Password It Can Never Read)](https://usenaive.ai/blog/how-to-build-an-agentic-no-api-operator): Build a multi-tenant agent on Naïve for tools with no OAuth or API: the vault holds each customer's secrets, including write-only passwords it can never read. - [Introducing /browser: give your agents a governed web session](https://usenaive.ai/blog/introducing-browser): Browser sessions your agents drive — navigate, act, extract — plus autonomous signup and login that vault credentials, scoped per user and watchable live. - [Introducing /connections: connect each user's agents to 1,000+ apps](https://usenaive.ai/blog/introducing-connections): The connections primitive gives each end-user's agents authenticated access to 1,000+ third-party apps — per user, gated by the Account Kit, in one surface. - [Introducing /vault: per-user encrypted storage for agent secrets](https://usenaive.ai/blog/introducing-vault): The vault primitive: per-user encrypted storage for the secrets your agents hold — API keys, cookies, tokens — envelope-encrypted with a managed KMS. - [Build an Agentic Inbox Copilot: a Multi-Turn OpenRouter Tool-Use Loop, Bounded Per User at Execution Time](https://usenaive.ai/blog/how-to-build-an-agentic-inbox-copilot): Build an agentic inbox copilot on Naïve: a multi-turn OpenRouter tool-use loop bounded per user at execution time by their Account Kit over Gmail and Slack. - [Build an Agentic Access-Governance Platform (Where the Agent Can Onboard a Hire but Is Gated from Offboarding Outside Its Tier)](https://usenaive.ai/blog/how-to-build-an-agentic-access-governance-platform): Build an agentic access-governance platform on Naïve where each company's Account Kit decides per tool which GitHub and Slack actions the agent may run. - [Build a Bring-Your-Own-Agent Platform: Hand Each Customer's AI a Scoped, Revocable MCP Session](https://usenaive.ai/blog/how-to-build-a-bring-your-own-agent-platform): Build a bring-your-own-agent platform on Naïve: mint each customer a short-lived, revocable MCP session that's scoped and filtered by their Account Kit. - [Build a Multi-Tenant AI Social Media Manager (Where the Plan Tier Decides — at Execution Time — Whether the Agent Can Publish)](https://usenaive.ai/blog/how-to-build-a-multi-tenant-ai-social-media-agent): Build a multi-tenant AI social media manager on Naïve where each brand's plan-tier Account Kit decides at execution time whether the agent may publish. - [Build a Multi-Tenant AI Answer-Engine-Optimization (AEO/GEO) Platform](https://usenaive.ai/blog/how-to-build-an-agentic-aeo-platform): A code-first tutorial for building an agentic AEO/GEO product on Naïve — give every brand an AI agent that audits how ChatGPT, Claude, Gemini, and Perplexity answer questions about them, finds the keyword and citation gaps with SEO data, writes answer-optimized content with an OpenRouter model, and publishes to their own connected CMS. Each customer is an isolated tenant user, governed by an Account Kit and a Customer-Billing plan, with usage metered and quota-enforced at execution time and sensitive actions frozen for human approval. - [Build a Multi-Tenant AI Support Agent (Where the Plan Tier Decides What It Can Touch)](https://usenaive.ai/blog/how-to-build-an-agentic-customer-support-platform): Build a multi-tenant AI customer-support platform on Naïve: each customer's agent reads their inbox, drafts replies, and refunds only where the plan permits. - [Build an Agentic Accounts-Payable Platform (Where No Invoice Gets Paid Without Permission)](https://usenaive.ai/blog/how-to-build-an-agentic-accounts-payable-platform): Build a multi-tenant AI accounts-payable platform on Naïve: an agent reads invoices, extracts line items, and pays each bill from a capped per-invoice card. - [Build an Agentic Incorporation Platform (Where No Company Gets Filed Without Human Approval)](https://usenaive.ai/blog/how-to-build-an-agentic-incorporation-platform): Build an agentic incorporation platform on Naïve: an AI agent designs the entity, KYCs founders, and files a real US LLC, with every binding step approval-gated. - [Build a Multi-Tenant AI Email Marketing Platform (Where Each Customer's Plan Is Enforced at Send Time)](https://usenaive.ai/blog/how-to-build-an-agentic-email-marketing-platform): Build a multi-tenant AI email-marketing SaaS on Naïve: an agent drafts and sends from each customer's own inbox, with plan quotas enforced at send time. - [Introducing /compute: Run Docker containers, workers & cron jobs from one call](https://usenaive.ai/blog/introducing-compute): Spin up agent-owned Docker workloads on managed cloud compute — long-running services with public URLs, run-to-completion batch jobs, and scheduled (cron-for-code) jobs — metered by the second, isolated per tenant, with an interactive shell. No AWS account, no cluster, no DevOps. - [Introducing /phone: Give your AI agent a real phone number for SMS](https://usenaive.ai/blog/introducing-phone): Provision a real US phone number for any AI Employee — send and receive SMS — with carrier (10DLC) registration handled at provisioning. Inbound works immediately; outbound unlocks automatically on campaign approval. - [Introducing /queue: Durable work queues for agent pipelines](https://usenaive.ai/blog/introducing-queue): Durable message queues for your agents — managed Amazon SQS (standard & FIFO, with dead-letter queues) for producer/consumer fan-out, buffering, and retries. The natural pairing for compute workers. No AWS account, one bearer token. - [Build an Agentic Robo-Advisor (Where Trades Freeze for Approval Before They Execute)](https://usenaive.ai/blog/how-to-build-an-agentic-robo-advisor): Build a multi-tenant agentic robo-advisor on Naïve: each client links their brokerage, an AI agent proposes a rebalance, and every order freezes for approval. - [How to Build an Agentic Corporate Travel Agent With Server-Side Policy Enforcement](https://usenaive.ai/blog/how-to-build-an-agentic-travel-agent): Build a multi-tenant corporate travel desk with the Naïve SDK: an AI agent that researches, ranks, and books hotels, with spend capped and approvals enforced. - [Build a Multi-Tenant AI Sales Agent (Where Every Rep's Agent Has Its Own Identity)](https://usenaive.ai/blog/how-to-build-a-multi-tenant-ai-sales-agent): Build a multi-tenant AI sales agent on Naïve: each rep's agent researches leads, drafts with OpenRouter, sends from their own Gmail, and spends under approval. - [Introducing /trading: let your AI agent trade stocks, options & crypto](https://usenaive.ai/blog/introducing-trading): Link a user's brokerage account via OAuth and trade stocks, options, and crypto through one Naïve key — account, positions, orders, and market data, with money-moving actions human-approval-gated by default. Naïve is the governed gateway; the connected brokerage is the broker. - [Launching the Naïve Developer Platform: existence infrastructure for AI agents](https://usenaive.ai/blog/launching-the-naive-developer-platform): The Naïve Developer Platform turns every Naïve primitive into a multi-tenant building block for your own products. 38 primitives across 8 groups, four surfaces (SDK, CLI, MCP, REST), per-customer isolation, governance, and metered billing — so you can give every AI agent a real existence. - [Getting started with the Naïve SDK: one TypeScript client for all of agent infrastructure](https://usenaive.ai/blog/introducing-the-naive-sdk): The new @usenaive-sdk/server is a single, Stripe-style TypeScript client for every Naïve primitive — email, cards, apps, LLM, vault, and more — with first-class multi-tenancy and a drop-in agent toolset. A getting-started guide. - [Introducing the governance layer: approvals, logs, sessions, and jobs](https://usenaive.ai/blog/introducing-governance): Human-in-the-loop approvals that freeze sensitive actions until you say yes, a per-user audit trail of everything an agent did, short-lived scoped MCP sessions, and unified async job tracking — the controls that make an autonomous fleet safe to run. - [Introducing /billing: meter and monetize your own agent users](https://usenaive.ai/blog/introducing-billing): Define plans that map to an Account Kit, a Stripe price, and usage quotas — then reflect each customer's subscription and read their metered usage. The monetization layer for building a multi-tenant product on Naïve. - [Introducing market intelligence: app stores, marketplaces, and review data](https://usenaive.ai/blog/introducing-market-data): App Store and Google Play rankings, Amazon and Google Shopping product data, and Google Business, Trustpilot, and TripAdvisor reviews — structured competitive and market intelligence your agent can query through one key. - [Naïve Engineering Lessons: How We Burned $450K in One Month](https://usenaive.ai/blog/how-we-burned-450k-in-one-month): We gave every free signup its own always-on machine and $10 of model credits. At launch traffic, that became a $450K month. - [Introducing /seo and /aeo: rank in Google and show up in AI answers](https://usenaive.ai/blog/introducing-seo): Keyword volume, backlinks, SERP competitors, and ranked-keyword data for classic search — plus AEO/GEO visibility into whether ChatGPT, Claude, Gemini, and Perplexity actually mention you. The full visibility stack behind one key. - [Launching the Naïve Agent SDK: Identity, payments, and standing for every agent](https://usenaive.ai/blog/launching-the-agent-sdk): Launch the Naïve Agent SDK: one interface for agent identity, 40+ primitives, scoped cards, and real-world standing — multi-tenant, with audit logs, spend limits, and per-user MCP sessions. - [Introducing /clips and /media: turn long video into shorts and manage every asset](https://usenaive.ai/blog/introducing-clips): Clip long-form video into captioned, ready-to-post shorts in one call, and keep every generated or uploaded asset in a managed media library — the production layer for an autonomous content business. - [Introducing /llm: 300+ models behind one key, billed in credits](https://usenaive.ai/blog/introducing-llm): OpenAI-compatible chat completions across 300+ models with provider routing and fallbacks — streaming included, no per-provider keys, billed in Naïve credits at the exact upstream cost. Plus a drop-in OpenRouter proxy so your existing code just changes a base URL. - [Introducing the backend stack: Postgres, storage, auth, and edge functions for agent-built apps](https://usenaive.ai/blog/introducing-backend): Every fullstack app your agent ships gets a managed Postgres database, file storage, end-user auth, and edge functions — driven through one API key, with no Supabase dashboard and no service-role secrets ever leaving the runtime. - [How to Build a Faceless Clipping Channel Business in 2026](https://usenaive.ai/blog/how-to-build-a-faceless-clipping-channel): Step-by-step guide to starting a faceless YouTube Shorts, TikTok, and Instagram Reels clipping channel — from niche selection and AI-powered video clipping to automated publishing, monetization, and scaling to multiple channels. No filming, no editing, no on-camera presence required. - [What Is an Autonomous Company? A Founder's Guide](https://usenaive.ai/blog/what-is-an-autonomous-company): An autonomous company is a real legal entity run by AI employees instead of humans. Here's what one looks like, what it can actually do today, and how a non-technical founder can start one. - [Introducing /apps: Ship web applications from a single prompt](https://usenaive.ai/blog/introducing-apps): Create, build, deploy, and manage managed Next.js apps with dedicated AI engineer agents — preview deployments, production promotion, custom domains, environment variables, and with an optional managed database, all from the CLI or API. - [Introducing /orchestration: Turn your AI agent into an autonomous company](https://usenaive.ai/blog/introducing-orchestration): AI workforce orchestration with a CEO agent, kanban task board, strategic objectives, cron scheduling, and persistent memory — so your agent can plan, delegate, and execute multi-step workflows without manual supervision. - [Launching the Naïve Studio: Run an autonomous company from a single chat](https://usenaive.ai/blog/launching-the-naive-studio): Naïve Studio is a complete platform for running autonomous AI companies — a CEO agent powered by Hermes, a kanban task board, AI employees, 18+ business primitives, a hosted MCP server, and an agent-native CLI. No Paperclip, no wrappers, no vendor lock-in. - [Naïve removes Paperclip: Our v2 switch to Hermes](https://usenaive.ai/blog/naive-removes-paperclip-switch-to-hermes): Naïve Studio v2 swaps Paperclip for Hermes as the default orchestration framework. Hermes ships a durable multi-agent kanban, named agent profiles, persistent memory, and a stronger built-in runtime. Here's the honest comparison — and why our focus has always been the primitives layer, not the runtime. - [Introducing /formation: Company formation for AI agents](https://usenaive.ai/blog/introducing-formation): Form a US LLC from your AI agent via KYC, hosted checkout, and end-to-end LLC filing. Registered agent, state filing, and EIN application are included in the published formation fee; the Company becomes the substrate for cards, domains, and email. - [Introducing /kyc: Pass identity verification when your customer is an agent](https://usenaive.ai/blog/introducing-kyc): Verify the identity of an Employee — the principal behind every autonomous business — with hosted KYC, per published verification docs, and PII handled outside plaintext on Naïve servers. - [Introducing /cards: give your AI agent virtual cards with hard limits](https://usenaive.ai/blog/introducing-cards): Issue virtual cards for your agents — a prepaid gift card or a managed virtual card — funded via checkout, capped by a spending limit, and fully audited. - [Introducing /email: Send and receive email from any AI agent](https://usenaive.ai/blog/introducing-email): Provision a real email address for every AI Employee with DKIM, SPF, and DMARC configured automatically. Send, receive, schedule, and triage — with deliverability built for agent-volume sending. - [Introducing /social: Provision and post to social accounts from your agent](https://usenaive.ai/blog/introducing-social): Cross-post to the social platforms exposed in the published Naive docs (10 in the MCP connect enum). Provision connected accounts, post natively, fetch analytics, and manage comments — through documented OAuth and posting flows. - [Introducing /video: Generate video from your agent in one call](https://usenaive.ai/blog/introducing-video): Produce text-to-video and image-to-video output from a single Naïve call, routed through Naïve's model catalog models (Kling, Minimax, Wan, and more) — composed with /image, /social, and /brand. - [Introducing /image: Generate logos, brand assets, and marketing imagery on demand](https://usenaive.ai/blog/introducing-image): Generate logos, brand assets, and marketing imagery from any AI Employee. FLUX and Recraft models, plus additional models from the live catalog (see docs) — composed with /brand for consistent prompts. - [Introducing /domain: Buy domains and configure DNS programmatically](https://usenaive.ai/blog/introducing-domain): Connect, verify, purchase, and manage domains for a Company — including DNS on the live zone and email-provider records — per the published Domain Management guide. - [Introducing /research: Multi-step web research with citations for AI agents](https://usenaive.ai/blog/introducing-research): Three depths of web research — single-page extraction, multi-source web search, and full multi-step deep research with cited synthesis. Backed by Naïve's search providers and ready for agent loops that need real, verifiable facts. - [Naive vs Paperclip: Naive is Not Paperclip](https://usenaive.ai/blog/on-paperclip-and-open-source): Our approach to attribution, open source, and the infrastructure we're building. Naïve attributes Paperclip in §7.4 of the Terms of Service; the rest of the platform — primitives, runtime, templates — is original work built on top of an MIT-licensed foundation. - [Top 10 Platforms to Build Autonomous Companies in 2026](https://usenaive.ai/blog/top-10-platforms-autonomous-companies): A concise review of the 10 best platforms for building autonomous AI-run companies in 2026 — from no-code app builders (Lovable, Replit, Bolt) to developer agent frameworks (Paperclip, CrewAI) to full-stack agent infrastructure (Naïve). ## Optional - [Full content (llms-full.txt)](https://usenaive.ai/llms-full.txt) - [RSS feed](https://usenaive.ai/feed.xml) - [Sitemap](https://usenaive.ai/sitemap.xml)