SocialGO

Built for machines

Run the panel from a script.

The CLI turns every SocialGO action into a command you can pipe, schedule and hand to an agent. Search the catalog, place orders, track them and check balance, from your terminal, a CI pipeline or a bot.

What you build on it

One command surface. Scripts, pipelines and agents.

Same commands the dashboard runs on. Exposed for code. Stitch them into a shell script, a CI step or an autonomous agent. Every command returns a clean exit code and machine-readable JSON.

Scripts

Chain commands in a shell script: find a service, place the order, poll the status. Pass --json and parse the output with jq.

Pipelines

Drop the CLI into a CI step or a cron job. It exits 0 on success and non-zero on failure, so your pipeline stops when an order does.

Agents

Hand the commands to an AI agent. It reads the catalog, confirms the rate and quantity, then places the order, the same calls you'd type by hand.

Spending is explicit. Search and list are read-only; an order only happens when you run order create with a service, link and quantity, in a script or by hand. The CLI never spends on its own.

Install

Install the CLI globally with npm, or run it on demand with npx and skip the install:

# install globally
npm i -g @socialgo/cli

# or run without installing
npx @socialgo/cli --help

Once installed, the socialgo command lives on your PATH. Run socialgo --help to list every command and flag.

Read the source on GitHub

Authenticate

The CLI reads an API key from the SOCIALGO_API_KEY environment variable. Generate a key in your dashboard, then export it in your shell or CI secrets:

# macOS / Linux
export SOCIALGO_API_KEY="your_api_key_here"

# Windows (PowerShell)
$env:SOCIALGO_API_KEY="your_api_key_here"

Treat the key like a password. Keep it out of version control. Use per-environment secrets or a .env file you never commit.

Commands

Search the catalog

Find services by keyword. Use it to grab the service id before you place an order. Read-only, it never spends:

socialgo services search "instagram followers"

List services

Print the full catalog of available services:

socialgo services list

Place an order

Order by service id, target link and quantity. This is the one command that spends. It runs only when you call it:

socialgo order create \
  --service <id> \
  --link <url> \
  --quantity 1000

Track an order

Look up the current status of an order by its id:

socialgo order status <id>

Check balance

Show the balance available on your account:

socialgo balance

Wallet

Inspect wallet details and recent transactions:

socialgo wallet

Admin: sync the catalog

For panel operators: pull the latest services and pricing from your connected provider into the local catalog. Requires an admin key:

socialgo admin sync-catalog

The three-command loop

Find a service, place the order, track it. The loop every script and agent runs:

# 1. find the service id
socialgo services search "instagram followers"

# 2. place the order
socialgo order create --service 1423 --link https://instagram.com/yourhandle --quantity 1000

# 3. track it
socialgo order status 90871

Script it end to end

Pass --json to any command and pipe it into jq. Here the script picks the cheapest matching service, then orders it, no clicking:

# pick the cheapest matching service, then order — with jq
id=$(socialgo services search "instagram followers" --json \
  | jq -r 'sort_by(.rate) | .[0].id')

socialgo order create --service "$id" \
  --link https://instagram.com/yourhandle --quantity 1000 --json

Exit codes & JSON

Every command returns 0 on success and a non-zero code on failure, so you can chain calls in CI pipelines and shell scripts. Pass --json to any command for machine-readable output to pipe into tools like jq, or to feed straight back to an agent.

Browse servicesConnect via MCPNeed help? Talk to us