ssh.autos

Catalog / Social, content & reviews

SOCIAL, CONTENT & REVIEWS

X (Twitter) Profile & Post

Collect public X (Twitter) profiles and posts by link.

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 X (Twitter) profiles and posts by link. Profiles come with exact follower, following and post counts, bio, website, verification and join date, plus latest posts. Posts come with text, media and exact likes, reposts, replies, quotes, bookmarks and views. Pay only for rows delivered.

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/x/snapshot

Fetch one public X/Twitter profile and up to two posts displayed on it, or one post by URL/ID.

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

Profile rows include name, bio, location, website, follower/following/post counts and verification.

Post rows include public text, author, publication time and engagement counts supplied by X.

Replies are not crawled.

Input

Send a JSON body to POST https://api.ssh.autos/v1/x/snapshot.

FieldTypeRequiredNotes
sourcestringrequired1–2048 characters
includeLatestPostsbooleanoptionaldefault 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 51 fields; a field the source does not publish comes back null.

51 fields per record
FieldTypeNotes
typestringprofile or post
one of profile, post
idstringX's numeric id of the profile or post
urlstringThe profile or post page on X
originstringrequested: from your input; latest: a profile's latest post; reply: a top reply under a post link
one of requested, latest, reply
usernamestringHandle without @ (profiles only)
namestringDisplay name (profiles only)
biostring—
locationstring—
websitestring—
createdAtstringJoin date (profiles) or posting time (posts), ISO 8601 UTC
followersinteger—
followinginteger—
postsCountinteger—
isBlueVerifiedboolean—
verifiedTypestringBusiness, Government or null
isProtectedboolean—
avatarUrlstring—
bannerUrlstring—
professionalTypestring—
affiliatesCountinteger—
subscribersCountinteger—
latestPostIdsarray of strings—
textstringPost text with links expanded (posts only)
langstring—
authorIdstring—
authorUsernamestring—
authorNamestring—
authorFollowersinteger—
authorIsBlueVerifiedboolean—
authorVerifiedTypestring—
authorAvatarUrlstring—
likesinteger—
repostsinteger—
repliesinteger—
quotesinteger—
bookmarksinteger—
viewsintegernull for older posts without a view counter
mediaarray of objectsPhotos, videos and GIFs: type, url (image or video preview), width, height, altText, videoUrl (best quality MP4), durationMs
hashtagsarray of strings—
mentionsarray of strings—
linksarray of strings—
possiblySensitiveboolean—
isReplyboolean—
inReplyToIdstring—
inReplyToUsernamestring—
isQuoteboolean—
quotedPostobjectThe quoted post: id, url, text, createdAt, author, likes, reposts, replies, views, media
isPinnedboolean—
countsPartialbooleantrue when only likes and reply count could be read
sourcestringThe input line this row came from
scrapedAtstring—

Example call

TERMINAL · $0.01 PER RUN
npx agentcash@latest fetch https://api.ssh.autos/v1/x/snapshot -m POST -b '{"source": "NASA", "includeLatestPosts": 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: X (Twitter) Profile & Post 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.