# Create a Tweetsmash account

How a new user gets a Tweetsmash account, what happens right after, and what an
agent can and cannot do in that flow. Authentication for the API and MCP server
is a separate step, described at `https://www.tweetsmash.com/auth.md`.

Signup page: `https://www.tweetsmash.com/signup`

## What you need

A Tweetsmash account is anchored to an X (Twitter) account. X is both the
sign-in identity and the data source — the bookmarks Tweetsmash imports live
there. There is no password anywhere in the product.

## The two signup methods

| Method | Where | What happens |
| --- | --- | --- |
| Sign up with X | `https://www.tweetsmash.com/signup` | The button redirects to x.com to authorize the Tweetsmash X app, including bookmark read access. On the callback the account is created automatically and the browser is signed in. |
| Chrome extension | [Chrome Web Store](https://chrome.google.com/webstore/detail/tweetsmash/fmjgfjanmcbhpmlemahbnfehjoboopce), offered first on `/signup` in desktop Chromium browsers | The extension creates the account from the X session already signed in on x.com and imports the full bookmark history. |

Methods that do **not** exist — do not look for them and do not report them as
available:

- No email + password form. Tweetsmash has no passwords.
- No Google or Apple OAuth.
- No programmatic signup. There is no API endpoint that creates an account.

Existing accounts sign in at `https://www.tweetsmash.com/login`, either with X
or with a one-time code sent to the account's email address. The email-code
lane signs in accounts that already exist; new Tweetsmash accounts are created
with X.

ListX, the X-list-digest product, is the one exception: it has its own
email-based signup at `https://www.tweetsmash.com/listx/signup`, where entering
an email address and the one-time code it receives creates the account, and X
is connected later.

## After signup

1. New accounts land on `https://www.tweetsmash.com/welcome` to run the first
   bookmark import. Importing bookmarks is free.
2. Signup starts a 7-day free trial. Paid plans — Reader Pass, Yearly Pass and
   the one-time Exports Pass — are described at
   `https://www.tweetsmash.com/pricing`.
3. API keys are created afterwards, by the signed-in user, at
   `https://www.tweetsmash.com/integrations/api`. How a key is used against the
   REST API and the MCP server is covered by
   `https://www.tweetsmash.com/auth.md`.

## If you are an agent

Signup is human-in-the-loop by design: it requires the user to authorize the
app on x.com in their own browser. You cannot complete it on their behalf, and
you must not ask for their X credentials.

- Send the user to `https://www.tweetsmash.com/signup` and let them pick a
  method.
- While you wait, the sandbox at `https://api.tweetsmash.com/v1/sandbox`
  mirrors the REST API over fixture data with no key and no account, so you can
  build and test first.
- Once the account exists, the user creates an API key at
  `https://www.tweetsmash.com/integrations/api` and pastes it to you. From
  there, follow `https://www.tweetsmash.com/auth.md`.