truth-social-api
Skill3 starsChanged 3 months agoMIT-0View on GitHub
Truth Social data toolkit via ScraperSocial — public profiles and user post timelines 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
- trustpilot-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 44
You need to post or interact: Read-only.
- Very specific: line 67
Every script also accepts --limit, --cursor, --fields, --format and --fresh.
- Distinctive: line 75
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
Truth Social API skill
Read public Truth Social data as clean JSON. This Truth Social API skill has two endpoints: a public profile and a user's posts, at 2 credits each. Coverage of this network by mainstream data tools is thin, which matters for anyone doing balanced media monitoring rather than monitoring only the platforms that are easy to read.
This skill wraps 2 live Truth Social endpoints from the ScraperSocial API. Public data only, returned as clean JSON.
When to use this skill
- You are doing cross-platform media or discourse monitoring and need this network represented.
- You are tracking what a specific public account posts.
- A user pastes a Truth Social link and asks what the account is.
Do not use this skill when
- You need search. There is no search endpoint here — you need a known handle. Profile and posts only.
- You need to post or interact. Read-only.
- You need private accounts. Public data only.
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 2 documented /v1/truthsocial/ paths in the table below and refuses anything else before a request is made.
Scripts
| Script | What it does | Input | Credits |
get_profile.js | Get Truth Social profile. | handle | 2 credits |
get_user_posts.js | List Truth Social user posts. | handle | 2 credits per post |
call_endpoint.js | Call any /v1/truthsocial/ 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/truth-social-api/scripts/get_profile.js <truthsocial-handle>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/truthsocial/profile | handle | profile | 2 credits | no |
/v1/truthsocial/user-posts | handle | post | 2 credits per post | yes |
Costs shown per item for paginated endpoints, per call otherwise. Failed calls are not charged.
FAQ
What can I get from Truth Social?
Two endpoints: get_profile.js for a public profile and get_user_posts.js for that account's posts, 2 credits each.
Can I search Truth Social by keyword?
No. This API covers profile and posts only, so you need the handle up front.
Is this an official Truth Social API?
No. ScraperSocial is independent and not affiliated with Truth Social or TMTG. It returns publicly available 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.

