Get the data where your team already works.
Give your analyst a file, query the data through an API, or review a proposed website change. Choose the output your team needs, then check the delivery route’s availability, permissions and limits before connecting it. Planned connectors are labelled below; connecting one never grants permission to publish without review.
Included in the plans, not sold on its own
The file and the API come with the Rewalto Data plans, and a weekly file comes with Watch. The price of each plan is on the plans page, read from the published price book.
Where you switch it on
Each delivery route is listed with what it does and who receives it, so a person can see what leaves Rewalto and where it goes.
How it works
- STEP 1
Choose how it leaves
Pick a file, the API or a proposal, depending on who needs it: an analyst, a developer or the person who owns your website.
- STEP 2
Grant only what is named
A connector states what it reads and what it can never do before you grant anything. Credentials sit in the vault.
- STEP 3
End it whenever you like
Every connector says how to revoke it, above the fold. Disconnecting stops collection.
Choose the output your team needs
These are the delivery formats and their limits. Check the availability label on each named connector below before choosing a route.
CSV
A file for the people who need the data in their own model. Daily on Feed and Category, weekly on Watch.
API
The same record through a controlled query surface, without a manual download. Included with Feed and Category.
A proposal
A suggested website fix as a diff and a description. Your developer reviews it and Rewalto cannot publish it.
A pull request
The Next.js connector opens one pull request on the repository you name, with the finding it answers. It cannot merge.
A source behind every row
Whatever route the data takes, each row keeps the address of the retailer page it came from and the time it was read.
Revoke in one place
Each connector's page says how to end it, and what stops when you do.
Every connector, named
What each one reads, what it writes and how to leave. One built, no planned, and the planned ones are named as planned rather than left out.
Not seeing yours? A proposal is a diff and a description, so any system that accepts one can take it. Tell us what you use.
What you get
The record in the form each person on your team can use.
For your analysts
A CSV with an evidence reference on every row, ready for your own model.
For your developers
The API for the same record, and proposals and pull requests written to be reviewed like any other change.
For whoever signs off
A plain statement of what each connector can reach and what it can never do, before anything is granted.
Where we look
What the delivered record covers so far: the retailers, pin codes and AI engines behind every file and API response. The figures are read from the live record and never typed on this page.
- 6,701
- RETAILERS & D2C STORES WE COLLECT FROM
- 5,854
- PIN CODES
- 13,709
- DARK STORES
- 7,70,846
- PRODUCTS
- ChatGPT
- Claude
- Grok
- Perplexity
- Google AI
Google AI here is Gemini, reached through Google's official API. Google's AI Overviews and AI Mode have no official API, so they are not part of the check.
Read the rest of the trust surface
Questions before you start
How does the data reach my team?
As a file, through the API, or in the dashboard. Feed and Category include the daily CSV and the API, and Watch includes a weekly CSV and PDF. The plans page shows which plan includes what, and what it costs.
What is a proposal?
A suggested change to your website, written as a diff and a description that your developer reviews. Rewalto opens it, and only a person on your side can approve it. Rewalto cannot publish it.
Which connectors are live?
One is built and no more are planned and not yet live. Each connector has its own page that says what it can reach, what it never does and how to revoke it, and the planned ones are marked as planned.
Is there a webhook, a scheduled email or a BI connector?
Not yet. A file and the API are the routes that exist today. If your team needs one of the others, tell us what you use and we will say plainly whether it is planned.
Where do my keys and credentials live?
In an encrypted vault, and they are substituted at the point of use rather than copied into application code. The security page covers this in full.
Questions before you connect something?
Ask us directly, and you’ll hear back within one working day.