Mesos Lab

Mesos Agent

Turn your app into an AI-powered service channel.

Embed an AI agent that understands customer intent and coordinates discovery, booking, ordering and approved transactions through MCP and API connections.

Proposed product. Available services depend on connected providers.

PARTNER APPAssistant
Find a table for four near the office this Friday at 7 pm.
Two tables near the office on Fri 2 Oct:
Juniper Room · 19:004 min walk
Olive & Ash · 19:157 min walk

Review before confirming

Venue
Juniper Room
Date & time
Fri 2 Oct, 19:00
Party size
4 guests
Terms
Table held 15 min. Free cancellation until Thu 18:00.
Deposit
40,000 ₮
Illustrative embedded experience

Interactive simulation · Fictional providers

Plan. Draft. Commit. Execute.

A proposed action is not a result. Only the provider’s confirmation, with its reference, counts as done.

  1. 01

    Plan

    Understand the request, resolve missing details and discover supported services.

  2. 02

    Draft

    Prepare the selected action, price and terms.

  3. 03

    Commit

    Capture approval for the specific action.

  4. 04

    Execute

    Call the provider, track status and return its confirmed outcome.

Journey

Provider outcome to simulate
  1. 01Plan
  2. 02Draft
  3. 03Commit
  4. 04Execute

Connection activity

Fictional tools

No calls yet.

PARTNER APPMesos Agent
Find a table for four near the office this Friday at 7 pm.
Which office — Central Tower? Any cuisine preference?
Simulation · fictional providers · no real bookings or payments

For banks, wallets and digital platforms

Agent for banks and fintechs.

01

Useful services in your app

Introduce everyday services customers can complete without leaving the existing app.

02

Your brand, your relationship

The partner keeps its brand and customer relationship; Mesos works behind it.

03

Connected journeys

Connect discovery, approval and supported payment steps in one flow.

04

Agreed economics

Enable agreed implementation, usage, referral or transaction economics where provider arrangements permit.

The partner provides the customer channel. Mesos coordinates the service workflow. Connected providers fulfil the approved request.

MCP and APIs

Connect intelligence to useful services.

MCP provides a structured way for AI agents to access supported tools and services. APIs connect the underlying provider systems.

Proposed architecture

  1. 01Partner appYour brand and customers
  2. 02Mesos AgentUnderstands intent, plans and drafts
  3. 03Mesos FabricPermissions, workflow, records
  4. 04MCP tools · API connectorsStructured tools over provider APIs
  5. 05ProvidersCommerce merchants + external providers
PermissionsInput validationCustomer approvalDuplicate preventionActivity records

These controls are provided by Mesos Fabric and the partner set-up. MCP itself does not process payments, grant permission or guarantee security.

Example tools

Illustrative interfaces
  • search_services

    Find supported services matching the request

  • check_availability

    Confirm times, stock or seats

  • prepare_order

    Build a priced draft order

  • create_booking

    Submit an approved booking once

  • get_execution_status

    Read the result of an existing request

Explore Mesos Fabric

Commerce + Agent

Commerce makes services discoverable. Agent brings demand back.

Merchant side · Juniper Room

CatalogueDinner tables · 2, 4, 6 seats
AvailabilityFri 2 Oct · 19:00 · 4-seat
Price & termsDeposit 40,000 ₮ · cancel by Thu 18:00
Supported actionReserve table

New in workspace

Reservation JR-20417 · 4 guests · 19:00 · via Partner app

Customer side · Partner app

  1. 01Request: table for four, Friday 7 pm
  2. 02Proposed booking at Juniper Room
  3. 03Customer approves terms and deposit
  4. 04Provider confirms · JR-20417

Mesos Commerce can provide the operational context agents need. Supported external providers can also connect through the shared integration layer. Merchant data is shared only as the merchant permits.

Explore Mesos Commerce

Intended product behaviour

The customer stays in control.

Review before commitment

Show the specific service, total price, fees, and material terms before approval.

Bounded permissions

Actions operate within the permissions and limits granted.

Visible execution status

Distinguish proposed, approved, pending, confirmed, and failed states.

Traceable outcomes

Retain relevant action records and provider references for support and reconciliation.

Cancellations and refunds follow each provider's terms and supported workflows; completed actions are not automatically reversible.

Action record · JR-20417 · illustrative

  1. Proposed18:02
  2. Approved18:03
  3. Pending18:03
  4. Confirmed18:04
  5. Failed — shown if the provider declines

Practical questions

What partners ask first.

Mesos Agent

Bring useful action into your customer experience.

Explore how Mesos connects customer requests, merchant services and approved execution.

Explore Mesos Fabric