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.

Guides

GuideFromNaive primitiveWhen to use
ComposioComposio tool auth/connectionsOAuth tool connect + execute
Stripe IssuingStripe Issuing/cardsVirtual card issue, fund, spend
AgentMailAgentMailemailAgent inbox send/receive
PortkeyPortkey gateway/llmOpenAI-compatible multi-model routing
TwilioTwilio SMSphoneUS number provision + SMS
PersonaPersona inquiriesverificationFounder KYC before formation
DoolaDoola Formation APIformationUS LLC incorporation
BrowserbaseBrowserbase + StagehandbrowserCloud browser + signup/login
E2BE2B sandboxescomputeIsolated code execution
GoDaddyGoDaddy Domains APIdomainsSearch, buy, DNS
AlpacaAlpaca Trading APItradingStocks, options, crypto orders
TavilyTavily search/extractsearchWeb research, URL extract, multi-source answers
Amazon SQSAmazon SQSqueueDurable per-tenant work queues
ElevenLabsElevenLabs TTS/voice clonevoiceVoice clone + text-to-speech
LagoLago metering/billingcustomer-billingPlans, subscriptions, usage quotas
AyrshareAyrshare social APIsocialMulti-network posting + analytics
Appetize.ioAppetize.io cloud devicesmobileHosted Android/iOS device streaming
DopplerDoppler secretsvaultPer-user encrypted secrets

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:
npm install @usenaive-sdk/server
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.