Start with your existing product feed
Connect a Google Merchant XML feed, CSV or JSON Lines export. Siroua groups variants into products and keeps each variant’s SKU, options, price and availability. We import updates on a schedule, so the catalog is only as fresh as the feed we’ve received.
You keep your ecommerce platform. When an agent sends a shopper to your store, it uses your original product URL. Siroua’s product pages also point to that URL with a canonical link.
Give agents useful answers, not another page to scrape
A request such as ‘waterproof running shoes under 150 EUR size 44’ combines meaning with requirements. Siroua extracts price, size and stock phrases in English and German before retrieval, then applies those constraints to both semantic and keyword search.
Search returns compact product cards, around 80 tokens in the documented example. The agent reads full details only for products worth considering. Attributes such as material and fit can be filtered explicitly when recorded; a missing attribute is unknown, not proof that a product has it.
{
"query": "waterproof running shoes under 150 EUR size 44",
"filters": { "in_stock": true },
"limit": 10
}Connect through MCP, ACP, REST or the web
MCP clients can use tools for product search, detail, checkout and order lookup. ACP clients can use checkout sessions. Other integrations can call the REST API, while browsing agents can read lightweight product pages with Schema.org markup.
Protocol support makes a catalog usable by a compatible, authorized client. It does not automatically enroll a brand in an assistant’s shopping program or guarantee recommendations in ChatGPT, Claude or Gemini. Each platform controls its own discovery, eligibility and user experience.
Get paid through your own account
When API checkout is enabled, Siroua validates the cart and computes the total before forwarding payment to the brand’s own Stripe account. Idempotency prevents a retried checkout from creating a second charge for the same key.
If API checkout is not enabled, product details direct the agent to your own product page. That website visit is a handoff, not evidence of a sale. Confirmed API payments and website traffic should be measured separately.
Is your catalog ready?
We’re setting up a few brands at a time. You’ll need a feed with stable variant IDs, accurate prices and stock, and working product URLs. It also helps to know which agent or client you want to connect.
- Bring a sample feed and identify the fields used for variant grouping and options.
- Choose website handoff or API checkout; payment setup is a separate step from importing products.
- Test real shopper questions, including unavailable sizes, over-budget items and missing attributes.
- Agree a feed refresh schedule and check how price changes behave before a purchase.
Let’s look at your catalog
Join the waitlist with your store URL. We’ll talk through your feed and how you want agents to use it.
Join the waitlist