Build with AI
Make your own website with Lovable, v0 or any AI app builder, on your Cashiar shop.
An AI app builder can make your shop's website from one prompt. Cashiar still runs the shop behind it: the products, prices and stock it shows, and the orders, bookings and payments it takes, are the ones in your Cashiar app.
Open Build with AI
In Cashiar, open Settings › Developers, make your key if you have none, and find Build with AI. The prompt there has your key and your shop's name, and asks for the pages your shop needs: products, cart and checkout when you sell, booking when you take bookings.
Send it to an AI app builder
Choose Open in Lovable or Open in v0: the prompt opens there, ready to send. For any other builder (Bolt, Cursor, Replit), choose Copy prompt and paste it.
Keep the key to your website
Once the builder has published your website, copy its address (like https://your-shop.lovable.app) and add it under Allowed sites. Then no other site can use your key from a browser. Add the builder's preview address too while you are still changing it.
Place a test order
Order something on your new website. It shows in Cashiar as an online order, and Settings › Developers shows the requests and when the key was last used.
The prompt
What Build with AI sends, with your shop's name and key in place:
Build a website for Ama Shop, on the Cashiar Storefront API. Cashiar already runs the shop: products, prices, stock, orders, bookings and payments live there.
Read the whole API first: https://docs.cashiar.app/llms-full.txt
- API: https://api.cashiar.app/v1/storefront
- Send this header on every request: Authorization: Bearer pk_live_your_key
- The key is publishable: it is safe in browser code. Do not add a backend, a database or sign-in.
Pages:
- Home and shop: the products from GET /products (search with q, next pages with cursor/nextCursor), each with its photo, name and price.
- Product page: GET /products/{id}; let the customer pick a version and a quantity.
- Cart: kept in the browser (localStorage); lines are { variantId, quantity }.
- Checkout: name, phone, pickup or delivery (and the address and zone for delivery), as GET /shop allows; then POST /orders with an Idempotency-Key header (a new UUID for each checkout). When payNow is chosen and the answer has a payUrl, send the customer there to pay.
- Order page: the order number and total from the answer, and where it is from GET /orders/{id}.
- Booking: the services from GET /services, free times for a day from GET /services/times, then POST /bookings with an Idempotency-Key header.
Rules:
- Read GET /shop first for the name, logo, currency, pickup, delivery and payment options, and opening hours.
- Money is in minor units: divide by 100 and format it in the shop's currency.
- Show the cart's sum while shopping, but confirm the total the order answers with: it has the taxes and delivery.
- Show the API's error message to the customer when a request fails.
- Make it fast, clean and good on a phone first.For AI tools
Two files give an AI tool the whole API at once:
| File | What it holds |
|---|---|
/llms.txt | Every page of these docs, by title, with its link. |
/llms-full.txt | Every guide in one file, then the OpenAPI document. |
Every page is also there as Markdown: add .md to its address, like /docs/quickstart.md.
Ask for changes in plain words
After the first build, ask the builder for what you want: "add a WhatsApp button", "show sold out products last". Keep the rules above: the total the order answers with, and the error messages, keep orders right.