ssh.autos

Catalog / Social, content & reviews

SOCIAL, CONTENT & REVIEWS

Threads Profile & Posts

Collect public Threads profiles and their latest posts.

PER CALL · X402 / MPP From $0.01 per call 1 endpoint at api.ssh.autos. Pay in USDC, no account. See the endpoint
APIFY STORE Public actor Run it with your Apify account: bulk runs, schedules and exports. Open on Apify

About this data

Collect public Threads profiles and their latest posts. Paste usernames or profile links to get name, bio, links, exact followers, verified badge and photo, plus each recent post's text, time, likes, replies, reposts and media. Failures are not charged.

From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.

Buy per call over x402

One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.

POST /v1/threads/profile

Fetch one public Threads profile and optionally up to two posts from its initial page.

PRICE$0.01 per call, in USDC
RESULTOne JSON answer per call
PAYMENTx402 or MPP · no account

Returns the displayed name, bio, follower count, verification and profile picture; posts include public text/media, publication time and engagement counts when supplied.

No pagination or login.

Input

Send a JSON body to POST https://api.ssh.autos/v1/threads/profile.

FieldTypeRequiredNotes
profilestringrequired1–400 characters
includePostsbooleanoptionaldefault true
maxPostsintegeroptional1–2; default 2

Returned fields

The answer is JSON: records, a list, and summary, the run status and counts. Each record has these 33 fields; a field the source does not publish comes back null.

33 fields per record
FieldTypeNotes
kindstringprofile: one row per profile. post: one row per post. Failures live in OUTPUT.sourceErrors and are never dataset rows.
one of profile, post
usernamestringThe profile's username, or the post author's username.
urlstringLink to the profile or post on threads.com.
isVerifiedbooleanWhether the profile (or post author) has the verified badge.
userIdstring—
fullNamestring—
biographystringProfile rows only.
bioLinksarray of stringsLinks listed on the profile. Profile rows only.
followerCountintegerExact follower count. Profile rows only.
isPrivatebooleanProfile rows only.
profilePicUrlstringLargest available profile picture. Profile rows only.
postsReturnedintegerPost rows collected for this profile. Profile rows only.
postIdstring—
codestringThe post's short code from its link.
textstring—
createdAtstringPost time (UTC, ISO 8601).
likeCountinteger—
replyCountinteger—
repostCountinteger—
quoteCountinteger—
mediaTypestringone of text, image, video, carousel, other
imagesarray of strings—
videosarray of strings—
linkUrlstringThe link a post previews, when it has one.
quotedPostUrlstringLink to the post this post quotes.
isReplybooleanTrue for a post that continues the author's own thread or replies to another post.
isPinnedbooleanTrue for a post pinned to the profile.
isRepostbooleanTrue when the post shown on the profile was written by another account.
profileUsernamestringThe profile the row was collected from; null for rows from post links.
sourcestringThe input kind the row came from.
one of profile, post
inputstringThe input value exactly as given.
scrapedAtstring—
errorobjectAlways null in the dataset. Failed profiles and posts live in OUTPUT.sourceErrors and are not charged.

Example call

TERMINAL · $0.01 PER RUN
npx agentcash@latest fetch https://api.ssh.autos/v1/threads/profile -m POST -b '{"profile": "nasa", "includePosts": true, "maxPosts": 2}'

The example values come from the API spec or the actor’s own sample input. Running it is a paid call.

What is and isn’t charged

Free

  • Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
  • Invalid input and source failures are not charged.

Prefer a subscription? Run it on Apify

This data source is a public actor on the Apify Store: Threads Profile & Posts Scraper. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.

Open on Apify

How x402 payment works

  1. Your client sends the request. The API answers 402 Payment Required with the price and where to pay.
  2. The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
  3. The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.

The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.

Machine-readable: openapi.json · llms.txt

Some links to Apify are affiliate links. We may earn a commission if you sign up and become a paying customer.