Integration1 min read

Naïve 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.

Read the docs →

Integration
TL;DR
  • Naïve supports Doola for Agent Incorporation `/formation` files US LLCs through Doola after founder KYC and hosted checkout
  • Naïve is the orchestration layer; Doola handles the licensed formation filing the resulting Company is a first-class runtime object
  • One governed identity the same profile that incorporates can own cards, domains, and email without a second vendor account
  • Per-tenant isolation with naive.forUser(), Account Kits, approvals on binding steps, and a unified audit trail
  • Entity type in published docs centers on LLC see the formation guide for supported states and gap cases

An agent that can research markets and draft contracts still cannot operate as a business until it has a legal entity — something that can own a domain, sign agreements, and hold financial relationships. Naïve is the autonomous company infrastructure that gives agents real-world capabilities, and Naïve supports Doola for Agent Incorporation through /formation: founder KYC, hosted payment, and US LLC filing orchestrated on one governed profile.

How /formation works with Doola

Naïve is an orchestration layer. State filings run through a licensed formation partner — Doola — while Naïve owns the agent-facing flow:

  1. Verify — founders complete hosted KYC via /verification until ready_for_formation is true.
  2. Submitnaive formation submit returns a checkout_url for the published formation fee (see the formation guide for current pricing).
  3. Execute — after payment, naive formation execute dispatches the filing; verified PII stays in Naïve's encrypted identity vault until filing time.
  4. Compose — attach /cards, /domains, /email, and the rest of the stack to the Company object that comes back.

The entity your agent forms is a first-class runtime object, not a document trapped in a third-party inbox.

Why this matters for agent builders

  • No second vendor account — incorporation lives on the same Naïve workspace as spend, comms, and runtime.
  • Per-tenant isolation — scope every call with naive.forUser() so one customer's formation never leaks to another.
  • Governance by default — formation submit and execute can freeze for human approval at execution time.
  • Honest scope — LLC-centric today; read the Doola migration guide if you are comparing direct Doola API features.

Where to go next

Frequently Asked Questions
What does it mean that Naïve supports Doola for agent incorporation?+
Naïve's `/formation` primitive orchestrates US LLC incorporation end-to-end: founder KYC, a hosted checkout for the published formation fee, then filing through Doola. Your agent drives the flow on one governed identity — the Company that results is a runtime object your other primitives attach to, not a PDF in a separate dashboard.
Does my agent need its own Doola account?+
No. Naïve holds the formation integration and exposes it as `/formation`. You call Naïve's API or CLI — submit, pay via checkout, execute — and Naïve coordinates with Doola server-side. Your agents never manage a standalone Doola API key for this path.
How does incorporation connect to the rest of the agent profile?+
After formation completes, the Company is the substrate for `/cards`, `/domains`, `/email`, and other primitives on the same tenant user. That is the **Company → Employee → Primitive** model: one identity, one audit trail, revocable in one place.
What does not map through `/formation` today?+
Published docs and the Doola migration guide list real gaps — C-corp and DAO LLC types, ongoing compliance tooling, and cap-table workflows are out of scope for `/formation` today. Read the migration guide's gap table before you promise parity to customers.
NT
Naïve Team

Building the autonomous company infrastructure.

Keep reading