Skip to content

Connect your product

Let an assistant help a customer reach a first useful result with your product, create an account and continue with approved access.

Contact your Rose account manager. We'll manage the integration with your team. There is no Rose backoffice setting to configure for this step.

Choose the customer experience

Start with the action that best demonstrates your product's value. Tell Rose:

  • What an assistant should be able to try.
  • Which trial limits and product permissions you want to apply.
  • How customers currently sign up and sign in.
  • What should happen when a customer already has an account.
  • Which plans, prices and sign-up links you want assistants to see.

You keep control of customer relationships, product access and commercial terms.

Handover

Give customers a way to take over the trial their AI assistant started. They can discover what your product does before signing up, then claim the same account when they're ready to continue. The work and usage accumulated during the trial stay with the account.

  1. Try. The assistant starts a limited trial and helps the customer get a first useful result from your product.
  2. Claim. When the customer wants to continue, they open the claim link, sign in and approve access.
  3. Continue. The trial becomes their account. The assistant continues on that same account with the access the customer approved.

Handover works for products used through an API and for products used as an MCP server: the assistant uses your MCP with a trial token and keeps the account after the claim.

Bring Handover to your product

Together, we'll choose the trial experience, agree its limits and connect the account handover to your product. Your developers will:

  1. Install the vendor SDK and serve its agent-access endpoints, connected to your accounts and API keys.
  2. Create your own signing key and add Rose's public trust settings, listed in Connect Handover.
  3. Send Rose your public origin and endpoint URLs, then test a claim with us before launch.

Your developers can hand this to their coding agent (Claude Code, Codex, Cursor) in your product's repository:

Read https://userose.ai/rose-for-agents/handover-prompt.txt and add Rose Handover to our product.

Common questions

Does the customer need to sign up before trying the product? No. The assistant can start a limited trial first. The customer signs in when they decide to claim it.

Does claiming start a new trial? No. The customer claims the existing account, keeping its accumulated usage. They and their assistant continue from the result already reached.

What if the customer already has an account? We'll agree how Handover fits your existing accounts and login experience during the integration.

Can the customer later sign in to our product directly? Yes. The claim verified their email; your sign-in opens the claimed account for that verified email. See Let the customer sign in to the claimed account for where each authentication provider (Clerk, Auth0, Supabase…) gives your server that email.

Can every new account require the customer's approval? Yes, on request. By default, an assistant whose user is signed in to Rose creates the account directly. With approval required, signing up starts a Handover trial instead: the account becomes the customer's only once they claim it, so no account is left without an approved owner. Ask your Rose account manager to turn it on.

Can the assistant take over without the customer's approval? No. The customer explicitly approves the claim and the assistant's access. Your service controls which product features that access includes.

Use the vendor SDK

The Rose vendor SDK is a server-side JavaScript and TypeScript package. It verifies and routes Rose requests to your existing trial, account, checkout and access services, and provides identity verification for Handover. Your product keeps its account storage, permissions, usage limits and commercial terms.

Rose provides the configuration as part of your integration. Your developers can follow Install and set up the vendor SDK for the installation command, examples and setup checklist.

Review the experience together

Before making it available to customers, check the journey with Rose:

  1. The assistant can find your product and understand its offers.
  2. The trial produces a useful result within the limits you selected.
  3. The customer understands and approves the account claim and assistant access.
  4. Claiming keeps the same account and accumulated trial usage.
  5. Your existing customers have a clear path through the agreed account experience.

Return to the Rose for Agents overview.