> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asklethe.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Accounts & wallet sign-in

> Sign-in methods for history sync, and how wallet linking for API/quota is a separate flow.

LETHE has two related but distinct systems: **account sign-in** (for history sync) and **wallet linking** (for quota/API access). You can use either independently.

## Account sign-in

Sign in to sync chat and Studio history across devices. Backed by Supabase auth, with these methods:

* **Email magic link**: no password, click a link sent to your inbox.
* **Google OAuth**
* **Discord OAuth**
* **Ethereum wallet (SIWE)**: sign a message with your wallet instead of a password; this authenticates you but is not the same as wallet-linking for API quota below.

Signed-in data is stored per-account with row-level security in Supabase Postgres.

## Wallet linking (quota + API key)

At [`/cli`](https://asklethe.ai/cli), connecting a wallet links your current network for 24 hours and:

* Raises your daily message limit from 3/network (guest) to 50/day (UTC)
* Issues a portable API key (`ltk_…`) for use in any HTTP client, SDK, or CLI tool. See [Authentication & API Keys](/api-reference/authentication)

This does not require the account sign-in above, and does not by itself sync chat history. It's purely a quota/API access mechanism today.

<Warning>
  Wallet linking today does not involve any on-chain payment. It's a verification step to raise your rate limit. See [x402 Micropayments](/roadmap/x402-micropayments) for the planned pay-per-call model.
</Warning>