Install the gateway on your store
You don’t need to write code — hand your developer the Install page and the docs, and know what to expect once it’s live.
Installing the gateway is a developer task, but a small one: on a typical Next.js store it is one package and two short files. If you’re not the technical person, send whoever deploys your site to the developer docs and to your Console’s Install page — it contains copy-paste instructions pre-filled with your store ID.
- Developer quickstart: rebilder.com/docs/quickstart
- Your instructions with real credentials: Console → Install
If your store runs on Shopify
Shopify stores integrate through a Shopify App Proxy — no theme edits and no Liquid changes. Shopify forwards a dedicated path on your own domain (/apps/rebilder/…) to the gateway, which answers agents there. The Install page lists the exact Shopify Partners settings, and requests are cryptographically signed so content is never served on an unverified proxy request.
The two halves of an install
- Serving: the gateway answers agent requests with markdown. This works on its own, with no API key involved.
- Reporting: the gateway forwards a small event about each request to Rebilder (authenticated with your store’s API key), which is what fills the Agent visits log and Overview numbers.
Ask your developer to wire both — a store can serve agents perfectly while the Console stays empty because event reporting wasn’t connected.
What to expect when it’s live
- Nothing changes for your shoppers — humans get the exact same site as before.
- Google and other search engines keep getting your normal HTML pages. Always.
- AI agents that ask for markdown get a compact text version of the same page — same prices, same availability, same policies.
- Visits start appearing in Console → Agent visits as agents come by (agent traffic is a small share of total traffic, so give it time).