Getting started
Authentication
API keys, the bearer header, and how access is gated by subscription.
Every request authenticates with an API key tied to your workspace.
Passing the key
Use a bearer token (recommended — matches the SDK and the OpenAI/Anthropic convention):
curl https://www.artemise.live/api/v1/signals \ -H "Authorization: Bearer ns_live_..."
The x-api-key: ns_live_... header is also accepted.
Getting a key
Two ways:
- Dashboard — Settings → API → Create key. The plaintext is shown once.
- SDK login —
await Artemise.login()ornpx artemise loginruns a browser approval and provisions a key for you. See Connect the SDK.
Subscription requirement
API access is part of every paid plan. Without an active subscription:
- creating a key returns
402 - every
/api/v1call returns403 - SDK login approval is blocked in the browser
Subscribe in Settings → Billing (design partners: your promo code applies at checkout).
Key security
- Keys are 192-bit random secrets; only a SHA-256 hash is stored
- The plaintext is shown exactly once at creation
- Revoke instantly from Settings → API — revocation takes effect on the next request
- Never commit keys; use the
ARTEMISE_API_KEYenvironment variable