Install SocQ CLI
Add the published @socq/cli package and make the socq command available in your terminal.
Use one command line across public social platforms to discover the live API catalog, submit collections, complete asynchronous tasks, and deliver normalized results to shell scripts, CI, and data analysis workflows.
Install SocQ CLI, store your API key securely, then run an endpoint with the same definition used across SocQ docs, MCP, and REST.
Add the published @socq/cli package and make the socq command available in your terminal.
Store the key in the system keyring or a protected local configuration.
Run the YouTube comments endpoint and continue through the normalized result.
For CI, provide SOCQ_API_KEY through your secret manager so credentials stay protected across automated runs.
Read the complete CLI guideExplore APIs, submit a collection, check an existing task, or export results. Each command works independently and can be combined in local terminals, shell scripts, and CI when your workflow requires it.
$ socq tools youtubeExplore the current YouTube endpoints from the live Capability Registry.
These six examples use current SocQ endpoint IDs and accepted inputs. Each command is ready to copy and adapt to your workflow.
Endpoint: youtube/commentsCollect publicly visible YouTube comments and wait for normalized results.
Endpoint: x/searchBuild a focused public X post dataset from a search query.
Endpoint: tiktok/searchSearch public TikTok videos and export normalized records.
Endpoint: instagram/commentsCollect public comments from a known Instagram post URL.
Endpoint: facebook-ad-library/searchSearch public Facebook Ad Library creatives by keyword.
Endpoint: linkedin/jobsNormalize a public LinkedIn job page into structured job fields.
SocQ CLI submits each collection as a background task and returns a task ID. Wait in the current command with --wait or save the task ID and resume later, then read normalized results or retrieve available files.
Run a platform and resource command to create a background task.
The CLI returns the unique reference used to wait, resume, and read results.
Use --wait now or continue the same task later with its task ID.
Export normalized results and inspect available files after the task succeeds.
01 / Submit a collection
Run the relevant platform and resource command. The CLI submits the collection as a background task.
task_id: TASK_IDThe CLI returns the unique task ID after submission.
SocQ CLI brings the live API catalog, asynchronous task control, and normalized results into your terminal. Validate a command locally, then use the same workflow in shell scripts and automated pipelines without maintaining separate collectors for every platform.
Platforms, endpoints, input schemas, and billing guidance come from the live Capability Registry, so you do not maintain a second fixed command catalog.
LIVE REGISTRY → CURRENT COMMANDS
JSON, JSONL, CSV, and table output, file export, and meaningful exit codes make the same command model reliable in shell scripts and automated pipelines.
JSON · JSONL · CSV · EXIT CODES
Keep the task ID to resume after a timeout or interrupted process, then continue through paginated results and available files without resubmitting the collection.
SUBMIT → TASK_ID → RESUME → RESULTS
MCP, CLI, and REST are execution paths. Agent Skill is a guidance layer. They share one API catalog and asynchronous task model, so you can choose the interface that fits your workflow.
Use one command model to discover APIs, submit collections, resume asynchronous tasks, and export normalized results to files and automation.
Optional enhancement · Agent Skill
Add endpoint selection, cost control, pagination, and task recovery guidance. Pair it with MCP first, or execute through CLI or REST.
SocQ CLI is SocQ's command-line tool. Use it to discover and call SocQ APIs, submit public social data collections, wait for or resume asynchronous tasks, and export normalized results to files, scripts, and automated pipelines.
Use CLI for terminal work, shell scripts, automated pipelines, batch collections, and file exports. Use MCP when an AI client should discover and call tools directly, or use the REST API for long-lived application integrations.
Yes. The CLI reads current platforms, endpoints, input schemas, and billing guidance from the live Capability Registry, so available commands follow the SocQ API catalog. Use socq platforms, socq tools, and socq describe to inspect current capabilities.
Not necessarily. Install @socq/cli globally for regular use so the socq command is always available. Use npx @socq/cli for occasional commands or to explore the API catalog first.
You can browse the public Capability Registry without an API key. Collections, account queries, and task or file access require one. Use socq auth login for local work, and provide SOCQ_API_KEY through a secret manager in automated pipelines.
No. A local wait timeout does not cancel the server-side task. Keep the task ID and run socq task get or socq task wait again to continue the same task without resubmitting the collection.
SocQ CLI supports table, JSON, JSONL, and CSV. Read small results in the terminal, or use --output to write normalized results to a file for scripts, spreadsheets, or data analysis.
SocQ CLI requires Node.js 20 or later and runs on Windows, macOS, and Linux.