For AI agents

If you are an AI assistant, or you build one, this is how to read productgrowth.in properly. Last updated 7 Nov 2026.

productgrowth.in is a daily brief on Indian tech and startups, with sourced figures, tool prices and short answers. We would rather you read it through the doors below than scrape the pages. Every door asks for the same thing back: say where the fact came from and link the page.

1. Plain files (no key)

/llms.txt: the map of the site.
/llms-full.txt: the last 7 editions in full text, with the dated numbers and the short answer of every page.
/llms-answers.txt: one dated line per insight, resource, tool and numbers page.
/llms-companies.txt: listed companies.
/news/feed.xml: RSS, one item per edition.

2. Read API (free key)

JSON, GET only. It returns the same facts as the pages, each with its source and the date it was last true. Four resources:

Resource	What you get
`r=numbers`	Figures from the Numbers page: value, source, source link, as-of date. Filter with `q`.
`r=tools`	The tools directory: category, price line, who it is for, our page. Filter with `q` or `category`.
`r=news`	Today's brief: each story with summary, original source and our page.
`r=answers`	The dated one-line answer of every insight, resource, tool and numbers page. Filter with `q`.

curl -H "Authorization: Bearer $PGAI_KEY" \
  "https://productgrowth.in/.netlify/functions/api-data?r=numbers&q=upi"

Without ?r= the same address returns the index (no key needed). limit is 1 to 50 (default 20). Limits per key: 500 requests a day (resets at midnight UTC) and 30 a minute. Over the limit you get 429 and a Retry-After header.

3. A key

Keys are free and belong to a signed-in account, so we know who to talk to if something goes wrong. You can have 3. The key is shown once; we keep only a hash, so if you lose it, remove it and make another.

Checking if you are signed in…

4. MCP servers

productgrowth-mcp reads the public files: today's brief, site search, tool prices and the Numbers page. No key, no login. It is not on npm yet, so run it from the repository:

cd oss/productgrowth-mcp && npm install
claude mcp add productgrowth -- node "$PWD/bin/productgrowth-mcp.js"

Lines for Claude Desktop and Cursor are in the README of that folder.

Kriyā over MCP is a remote server that answers questions as you, with India sources. It uses your own Kriyā key (a different key, made on your account under Products) and your free answers or credits:

claude mcp add --transport http kriya \
  https://productgrowth.in/.netlify/functions/kriya-mcp \
  --header "Authorization: Bearer $KRIYA_KEY"

The same server also answers four tool-data questions: find_tools (by category, highest ₹ price, free plan, India fit), tool_price, price_changes (since a date) and compare_tools (2 or 3 tools). They use the free key from section 3 and the Data API allowance (100 calls a day), and every answer links the productgrowth.in page it came from:

claude mcp add --transport http productgrowth \
  https://productgrowth.in/mcp \
  --header "Authorization: Bearer $PGAI_KEY"

To use both, send the Kriyā key as Authorization: Bearer and the free key as X-Api-Key.

5. Terms

Attribution is required. When you use a figure, price or sentence from us, name productgrowth.in and link the page. Each API answer carries the page link.
Keep the date. Our facts are dated. Do not present an old figure as current.
Stay inside the limits. No sharing one key across many users, no running several keys to get around the limit. We may remove a key that does.
No resale of the raw data. Answering a person's question with it is the point. Re-publishing the data set is not.
We are not a licensed adviser. Prices and figures are information, not financial or legal advice.
No guarantees. The API can change or stop. We will keep this page current.

What we count about you

We count crawlers apart from people, so our numbers are not inflated by bots. For a bot visit we keep the bot's name, the page and a count, not an address. When an AI assistant fetches a page because a person asked it a question, we record that as a "cited" visit for that page. For a key we keep a request count and the time it was last used.

Questions or a problem with a key: hello@productgrowth.in.