Content and API Licence

1.Why this page exists

For a while our terms forbade reproduction while the site simultaneously published a public API, an MCP server, an OpenAPI document, `llms.txt`, and machine-readable versions of every page. That was a contradiction, and the honest fix is to say what we actually intend.

We publish machine-readable data on purpose. We want agents, researchers, comparison tools, and spreadsheet people to use this data. You do not need to ask permission, and you do not need to scrape us uninvited. This page is the permission layer.

2.What we publish for machine consumption

• A public REST API. Tool listings, individual tool records, and category records, plus a price index and a dedicated price file. The full specification is a published OpenAPI document.
• A Model Context Protocol server, described on our Developers page, so an AI agent can query our review data as a structured tool rather than scraping prose.
• llms.txt and llms-full.txt, which describe the site and its content for language models that read documentation first.
• Markdown instead of HTML. Send an `Accept: text/markdown` request header and any page is served as clean Markdown rather than a hydrated app, built for agents and crawlers that want text.
• A human-readable contact address. Every problem with the data, including something factually wrong, is worth an email.

3.What you may do

The following are permitted without asking, without a fee, and without credit beyond the attribution below.

• Read the site and share links to it, including publicly and commercially.
• Call the public endpoints and build your own tools, dashboards, agents, or workflows on top of the results.
• Quote published scores, ratings, and pricing in your own writing, with attribution and a link back.
• Redistribute the factual dataset inside your own product, article, comparison, spreadsheet, or analysis. See [the next section](#the-data) for exactly what counts as factual data.
• Quote short excerpts of our editorial writing with attribution and a link, without asking permission first.
• Use a machine-readable client, whether that is an AI agent, a script, a research tool, or a crawler, to read the site within the published rate limits.
• Use our content to inform your own purchasing decisions, obviously, since that is what it is for.

4.The factual dataset, and what is separate from it

Two different things live on this site, and they are licensed differently.

The distinction is between a fact about a vendor and our opinion about that vendor. A price is a fact. A judgement that the price is not worth it is our editorial work, and it stays ours.

Reusing the factual dataset is how a legitimate tool stays legitimate. Republishing our argument is how a copy becomes a pass-off, and it undermines the thing that makes these pages worth reading.

5.What you may not do

• Present our editorial writing as your own, or strip the byline or attribution from it.
• Remove attribution from the factual dataset in a way that suggests the data came from you.
• Use the API, the data, or the markdown endpoints to build a competing review or comparison site. This is the one restriction we hold firmly, because a mirror of our verdicts attributed to someone else is a misrepresentation of our testing.
• Train or fine-tune a machine-learning model on our editorial content. The factual dataset is licensed for that purpose under a separate, written permission, which you would need to request.
• Exceed the published rate limits, or attempt to circumvent them in any way. Doing so is a breach of our Terms of Service, not merely a technical preference.
• Republish our content in bulk as thin, machine-generated pages. Taking 200 reviews and posting them with a new domain is not redistribution, it is appropriation.

6.What attribution looks like

Attribution is required whenever you redistribute the factual dataset or quote our editorial writing. There is no fee and no permission form.

• A line reading *Data from GoPickStack* with a link to the page you took it from is sufficient.
• For a quotation, a link back to the specific review or comparison is sufficient.
• Do not imply the data was collected by you, and do not imply we endorse your product by association. We are named as a source, not as a partner, unless we have agreed otherwise in writing.

7.Vendor names, logos, and trademarks

Product names, company names, and logos belong to their respective owners. Nothing in this licence grants you any trademark rights.

Referring to a vendor by name in order to say something true about it is nominative use. It is not a claim of affiliation, endorsement, or partnership, and it does not require permission. Claiming to be an official partner of a vendor we have written about does, and we will ask you to remove it.

8.Rate limits

The public API is rate limited to a default of 120 requests per 60 seconds. We publish the limit in the standard IETF RateLimit header format, so a well-behaved client can read its own budget rather than guessing: `RateLimit-Limit`, `RateLimit-Remaining`, `RateLimit-Reset`, and `RateLimit-Policy`, with `X-RateLimit-` prefixed versions as backwards-compatible aliases.

Back off when `RateLimit-Remaining` reaches zero rather than retrying immediately, and respect the `Retry-After` header when you receive one. If you need a higher budget for a legitimate workload, ask. We would rather raise a limit than block real work.

9.Availability

Everything on this page is provided as is and as available. There is no uptime guarantee, and there is no service level agreement. If the API is down, that is a bug rather than a breach, and we will fix it as soon as we know about it.

The endpoints and the response shape may change as we add tools and fix data problems. We will note breaking changes in the changelog before shipping them, but we are a one-person operation and we will not always get it right in advance. Build defensively.

10.How current the data is

Pricing and features on this site are re-verified on a 15-day cycle. Every tool record carries the date it was last verified, and that date is part of the data we publish so you can decide how much weight to give a figure.

We publish a changelog recording what changed and when. If you cache our data, respect the verification date rather than serving a stale price as though it were current, because a wrong price is worse than no price.

11.Reporting a problem

If the data is wrong, the endpoint errors, or you think this licence is being applied unfairly, email Muhammad Shadab Shams at hi@gopickstack.com with the endpoint, the request, and what you expected. We fix data errors on report, including from people who are not our customers and never will be.

12.Governing law

This licence is governed by the laws of England and Wales, and it should be read together with our Terms of Service, which govern your use of the site itself.