linkme-api
Skill3 starsChanged 3 months agoMIT-0View on GitHub
Linkme data toolkit via ScraperSocial — resolve a Linkme page to the links and profile details it publishes.
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
- 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
- truth-social-apiSkill
- twitch-apiSkill
- twitter-apiSkill
- youtube-apiSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Read public Linkme pages as clean JSON.
- Very specific: line 45
The page is a Linktree, not a Linkme: Use the linktree-api skill.
- 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
Linkme API skill
Read public Linkme pages as clean JSON. This Linkme API skill has a single endpoint: give it a handle and it returns the links and profile details that page publishes, for 1 credit — the quickest way to turn a creator's link-in-bio into structured data.
This skill wraps 1 live Linkme endpoint from the ScraperSocial API. Public data only, returned as clean JSON.
When to use this skill
- You are resolving a creator's link-in-bio into their actual destinations.
- You are building a creator profile and want every channel they link to.
- A user pastes a Linkme handle and asks what is on it.
Do not use this skill when
- The page is a Linktree, not a Linkme. Use the
linktree-apiskill; they are different services. - You need analytics for a page you own. Linkme's own dashboard has those.
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/linkme/ paths in the table below and refuses anything else before a request is made.
Scripts
| Script | What it does | Input | Credits |
get_page.js | Get LinkMe page. | handle | 1 credit |
call_endpoint.js | Call any /v1/linkme/ 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/linkme-api/scripts/get_page.js <linkme-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/linkme/page | handle | page | 1 credit | no |
Costs shown per item for paginated endpoints, per call otherwise. Failed calls are not charged.
FAQ
What does the Linkme endpoint return?
get_page.js with the handle returns the page's links and profile details, for 1 credit.
Is this the same as Linktree?
No. Linktree is a separate service with its own skill in this repo, linktree-api.
Is this an official Linkme API?
No. ScraperSocial is independent and not affiliated with Linkme. It returns publicly available page 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.

