Skip to main content

Documentation Index

Fetch the complete documentation index at: https://authsome.agentr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Livestorm uses a long-lived API key. Authsome stores the key encrypted in the local vault, injects it at request time through the proxy, and keeps it out of shell history, process listings, and environment dumps.

At a glance

Provider namelivestorm
Display nameLivestorm
Auth typeAPI key
HeaderAuthorization: Bearer <key>
Proxy hostapi.livestorm.co
Env varLIVESTORM_API_TOKEN
Where to get a keyhttps://app.livestorm.co/#/settings/account/api-tokens

Get a key

Create an API key in the Livestorm dashboard at https://app.livestorm.co/#/settings/account/api-tokens.

Log in

uvx authsome login livestorm
A local browser form opens at http://127.0.0.1:7998. Paste the key into the masked input and submit. On a headless machine without a graphical session, authsome falls back to masked terminal input via getpass. The browser bridge is skipped automatically when no display is available. Verify:
uvx authsome get livestorm --field status
# → connected

Use the key

Run the agent under the proxy. The library tab is for embedding authsome inside a larger Python orchestrator.
uvx authsome run -- python my_agent.py
Under the proxy, authsome sets LIVESTORM_API_TOKEN=authsome-proxy-managed in the child’s environment and injects the real key into outbound requests to api.livestorm.co. The child process never sees the actual value.

Multiple keys

Pass --connection <name> on login and on every read command to keep two or more accounts on the same provider side by side. See Multiple connections per provider for the full pattern.
uvx authsome login livestorm --connection personal
uvx authsome login livestorm --connection team

Rotate or remove the key

uvx authsome login livestorm --force          # rotate
uvx authsome logout livestorm                  # remove local credential
uvx authsome remove livestorm                  # remove all local state for the provider
API-key providers have no revocation endpoint, so revoke and remove are equivalent for Livestorm.

Override the bundled definition

uvx authsome inspect livestorm > ~/.authsome/providers/livestorm.json
# edit fields
uvx authsome list   # source now shows "custom" for livestorm
See Provider schema for every field.

What’s next

Run agents with the proxy

Keep the key out of the agent’s environment entirely.

Multiple connections per provider

Keep two or more keys on the same provider side by side.

API-key providers

All bundled API-key providers.

Provider schema

Every field in a provider definition.