How to Sign Up for a CRM From Inside Your AI Agent (Agentic Signup)

Most software signup breaks the agentic loop: the agent is doing useful work, then has to stop and tell you to open a browser, fill a form, copy an API key, and paste it back. Agentic signup removes that seam — creating the account is itself a tool the agent calls. This is how it works on FavCRM, and how to build the same pattern.

The problem with normal signup

An AI agent connected to a tool can read and act — but only after someone provisions an account out of band. That "out of band" step is the whole friction. For an agentic CRM, it is also a contradiction: the pitch is "operate your business from chat," and the very first step makes you leave chat.

How agentic signup works

FavCRM exposes two tools that turn signup into a conversation:

register_organisation_request({
  email: "[email protected]",
  organisationName: "Your Studio",
  industry: "fitness",
  country: "HK"
})
→ { requestId }

register_organisation_verify({ requestId, code: "123456" })
→ { apiKey: "fav_mcp_…", companyId, loginUrl }

The flow, from the user's side:

1. The agent (Cursor, Claude, ChatGPT, v0) is connected to https://api.favcrm.io/mcp with no key yet.
2. You say: "Sign me up for FavCRM."
3. The agent calls register_organisation_request. An OTP lands in your inbox.
4. You paste the six-digit code back into the chat.
5. The agent calls register_organisation_verify and receives a scoped fav_mcp_* key — bound to one user and one workspace.

No portal, no form, no copy-pasting a key from a dashboard. The agent is operating a real workspace seconds later.

Why OTP, and why scoped

Two design choices matter. OTP-gated means email ownership is verified before a workspace exists — the request step is rate-limited, so the tool can't be used to spam accounts. Scoped means the key the agent receives is bound to one user and one workspace, and superadmin-class operations (raw SQL, plan management) are physically unreachable with it. The agent gets exactly the surface it needs, nothing more.

Building the pattern yourself

If you're designing an agent-callable backend, the shape generalises:

• A request tool that takes the minimum identity (email + a few fields), verifies ownership out of band (OTP, magic link), and is rate-limited.
• A verify tool that exchanges the proof for a scoped credential — never a god-key.
• Annotations on both so the agent treats them correctly (openWorldHint on the request, since it reaches an external mail service).

(See agentic registration in depth for the full backend walkthrough.)

Try it

Point your client at https://api.favcrm.io/mcp and ask it to sign you up, or create a workspace directly at favcrm.io/signup. Then connect FavCRM to your AI client and run your first command. The free tier covers 100 customers and 200 bookings a month.