Skip to main content

Quickstart

This page walks you through Actx0 for the first time. First you set things up in the dashboard: a workspace, a plan, and an access key. Then you pick a client — Pctx0 (Python), Nctx0 (Node.js), Gtcx0 (Go), cURL, or Acli — and do four things:
  1. Send a chat message (Actx0 turns it into a memory)
  2. Search those memories
  3. Upload a document and search it
  4. Save a prompt and load it by name
That is the same path your agent will use in production.
1

Create a workspace

Sign in at app.actx0.com. If you are new, register with email, GitHub, or Google.Open Workspaces, create a workspace, and copy its id. Everything below is scoped to that workspace.
2

Choose a plan

Open Billing and pick a plan. Hobby is free with basic limits. Starter, Growth, and Pro raise capacity for agents, sessions, memories, documents, prompts, API calls, and AI usage (extraction and search).For this guide, use a paid plan so you do not hit Hobby limits mid-way. Manage payment later from the same Billing page.
3

Create an access key

Open Settings → Access keys and create a key. Grant permissions for agents, sessions, messages, memories, prompts, and knowledge (create, list, get, query, update, delete as listed).Copy the secret immediately — it is shown only once. Send it as X-Access-Key. Keep it on the server, never in a browser or git.
4

Install a client

5

Create an agent and session

An agent owns conversations. A session is one run — use an external id you already have (demo-1, a user id, a ticket number).
6

Save a user message

Post the user’s turn. Actx0 stores it, indexes it, and extracts a memory in the background (greetings are skipped; useful facts become long_lived or short_lived). Assistant replies do not trigger extraction.
7

Search memories

Wait a few seconds for extraction, then search with the next user question. Put the hits in your model prompt.You can also write a memory yourself when you already know the fact (kind: summary, fact, preference, short_lived, long_lived).
8

Upload knowledge and search it

Knowledge is workspace-wide (FAQs, policies), not session memory. Upload UTF-8 .txt or .md (max 2 MB). Wait until status is indexed, then search.
9

Store a prompt and fetch it

Save the system prompt in the workspace. At runtime, fetch by handle: production for live traffic, latest while you iterate.
Before each model reply: fetch the prompt, search memories (and knowledge if the question is about your docs), then generate.
Keep access keys server-side. Never expose them in browser or mobile clients.

Next steps

Platform overview

How messages become memories

Agents

Sessions, messages, and scope

Knowledge

Documents, labels, and search

API Reference

Full REST surface and SDK samples