Kip in your app

Your app signs each customer up to Kip with one call, keeps the key it gets back, and then saves what it knows into their memory and asks Kip questions as them. Your customers never see a Kip sign-in.

Get a partner key

On API keys, sign in with Google and press Create key. You get a partner key, kipp_..., shown once. Keep it on your server. Revoke it there at any time.

Create the user when your customer signs up

const res = await fetch("https://app.tryafk.com/api/v1/users", {
  method: "POST",
  headers: { authorization: `Bearer ${process.env.KIP_PARTNER_KEY}`, "content-type": "application/json" },
  body: JSON.stringify({ email: customer.email, first_name: customer.firstName, last_name: customer.lastName, external_id: customer.id }),
});
const kip = await res.json();
await db.customers.update(customer.id, { kipUserId: kip.user.id, kipKey: encrypt(kip.api_key) });

A work email gets a company brain, shared with everyone you sign up from that company. A Gmail or other consumer address gets a personal brain. The call is safe to repeat: the same email gives back the same user and key. See Create a user.

Save what your app knows

await fetch("https://app.tryafk.com/api/v1/remember", {
  method: "POST",
  headers: { authorization: `Bearer ${kipKey}`, "content-type": "application/json" },
  body: JSON.stringify({
    memories: [{ title: "Onboarding call", content: "Ada wants weekly reports on Mondays.", key: `call:${callId}` }],
  }),
});

Use a stable key per item so an update replaces the memory instead of copying it. See Remember.

Answer from their memory

For an answer written by Kip, with sources:

const res = await fetch("https://app.tryafk.com/api/v1/ask", {
  method: "POST",
  headers: { authorization: `Bearer ${kipKey}`, "content-type": "application/json" },
  body: JSON.stringify({ question: "When does Ada want her reports?" }),
});
const { answer, sources } = await res.json();

For raw context to give your own model, use Recall, then Read memory on the best paths.

Which endpoint

You want	Use	Speed
A finished answer, researched across the memory	Ask	seconds to a minute
The matching pages, to feed your own model	Recall then Read memory	under a second
To add to the memory	Remember	immediate; searchable within a couple of minutes

Company and personal

The first user you create at acme.com creates Acme’s company brain. Every later Acme user you create joins it, and scope: "company" on Ask and Recall reads it.
Personal memories, including everything saved with Remember, stay private to that person.
If Acme is already in Kip from another way in, your user gets a personal brain and company.status: "requires_google_sign_in": to join Acme’s existing company brain they sign in to Kip with their Google Workspace account.
An email that already has a Kip account it did not get from you answers 409 user_exists. You never receive the key of someone you did not sign up.
If your customer later signs in to AFK with Google themselves, the account becomes theirs and your key for it stops working.

Trust and safety

You vouch for every email you send. Send only addresses your app has verified.
Keep both keys on your server. The user’s kipm_ key acts as that user.
Kip redacts credentials and payment details from what it returns, and refuses to save memories that look like them.

Billing

Ask, Recall and Read memory are each one credit on the user’s plan. Remember is free. See Credits and usage. Questions about an integration: founders@tryafk.com.

Get started

API reference

Partners

Integrations

Which endpoint

Company and personal

Trust and safety

Billing

​Which endpoint

​Company and personal

​Trust and safety

​Billing

Which endpoint

Company and personal

Trust and safety

Billing