Already have a login? Keep it

Use Claspine’s AI, files, payments, notifications and audit without moving your users or changing how they sign in.

⏱ About 10 minutes

Claspine’s features do not require Claspine’s sign-in. If your app already signs people in (Spring Security, Auth0, Clerk, Cognito, your own), keep it: your backend checks the person as it does today, then calls Claspine on their behalf, passing your own user ID where Claspine asks who did something. This is how every Claspine Atlas project works: Claspine Atlas does not store your users’ accounts or sign them in, so your app keeps its login and calls Claspine Atlas with the project’s API key (what runs where).

Words you’ll see

API key: A long secret string that lets software use your account, like a password made for programs. Anyone who has it can spend on your account, so treat it like a password.
Session: What keeps a person signed in. Claspine gives your app a session token after sign-in; every later request carries it. Claspine checks it, ends it at sign-out, and can end every session of a person at once.

Steps

Leave your login, users table and sessions exactly as they are.
Call Claspine from your backend only, never from the browser: with the Claspine Atlas project API key (X-Spine-Api-Key), or with the engine’s service key when self-hosted.
Where Claspine asks who is acting (audit entries, notification recipients, payments), pass your own stable user ID, for example "user-123". Use the same ID every time for the same person so their history lines up.
Spring Boot with self-hosted Claspine: call the capability services directly with your own IDs, for example new ActorId("user-" + me.getId()) and new AccountId(me.getId()); your security filter stays in charge.
Later, if you want Claspine to take over sign-in, follow the sign-in guide for your stack. Firebase can import your existing users, so nobody has to sign up again.

Your login protects the route; Claspine Atlas does the AI call (any language works the same with HTTP).

app.post('/api/summaries', requireYourLogin, async (req, res) => {   // your auth, unchanged
  const answer = await fetch('https://api.claspine.com/api/v1/llm/complete', {
    method: 'POST',
    headers: { 'X-Spine-Api-Key': process.env.SPINE_API_KEY, 'Content-Type': 'application/json' },
    body: JSON.stringify({ input: req.body.text }),
  }).then((r) => r.json());
  res.json({ summary: answer.content, by: req.user.id });
});

What goes where in Claspine

Console field	Value
Claspine Atlas API key	Claspine console → your project → API keys. Server-side only.
Your user ID	Whatever your app already uses (database ID, Auth0 sub, Clerk user ID); keep it stable.

Keep it safe

Check the person with your own login before every call to Claspine: Claspine trusts your backend, so your backend decides what each person may do.
Never put the Claspine API key or service key in a browser or mobile app.

Claspine stores the values encrypted, never shows them again in full, and never sends them to your app or SDK.

Provider documentation

← All setup guides