Connector CLI (vernclaw-connect-cli) — Install, Login, List, Invoke

Install vernclaw-connect-cli and run the connector CLI in five commands: install, login, list connectors, describe parameters, invoke, and check job status.

Quick Start

Five commands from zero to first connector result:

npm i -g vernclaw-connect-cli          # install the connector CLI
vernclaw-cli login                     # authenticate (browser opens)
vernclaw-cli list                      # list available connectors
vernclaw-cli describe seo.google-trends  # inspect parameters
vernclaw-cli invoke seo.google-trends --keywords "openai" --market us  # run it

Requires Node.js 20 or later. The vernclaw-cli command is available globally after install.

Need a repeatable agent workflow after install? Use the MCP connector workflow guide for JSON parsing, batch tasks, and agent skills.

Install

npm i -g vernclaw-connect-cli

Login

Browser login (recommended for interactive use):

vernclaw-cli login

Opens your browser for device-code authorization. Credentials are stored locally at ~/.vernclaw-cli.json.

API key login (for CI/CD and headless environments):

vernclaw-cli login --api-key YOUR_API_KEY

Generate an API key at API Keys (sign in → API Keys → Create API Key).

List and Describe

vernclaw-cli list                            # human-readable connector table
vernclaw-cli list --json                     # JSON catalog for scripting
vernclaw-cli describe seo.google-trends      # show parameters for one connector

list --json returns a compact JSON payload for agent and script use:

{
  "status": 200,
  "data": {
    "command": "list",
    "count": 3,
    "connectors": [
      { "id": "seo.website-traffic", "category": "SEO", "status": "available" },
      { "id": "seo.google-trends", "category": "SEO", "status": "available" },
      { "id": "generate.image", "category": "AI", "status": "available" }
    ],
    "hints": []
  }
}

Invoke a Connector

vernclaw-cli invoke seo.website-traffic --domain example.com

Sync connectors print results immediately. Async connectors (such as generate.image) return a job ID. Poll it with:

vernclaw-cli job get <jobId>

Add --pretty to any invoke call for human-readable terminal output instead of compact JSON.

Check Account Status

vernclaw-cli status

Prints your current login identity, active subscription tier, and remaining credit balance.

Commands

CommandDescription
vernclaw-cli loginAuthenticate via browser or API key
vernclaw-cli logoutRemove stored credentials
vernclaw-cli listList available connectors
vernclaw-cli describe <connectorId>Show connector details and parameters
vernclaw-cli invoke <connectorId> [flags]Run a connector and print connector output
vernclaw-cli job get <jobId>Check status of an async job
vernclaw-cli statusDisplay current login, subscription, and credit status

Output Format

All connector results use a JSON-first envelope printed to stdout:

{
  "status": 200,
  "data": {
    "summary": "...",
    "metrics": {}
  }
}
  • Metric tools: data.summary + data.metrics
  • List tools: data.summary + data.stats + data.items
  • Trend tools: data.stats + data.metrics + data.series
  • Extract tools: data.document

Add --pretty to render the same JSON as readable terminal text. Errors expose errorCode at the top level and x-error-code in API response headers.

Exit Codes

CodeMeaning
0Success
1Business rejection (e.g. insufficient credits)
2Authentication failure
3Invalid parameters
4Upstream failure

Provider Keys

Most CLI users only need a Vernclaw login or API key. Provider-level keys (such as YouTube Data API v3) are configured by the AIAPI Center operator, not per CLI user.

For YouTube connectors, the operator creates a Google Cloud project, enables YouTube Data API v3, generates an API key under APIs & Services → Credentials, and configures it in AIAPI Center's youtube provider.

Available Connector Skills

Each connector ships with a SKILL.md for AI agent integration via vernclaw-connect-cli on GitHub:

Connector IDCategoryModeSkill
generate.imageAIasyncvernclaw-image-generate
seo.website-trafficSEOsyncvernclaw-website-traffic-get
seo.backlinksSEOsyncvernclaw-backlinks-get
seo.serp-google-organicSEOsyncvernclaw-serp-google-organic-get
seo.google-trendsSEOsyncvernclaw-google-trends-get
seo.keyword-search-volumeSEOsyncvernclaw-keyword-search-volume-get
seo.keyword-suggestionsSEOsyncvernclaw-keyword-suggestions-get
seo.site-keywordsSEOsyncvernclaw-site-keywords-get
seo.site-technologiesSEOsyncvernclaw-site-technologies-get
seo.backlinks-summarySEOsyncvernclaw-backlinks-summary-get
seo.domain-rank-overviewSEOsyncvernclaw-domain-rank-overview-get
seo.domain-whoisSEOsyncvernclaw-domain-whois-get
seo.domain-authoritySEOsyncvernclaw-domain-authority-get
read.x.postSocialsyncvernclaw-x-post-read
read.x.repliesSocialsyncvernclaw-x-post-replies-read
read.x.articleSocialsyncvernclaw-x-article-read
search.xSocialsyncvernclaw-x-search
search.youtubeVideosyncvernclaw-youtube-search
read.youtube.videoVideosyncvernclaw-youtube-video-read
search.producthuntProductsyncvernclaw-producthunt-search
list.producthunt.launchesProductsyncvernclaw-producthunt-launches-list
search.webSearchsyncvernclaw-web-search
extract.urlExtractsyncvernclaw-url-extract

FAQ

What npm package provides the vernclaw-cli command? The npm package is vernclaw-connect-cli. Install with npm i -g vernclaw-connect-cli. After install, the global command is vernclaw-cli.

How do I use the connector CLI without a browser (headless/CI)? Run vernclaw-cli login --api-key YOUR_API_KEY. Generate the key at /settings/apikeys.

How do I list all available connectors as JSON? Run vernclaw-cli list --json. The response contains a data.connectors array with each connector's id, category, and availability status.

How do I use the CLI in an AI agent workflow? Use statuslist --jsondescribeinvokejob get as the stable chain. See the MCP connector workflow guide for full examples.

How do I check my credit balance or subscription status? Run vernclaw-cli status. It prints your login identity, subscription tier, and remaining credit balance.

How do I check whether an async job finished? Run vernclaw-cli job get <jobId> with the job ID returned by invoke. Poll until status is "ok" or "error".