Integration playbooks

Three integration patterns, all production-ready. Pick the one that matches how you want to drive (or be driven by) 10ex.

Who this fits: developers, sales engineers, and AI platform teams shipping agents that need to send email, generate content, or work the CRM. You’ll need a 10ex API key and basic familiarity with MCP or REST.

1. Driving 10ex from Claude or Cursor (MCP)

Configure the 10ex MCP server in Claude Desktop or Cursor (see MCP setup) and the agent can do everything a human can. Sign up, connect Gmail, ingest brand knowledge, manage leads, launch campaigns. All from a chat prompt.

This is the fastest way to dogfood the platform. Most developers go from zero to a launched sequence in under 10 minutes.

2. Driving 10ex from a CrewAI workflow

Your CrewAI app calls the 10ex MCP server (or REST API directly) as a tool. Use cases include:

• A research crew finds enterprise prospects, then calls bulk_import_leads and launch_email_sequence.
• A content crew generates a brief, then calls generate_blog and publish_blog.
• A sales-ops crew checks get_email_sequence_status and triggers follow-up flows.

# inside your CrewAI tool definition
from mcp import ClientSession  # any MCP client
session = ClientSession(transport="streamable-http", url="https://api.10ex.ai/mcp", headers={"Authorization": f"Bearer {tnx_key}"})
await session.call_tool("launch_email_sequence", {...})

3. Extending 10ex with your own CrewAI crew

The 10ex agent runtime is CrewAI under the hood, so you can register your own crew as a 10ex agent and have it run on the platform’s execution layer (workers, observability via Langfuse, billing). See Concepts → Agents architecture for the integration contract.

How to pick the right pattern

• Want a human in the chat seat with full platform access? Use pattern 1.
• Want your own AI app to call 10ex as a tool? Use pattern 2.
• Want to ship your own agent on 10ex’s execution layer? Use pattern 3.

Common pitfalls

• Hardcoding the auth header. Rotate keys via env vars; never commit them.
• Calling launch_email_sequence without approval_required: true in production. Approval gating is the spend safety net; bypass it only on lanes you trust.
• Skipping the brand-knowledge ingest step. Without it, generated copy ships in a generic voice.

Common questions

Can I use the 10ex MCP server from Claude Code? Yes. The same MCP setup that works for Claude Desktop works for Claude Code and Cursor. See MCP setup.

Is the REST API a separate surface from MCP? No. Every MCP tool is backed by the same REST endpoint. Pick whichever is more ergonomic for your stack.

Can my custom crew read the workspace’s brand knowledge? Yes. Registered crews receive the same brand context any first-party agent does. See Agents architecture.