Guides

CLI & agent skill

The published InboxIt terminal client.

Install and sign in

The package is @onedigitsa/inboxit; the command is inboxit. Email login prompts for a hidden password. Sign-up requires confirmation.

Example

npm install -g @onedigitsa/inboxit
inboxit login
inboxit whoami
inboxit help
inboxit commands

Workspace and account

Workspace names are 1–10 characters. Select by returned UUID.

Example

inboxit signup --email you@example.com --name "Your Name"
inboxit login --email you@example.com
inboxit workspaces create --name prod
inboxit workspace use --id WORKSPACE_UUID

Agent skill

Download the bundled instructions and give the file to your agent. Its permissions remain those of the credential you grant.

Example

inboxit skill --output ./inboxit-skill.md

Structured automation

JSON goes to stdout; errors go to stderr with a nonzero exit. --data accepts JSON, @file.json or - for stdin. --query accepts a JSON object. --output creates a file without overwriting. Writes are not automatically retried.

Example

inboxit emails send --data @email.json --idempotency-key order-001
inboxit logs list --query '{"status":"failed","limit":20}'
inboxit messages raw --id INBOX_UUID --message 42 --output message.eml

Configuration

--workspace overrides the selected workspace. --origin or INBOXIT_ORIGIN overrides the HTTPS origin. INBOXIT_TOKEN supplies a scoped API key. Login credentials are stored per origin in ~/.inboxit/credentials.json; INBOXIT_CONFIG_DIR overrides this directory. Keep it private.

Coverage

Endpoint pages include matching commands. billing get maps to /usage. smtp create-key maps to key creation. request can call implemented routes; it does not add unsupported features. Whole-account/workspace deletion is not implemented.

Example

inboxit request GET /usage
inboxit logout