Research and monitoring
Pull Threads signals such as user info, user info by id, user posts, post detail into repeatable market, creator, or community research workflows.
Threads API connector for agent workflows
Threads Social Data Connector gives AI agents one managed route for Threads search, profile, feed, detail, or trend operations. It is built for teams comparing Threads API options, scraper alternatives, and agent-ready social data workflows.
- Connector ID
- social.threads
- Sub-functions
- 4
- Cost
- 3 credits per successful run
What this Threads connector is for
Use it when an AI agent needs repeatable Threads research, public profile lookup, content detail checks, hot list monitoring, or search enrichment without managing separate credentials inside the agent. Vernclaw keeps every request behind one stable connector contract and returns normalized data for automation.
Managed connector access
Agents call Vernclaw with a stable connector ID, params object, and compact JSON response without managing separate credentials.
Normalized social data
Return platform, operation, result, and item fields in a consistent envelope so downstream automations do not parse varying response formats.
Supported Threads API sub-functions
This page covers User info, User info by id, User posts, Post detail. Choose the operation name in the request, then pass the platform-specific parameters through `params`.
User info
user_infoFetch Threads user info by username.
User info by id
user_info_by_idFetch Threads user info by user id.
User posts
user_postsFetch public Threads posts by user id.
Post detail
post_detailFetch Threads post detail by post id.
Agent and CLI usage
Agents can inspect the schema with `describe`, then invoke the platform connector with a selected operation and JSON params.
vernclaw-cli describe social.threads
vernclaw-cli invoke social.threads --operation user_info --params '{"username":"zuck"}'- Platform
- threads
- Default operation
- user_info
- Input params
- operation, params
Threads connector FAQ
Is this a Threads API or a scraper?
It is a Vernclaw connector. Agents call Vernclaw with a supported Threads operation, and the response is normalized for automation.
Do I need to manage a separate API key?
No for normal Vernclaw connector use. Vernclaw users authenticate with a Vernclaw API key and managed access is handled for them.
Which Threads operations are supported?
Supported operations are User info (user_info), User info by id (user_info_by_id), User posts (user_posts), Post detail (post_detail).
Can I use it from the Vernclaw CLI?
Yes. Run vernclaw-cli describe social.threads to inspect required fields, then invoke it with operation and params. Use vernclaw-cli list --json for structured catalog discovery.