trustpilot-api
Skill3 starsChanged 3 months agoMIT-0View on GitHub
Trustpilot data toolkit via ScraperSocial — company review listings as clean JSON.
In this repository33 other files it gives its agents.
- amazon-apiSkill
- app-store-apiSkill
- bluesky-apiSkill
- facebook-apiSkill
- github-apiSkill
- google-apiSkill
- google-finance-apiSkill
- google-maps-apiSkill
- google-news-apiSkill
- google-play-apiSkill
- google-shopping-apiSkill
- google-trends-apiSkill
- hacker-news-apiSkill
- instagram-apiSkill
- kwai-apiSkill
- linkedin-apiSkill
- linkme-apiSkill
- linktree-apiSkill
- naver-apiSkill
- pinterest-apiSkill
- polymarket-apiSkill
- reddit-apiSkill
- snapchat-apiSkill
- social-media-apiSkill
- spotify-apiSkill
- threads-apiSkill
- tiktok-apiSkill
- tiktok-shop-apiSkill
- tripadvisor-apiSkill
- truth-social-apiSkill
- twitch-apiSkill
- twitter-apiSkill
- youtube-apiSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 45
You need to reply to reviews or flag them: Read-only; Trustpilot's Business API covers that.
- Very specific: line 68
Every script also accepts --limit, --cursor, --fields, --format and --fresh.
- Distinctive: line 76
Every response uses the same envelope:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Trustpilot API skill
Read public Trustpilot reviews as clean JSON. This Trustpilot API skill has a single endpoint: give it a company URL or handle and it returns their reviews at 1 credit each — the cheapest review source in this repo, and the standard reference for company reputation in Europe.
This skill wraps 1 live Trustpilot endpoint from the ScraperSocial API. Public data only, returned as clean JSON.
When to use this skill
- You are assessing a company's reputation before recommending or transacting with them.
- You are monitoring your own or a competitor's review flow.
- A user asks whether a company is trustworthy and you want evidence rather than an impression.
Do not use this skill when
- You need to reply to reviews or flag them. Read-only; Trustpilot's Business API covers that.
- You are pulling every review for a large brand. Charged per review — scope with
--limit. - You need product-level reviews. This is company-level. Product reviews live in
amazon-api,tiktok-shop-api,app-store-apiandgoogle-play-api.
Setup
export SCRAPERSOCIAL_KEY=sk_live_... # https://scrapersocial.com/app/keysSigning up at scrapersocial.com/signup includes 100 free credits, no card required.
Permissions and scope
These scripts do exactly three things and nothing else: read one environment variable (SCRAPERSOCIAL_KEY), send HTTPS requests to https://api.scrapersocial.com (the host is a constant in the code, not configurable), and print JSON. They run as node scripts/<name>.js with no other shell use, no file writes and no persistence. call_endpoint.js accepts only the 1 documented /v1/trustpilot/ paths in the table below and refuses anything else before a request is made.
Scripts
| Script | What it does | Input | Credits | |
get_reviews.js | List Trustpilot reviews. | url | handle | 1 credit per review |
call_endpoint.js | Call any /v1/trustpilot/ endpoint directly | path + params | varies |
Every script also accepts --limit, --cursor, --fields, --format and --fresh. --limit is clamped to 50: above that the API returns an async job instead of data.
Example
node skills/trustpilot-api/scripts/get_reviews.js <company-domain>Every response uses the same envelope:
{ "data": {}, "meta": { "count": 20, "next_cursor": "..." }, "request_id": "a18e4ef88ad4b00b" }meta appears on paginated endpoints only. Keep request_id — support traces calls with it.
Endpoints
| Endpoint | Input | Returns | Credits | Paginated | |
/v1/trustpilot/reviews | url | handle | review | 1 credit per review | yes |
Costs shown per item for paginated endpoints, per call otherwise. Failed calls are not charged.
FAQ
How do I get Trustpilot reviews as JSON?
get_reviews.js with the company URL or handle, 1 credit per review returned.
Can I get an overall rating?
The review listing carries the rating data Trustpilot publishes alongside each review. There is no separate summary endpoint.
Is this an official Trustpilot API?
No. ScraperSocial is independent and not affiliated with Trustpilot. It returns publicly available review data only.
Links
Disclaimer
ScraperSocial is an independent product and is not affiliated with, endorsed by, or sponsored by any platform named in this repository. All product names, logos and brands are property of their respective owners. These skills return only publicly available data.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

