API for applications
Request structured JSON through a versioned contract.
API / CLI / MCP (PREVIEW)
Give your application
a connection to the world.
Rewalto's developer tools give applications, terminals and AI agents the same India data layer: a REST API at api.rewalto.com, a CLI for your terminal, and an MCP server (preview) at mcp.rewalto.com/mcp. Every account gets 1,000 free credits a month, and each read shows its credit cost before it runs.
Missing a data type?
This request is free. Do not include email addresses, phone numbers or other contact details. It does not start paid work or guarantee that the requested data can be supplied.
A promised reply requires sign-in and a verified account email. Anonymous requests have no response deadline.
HOW IT FITS YOUR DAY
Clarity at every step.
Useful data, with enough context to act on it.
CLI for your terminal
Discover and work with data from your existing workflow.
MCP (preview) for your agent
Connect an agent to data with the same source context.
FREE TOOLS / USEFUL DATA
A toolkit for the work between questions.
Search & page
Find a relevant source and read a page.
Site & extract
Explore a site and select the fields your workflow needs.
Browser & file
Work with interactive sources and documents.
Watch & task
Follow a change or define a bounded data task.
Tools are free. Credits pay for data delivered. Available capabilities follow the connected API contract.
Is there an API for India’s quick-commerce apps? Read the straight answer What the API covers: India ecommerce data by pin code and marketplaceTHE PAGE / THE RECORD
What people see.
What your workflow gets.
A product page holds useful details in a visual layout. Rewalto connects those details to named fields, with the source alongside them.
Fat ProfileToned
Shelf Life2 days
Biological SourceCow Milk
BLINKIT / DAIRY
Amul Taaza Toned Milk
A
AmulExplore all products
Product layout and unit prices follow the supplied 15 October 2026 screenshot. This is a dated source view; price and availability can vary by location and time.
{
"name": "Amul Taaza Toned Milk",
"brand": "Amul",
"quantity": "500 ml",
"source_page_id": "19512",
"source_url": "https://blinkit.com/prn/amul-taaza-toned-milk-500-ml/prid/19512",
"price": 30,
"currency": "INR",
"fat_profile": "Toned",
"shelf_life": "2 days",
"biological_source": "Cow Milk",
"reference_date": "2026-10-15",
"location": null
}A source-linked explanation of the fields, not a live retailer connection. Retailer and product marks belong to their respective owners.
SAME DATA / SAME PRINCIPLE
Pay for the data.
Keep the context.
Tool work is free. Review the rate or quote before a run. For recurring deliveries, review both the per-delivery and monthly cost first.
Explore pricingFROM QUESTION TO WORKFLOW
Make each result useful beyond the page.
Build a research assistant
Give your agent named fields with source URLs so it can explain where an answer came from.
Connect an internal workflow
Use structured records in analysis or an application. Preserve units, dates and unknown values through the integration.
Keep human approval explicit
Show the quote before execution. Handle an uncertain write outcome without silently starting the same job twice.
BEFORE YOU BEGIN
A little more context.
Make scope, evidence and cost part of the same decision.
What should I include in a brief?
Name the records, fields, sources or geography, and the period you need. For a watch, add the exact change condition and cadence. For a report, add the question and audience.
Is every source or field available?
Availability depends on source coverage and the requested scope. Confirm the available fields and collection period before running; a dataset page is not a guarantee of complete coverage.
When am I charged?
Review a published rate or an approved quote before a run. Tool work is free; credits pay for data delivered. Preparing a brief on this page does not charge credits.
How do I judge freshness?
Read the collection date alongside the original source date and location. A recent collection timestamp does not mean the underlying source was recently updated.
A REAL REQUEST / A DATED RESPONSE
What the API answered on 31 October 2026.
API v1, contract 0.141.0, release api-prod-v20261031.3. Last reviewed 31 October 2026. Any time, GET /v1/version names the release answering.
curl "https://api.rewalto.com/v1/data/samples?dataset=price_history"
No key, no credits: this free sample is open to anyone. It sent back 10 rows, each at least 7 days old. Here is one row, cut to 10 fields.
{
"retailer": "instamart",
"pincode": "411014",
"observedAt": "2026-10-24T15:34:14.000000Z",
"title": "Palmolive Naturals Black Orchid & Milk Liquid Hand Wash",
"brand": "Palmolive",
"packSizeRaw": "250 ml",
"priceMinor": 12800,
"mrpMinor": 16000,
"currency": "INR",
"inStock": true
}Read this as: Palmolive Naturals Black Orchid & Milk Liquid Hand Wash, 250 ml, listed at ₹128 against an MRP of ₹160 on Instamart at pin code 411014, read 24 October 2026 IST. Prices come in paise. The paid read of this data costs 1 credit per 10 readings. We saved this response whole on 31 October 2026, so the example stays fixed when the free sample changes.
PUT THE EVIDENCE TO WORK
Build a source-aware data integration
Discover the contract before writing a client
Start with the connected environment, authentication method and service version. Then choose the record type and inspect its documented fields and response shape. The downloadable OpenAPI snapshot describes a contract; check the environment integration note separately for deployment availability.
Preserve evidence in your application
Store source identifiers, location where supplied, observation dates and delivery receipts alongside the data you use. Present unavailable fields explicitly. If a chart or agent answer depends on a stale observation, show its date so the reader can judge whether it still supports the decision.
Keep agent actions bounded
An agent needs the same scoped credentials and cost review as an application. Begin with a read-only request, review the result and source context, and require approval before chargeable or recurring execution. Client installation details and MCP (preview) connection settings must come from the supplied integration note.
ONE DATA LAYER / MANY POSSIBILITIES