API & account

Pathvela runs on one account. It holds your identity, your credit balance, and the API keys the agent authenticates with — the same account whether you use the CLI or the SDK.

Developer console

Sign in and manage everything at:

platform.pathvela.com

The console is where you mint, rotate, and revoke API keys and review your usage.

API keys

Every request to the Pathvela backend carries a key, which the backend validates and meters against your account. There are two kinds:

• Signed-in user token — short-lived, refreshed by a Pathvela app while a user is logged in. Best for browser apps.
• Programmatic key — long-lived, minted in the console for servers, scripts, and the CLI. New keys look like sk-lily-…; older sk-agent-… keys still work.

Keys are sent as a bearer token:

Authorization: Bearer sk-lily-...

Managing keys in the console:

The agent endpoint

The agent itself is served from https://agent.pathvela.com. You normally reach it through the SDK or CLI rather than calling it directly — the SDK's baseUrl option points there by default, and you can route it through your own same-origin proxy if you prefer.

A model-listing endpoint is available for discovering what a key can use:

GET https://agent.pathvela.com/v1/models

The SDK wraps this as listModels().

Metering

Usage is metered in credits against your account, at a rate that depends on the model tier. Both the SDK and the CLI report token usage per run so you can track spend:

const result = await agent.runDetailed(messages)
console.log(result.usage) // { inputTokens, outputTokens, cachedInputTokens, calls }

Next

• Your Pathvela account — signing in and minting keys.
• SDK: createLilyAgent reference — how the SDK authenticates.
• CLI: Commands — lily key commands.