Creating your account
Go to reclaimllm.com/register and create an account with GitHub, Google, or an email address and password. No credit card is required — the Free plan is free forever, and paid plans include a three-month free trial before any charge applies.Use the same sign-in method whenever you return. Email/password accounts can change their password from Settings; OAuth-only accounts continue through GitHub or Google.
Finding and creating API keys
RCLM uses API keys to authenticate session data ingest from hooks, the local API proxy (rclm-proxy), and any direct API usage. Team gateway keys for the hosted Enterprise Gateway (rclm-gw-… on proxy.reclaimllm.com) are separate and managed under the org LLM Gateway tab.
1
Open Settings
Sign in and select Settings from the top navigation.
2
Find API Keys
Scroll to API Keys on the Settings page.
3
Create a new key
Click Create API Key, give it a descriptive name (for example,
laptop-hooks or work-proxy), and confirm. Copy the key immediately — it is only shown once.How API keys are used for ingest
All three capture methods — hooks, proxy, and browser extension — authenticate with your RCLM account when uploading session data. The ingest endpoint accepts two authentication formats:
If you’re building a custom integration against the RCLM ingest API, pass your key as the
X-API-Key header on every POST /api/ingest request.
Account tiers
RCLM offers three tiers. All tiers include every capture method and full-text search.Upgrading your plan
To upgrade from Free to Paid, open Settings, find the plan and billing section, and select Upgrade. The Paid plan activates immediately with a three-month free trial; no credit card is charged until day 91. For Enterprise, go to reclaimllm.com/pricing#enterprise or email [email protected] to discuss seat counts, volume pricing, annual billing, and deployment requirements.Enterprise org membership
If your organization uses RCLM Enterprise, an org admin invites you by email from the enterprise portal. Once you accept:- Your account is linked to the org, and new sessions are tagged with your team attribution at ingest.
- An admin can optionally backfill your existing sessions into the org’s view so historical activity is included.
- Your personal capture tools (hooks, proxy, extension) continue working without any reconfiguration.
- Your access level — developer, team lead, or admin — is set by the org admin and determines what you can see in the enterprise portal.
Developers in an Enterprise org do not get access to the enterprise portal by default. The portal is visible to org admins and, within their team scope, to team leads.