Help in the shop
Ask while you work. Connect the tools you trust.
Stuck on a product, an order, or a setting? Ask inside the console. When you are ready, let the apps you already use see the same shop.
Open your shop
01
A hand in admin
Catalogue, orders, everyday questions. You stay in the console.
02
Tools that know your shop
Connect an app you trust. It works with the same permissions you would give a teammate.
03
A door for developers
The full reference lives on the API docs, when you want it.
The boring work, handled.
Credits apply when you use the assistant. Buy a pack after you sign in. Developers who want the raw reference can open the API docs.
For you and your AI
Hand your shop to your own AI.
Point Claude, Cursor, ChatGPT or any MCP client at your shop and the work becomes a sentence: add a product, move an order through fulfilment, publish the theme. One endpoint, one key, 87 tools.
Where the line stops
A key runs the shop, and four things stay yours: topping up the wallet, closing the shop, the CHIP and courier credentials, and handing the shop over. No key can reach them.
Prefer scripts?
A read API, version 1, that can never charge the wallet.
- GET /shop
- GET /products
- GET /orders
- GET /subscriptions
- GET /shipping
›Add the batik scarf at RM45, 20 in stock
tools/call mcp_products
{
"body": {
"name": "Batik scarf",
"price_minor": 4500,
"stock": 20
}
}Live at yourname.shopayla.co/product/batik-scarf
JSON-RPC 2.0 at protocol revision 2025-06-18, no session, no cookie.
Show the config
MCP client config
{
"mcpServers": {
"my-shop": {
"type": "http",
"url": "https://<your-shop>.shopayla.co/api/mcp",
"headers": { "Authorization": "Bearer ${SHOPAYLA_KEY}" }
}
}
}Field names differ a little between clients; the URL and the Authorization header are what carry across. Mint a key and set it as SHOPAYLA_KEY.
Your shop.
Your customers. Your pace.
Open a branded storefront, sell online or go live, welcome members when you are ready—and pay platform fees only when orders land.