Skip to main content
These guides help you move agent workloads from standalone vendor APIs to Naive primitives. Each guide maps the vendor’s core path, shows a minimal swap, and calls out what does not map yet.
Third-party product names and logos in these guides are trademarks of their respective owners, used here for identification and comparison only. No endorsement, partnership, or affiliation is implied.

​
Naive → Naive

When Naive itself supersedes one of its own surfaces, the guide lives here. Same five sections; the “vendor” is a previous version of Naive. Nothing on either path is removed — every route, CLI command and DSL symbol named in the From column keeps answering. The entrypoint guide is separate from the orchestration one because they move different things: renaming the call changes when a config refuses, not where anything runs; the orchestration guide moves the workload itself. The remaining two differ by blast radius: memory is on by default; brain is opt-in, and a gated call with no kit entry is a refusal. Merging them would bury the one fact that breaks a real migration on day one.

​
Third-party → Naive

​
Shared migration pattern

Every guide follows the same shape:
  1. Concept map — vendor object ↔ Naive primitive
  2. Before / after — smallest working code swap
  3. Minimal viable migration — ship without rebuilding everything
  4. Consolidation gains — one tenant user across cards, email, vault, connections, and more
  5. What does not map yet — honest gaps before you commit
Install the Node SDK once for all guides:
Set NAIVE_API_KEY from the dashboard. Examples use @usenaive-sdk/server against https://api.usenaive.ai/v1 unless noted.

​
Before you start

  • Pick the guide that matches one vendor you are replacing — do not assume feature parity across primitives.
  • Read each guide’s What does not map yet section; several vendors have capabilities Naive does not mirror today.
  • Confirm webhook event types with GET /v1/webhooks/event-types before depending on inbound events.
  • Scope migrations to what Naive actually ships — e.g. Persona and Doola guides target founder / formation flows, not arbitrary end-user KYC or every entity type Doola supports.