Demo build. Every business shown is fictional, data is synthetic and partner integrations are simulated.What is real here

Conversion: sign-up

Eligibility-gated sign-up hands the customer to your flow only where they are permitted.

Sign-up starts a customer account with your business. When an offering is restricted (by age, residence, licence or any other rule in your policy pack), AGORA checks eligibility first and hands the customer to your sign-up flow only where they are permitted. An unresolved jurisdiction is a denial for restricted categories, never a guess.

Set it up

  1. Enable signup for the merchant.
  2. Choose the eligibility policy pack that applies, if any. Unrestricted sign-ups skip the check.
  3. Configure the hand-off target: your sign-up page, which the site SDK attributes.

What an agent does

Check eligibility with what the customer has declared, then start the sign-up with the eligibility reference. An ineligible customer gets a clear refusal with the reason, and no hand-off link is ever minted for them.

Applies to

product n/aservice n/aplan mustprogramme mustlisting n/amembership mustevent mayconsultation n/aother may

Endpoints in this build

POST/m/:slug/commerce/v1/signupsregistered

MCP tools

Besides the read tools every merchant server has, a business that enables Sign-up exposes:

  • search_catalogue: Search catalogue
  • get_product: Get product
  • get_offers: Get offers
  • search_services: Search services
  • get_credentials: Get credentials
  • get_fees: Get fees
  • check_eligibility: Check eligibility
  • start_signup: Start sign-up
  • start_application: Start application
  • verify_buyer: Verify buyer

Events

Delivered as webhooks:

conversion.signup.started conversion.signup.eligibility_checked conversion.signup.completed

Source: docs/portal/docs/conversions/signup.md + KIND_CONVERSION_MATRIX + registered routes + MCP tool registry