Skip to content
AI & MCP · Typed actions

Twelve typed actions, run by the same code as your screens

Your assistant can create orders, collect payments, issue refunds, manage kitchen tickets, adjust stock, record expenses and more. Each action runs through the service the matching screen uses.

In short

describe_action lists the writes a business allows and perform_action runs one of them, such as create_order, collect_payment, issue_refund, manage_kot, adjust_stock, create_shipment or record_expense. Each runs through the same service as the matching screen in the app, with the same validation.

The problem it solves

An assistant that writes straight into the database skips the stock deductions, kitchen tickets and ledger entries your screens do. The two drift apart and the books stop adding up.

How it works

3 steps, start to finish

  1. 1

    Ask what is allowed

    describe_action lists the actions this business allows and their arguments.

  2. 2

    Try it first

    perform_action with dry_run describes the effect and changes nothing.

  3. 3

    Run it

    Consequential actions need the confirmation token from that dry run; ordinary writes run directly.

In detail

What typed actions does for you

Common queries

Questions people ask

  • Yes. Each action runs through the same service a merchant's screen uses, and names the capability and screen it corresponds to.
  • The consequential ones: create_order, collect_payment, issue_refund, manage_kot, adjust_stock and create_shipment.
  • Pass an idempotency_key: the same key with the same arguments replays the first result instead of writing again.

Typed actions · Free to start

Try typed actions on your own business

Set up in a couple of minutes. Your catalogue, orders and books stay yours to export.

  • Live in 2 minutes
  • Free to start
  • No credit card
The dashboard open on a laptop, a tablet and a phone