The CLI

The spideriq CLI puts SpiderPublish in your terminal. It is ideal for scripting, CI pipelines, and anyone who prefers the command line. It uses the same API and the same safety model as the dashboard and MCP.

Install

Run it on demand with npx, or install it:

npm install -g @spideriq/cli --registry https://npm.spideriq.ai

Then spideriq --help lists everything available.

Authenticate

Request access — this emails your admin to approve:

spideriq auth request --email you@yourcompany.com

Check who you are signed in as at any time:

spideriq auth whoami

See Authentication for tokens and the approval flow.

Bind your workspace

In a project directory, bind it to your workspace so commands target the right site:

spideriq use <your-workspace>

This writes spideriq.json. Commands run from that directory (or below it) automatically use that workspace and project.

Everyday commands

  • Content — spideriq content manages pages, posts, docs, and settings.

  • Templates and themes — spideriq templates list, spideriq templates apply-theme <name>.

  • Forms — spideriq form creates, edits, and publishes forms.

  • Agents — spideriq agent finds, hires, and embeds a live AI agent on your site.

  • Deploy — spideriq content deploy previews and pushes your site live.

Manage your embedded agent from the CLI

Put a live AI agent (SDR, support, concierge) on your site — and manage it — without opening the dashboard.

spideriq agent roster          # agents you already hired on OPVS — re-embedding one is free
spideriq agent catalog         # the storefront of agents you can buy
spideriq agent hire <id> --roster   # re-embed one you already own (free); omit --roster to buy a new one
spideriq agent list            # your embedded agents + the flow id for each
spideriq agent embed-snippet <flow_id> --mode inline   # paste-ready embed code

hire always answers with a status — active (your flow_id is ready to embed), provisioning (run the same command again to check), or payment_required (it hands you a checkout link). After you hire a new agent for a site on a new domain, allow that domain on the agent so the conversation can start — pass --origin https://your-site.com when you hire. Full walkthrough: Agent Embed.

Safe by default

Destructive commands preview first. For example, spideriq content deploy shows you what will change and asks for confirmation before going to production. For automation, you can pass a confirmation token from a prior preview, or opt into non-interactive output. See Safe Publishing.

In CI

Because the CLI authenticates with a token and supports non-interactive output, you can run deploys and content updates from a pipeline — for example, redeploy a site whenever its source changes. Store your token as a secret and bind the workspace in the job.

Tips

  • spideriq.json is per-directory. Keep one per site so commands never target the wrong workspace.

  • Preview before you automate. Run a command interactively once to see its preview before wiring it into a script.

Next steps