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

Conversion: application

Agents start an application with the documents your programme requires.

An application is a request for admission to something you offer selectively: a programme, a membership, a listing or any offering where you decide who takes part. The agent collects what the applicant declares and references to the documents your programme requires; you decide the outcome in your own system.

Set it up

  1. Enable application for the merchant.
  2. Model the programme as an offering and list the documents it requires.
  3. Connect the destination for applications (CRM or admissions system); the demo uses a stand-in.

What an agent does

Start the application with the applicant's declared context and document references. The outcome arrives later as conversion.application.outcome, which the agent can relay.

Applies to

product n/aservice n/aplan n/aprogramme mustlisting mustmembership mayevent n/aconsultation n/aother may

Endpoints in this build

POST/m/:slug/commerce/v1/applicationsregistered

MCP tools

Besides the read tools every merchant server has, a business that enables Application exposes:

  • 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.application.submitted conversion.application.outcome

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