auth-and-profiles

Configure Frontline CLI authentication and manage named profiles across multiple API environments.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/api-evangelist/frontline --skill auth-and-profiles-api-evangelist
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auth-and-profiles
Source: https://github.com/api-evangelist/frontline/tree/main/skills/vendor/auth-and-profiles
Command: npx skills add https://github.com/api-evangelist/frontline --skill auth-and-profiles-api-evangelist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing API credentials across multiple Frontline environments (production, staging, on-prem) is error-prone when done manually. This Skill explains how to authenticate the Frontline CLI with API keys, organize credentials into named profiles, and switch between environments without re-entering keys. ## Core Features & Use Cases - API Key Login: Store personal (USER) or account (GENERAL) API keys via frontline auth login, with keys kept in sync between the frontline and max binaries. - Named Profile Management: Create, list, switch, and remove profiles per environment, each with its own key and base URL. - Per-Call Overrides: Pass --api-key, --profile, or --base-url on any leaf command for one-off calls in scripts and CI without persisting credentials. - Use Case: A developer maintains dev and prod profiles, works against dev by default, then runs frontline auth profiles use prod to query production agents and workflows with the correct key automatically applied. ## Quick Start Log in to the Frontline CLI with my API key and create separate profiles for my staging and production environments.

Frequently Asked Questions about auth-and-profiles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate the Frontline CLI with an API key?▼

Run `frontline auth login <api-key>` to store the key in the current profile, which defaults to `default` and points at the production Public API. Create a personal key in the Frontline app under My settings, Bring your own Agent.

How do I switch between multiple Frontline environments?▼

Create a named profile per environment with `frontline auth login <key> --profile staging --base-url <url>`, then switch with `frontline auth profiles use <name>`. Every subsequent command uses that profile's key and base URL.

What is the difference between a personal key and an account key in Frontline?▼

A personal (USER) key attributes writes to the user and works on all endpoints, while an account (GENERAL) key is read-only and returns 401 on endpoints requiring USER scope. Personal keys are recommended for CLI use.

Can I override credentials for a single Frontline CLI command?▼

Yes, pass `--api-key`, `--profile`, or `--base-url` on the leaf command, such as `frontline agents list --profile staging`. Flags take priority over environment variables, which take priority over the active profile.

Why does the Frontline CLI return 401 Unauthorized on write operations?▼

A 401 on writes usually means you are using a GENERAL account key on an endpoint that requires USER scope. Create a personal API key under Bring your own Agent in the app and log in again.

Where does the Frontline CLI store its config files?▼

Config is stored via the standard conf package paths: ~/Library/Preferences/frontline-cli-nodejs/ on macOS, ~/.config/frontline-cli-nodejs/ on Linux, and %APPDATA%\frontline-cli-nodejs\Config\ on Windows. Run `frontline auth profiles list --pretty` to see the exact path.