Getting started with wrxstack.

Five minutes from "I have an account" to "I shipped a workflow." This guide assumes you've signed up and have a teammate to invite. If you don't, follow the link in your invite email first.

Prerequisites

You need an Atlas account (free works), a terminal, and any HTTP client (curl works fine). If you plan to wire up SSO before your first invite, have an admin from your IdP on hand for a single five-minute window.

1. Create the workspace

   Sign in at atlas.wrxstack.com. The first page asks for a workspace name and a subdomain. Pick something stable. Renames are supported but they break old links.

   Workspaces are isolation boundaries. Two workspaces never share data, never share the work graph, and never share audit logs. You can belong to many; everyone signs in once.

2. Invite a teammate

   Open the People tab. Paste an email. The default role is member, which can read everything in the workspace but not change billing or rotate API keys. Promote to admin from the same row when you need to.

   If you're planning to use SSO, skip the email step and go straight to the SSO guide. Pre-provisioning seats by email and then layering SSO on top is the slower path.

3. Create an API key

   Create an API key from Settings → API keys in Atlas. Keys are scoped to a workspace. The first key you create has full read/write; rotate it to a scoped role before shipping anything customer-facing.

   export WRX_API_KEY="sk_live_..."
   export WRX_WORKSPACE="acme"

   Every Atlas API request authenticates with the key in an Authorization: Bearer header and the workspace in the URL.

4. List your assistants

   Every workspace ships with three pre-built assistants: triage, recap, and redline. List them to confirm everything is wired:

   curl https://atlas.wrxstack.com/api/v1/$WRX_WORKSPACE/assistants \
     -H "Authorization: Bearer $WRX_API_KEY"
   
   # tsk_assistant_01HQ... triage Triage incoming tickets
   # tsk_assistant_01HQ... recap  Summarize a meeting
   # tsk_assistant_01HQ... redline Review an MSA

5. Run an assistant against a real task

   Create a task, ask the assistant to act, then read the audit log. This is the loop you'll write a hundred more times.

   # Create a task
   curl https://atlas.wrxstack.com/api/v1/$WRX_WORKSPACE/tasks \
     -H "Authorization: Bearer $WRX_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"title":"Review pricing one-pager from Acme","assignee":"priya@acme.com","labels":["sales","acme"]}'
   
   # Invoke the triage assistant on it
   curl https://atlas.wrxstack.com/api/v1/$WRX_WORKSPACE/assistants/triage/invoke \
     -H "Authorization: Bearer $WRX_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"input":{"task_id":"tsk_01HQ3K..."}}'

   The response lists the run's steps. You should see a handful of tool calls (read the task, search the graph, post a comment, label it), each with a status and a duration. Open the run URL in the response to see the same trail in the UI.

6. Ship a workflow

   A workflow is a saved triple: an assistant, the data it can see, and the actions it can take. Define one as JSON and create it through the Atlas API.

   curl https://atlas.wrxstack.com/api/v1/$WRX_WORKSPACE/workflows \
     -H "Authorization: Bearer $WRX_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "inbound-leads",
       "assistant": "triage",
       "trigger": "forms.submitted",
       "scope": {
         "read": ["crm:accounts", "forms:submissions"],
         "write": ["crm:opportunities", "slack:#sales"]
       },
       "approvals": { "above_arr": 100000, "require": "role:sales-lead" }
     }'
   
   # Workflow inbound-leads created · v3 · audited

Next steps

You have a workspace, a teammate, an API key, and a workflow under change control. From here, the next page depends on what you came to ship:

• Building an assistant from scratch. Go to Writing your first workflow and the deeper Tool calling guide.
• Connecting your IdP. Read SSO with Okta. Roughly 15 minutes if you have the Okta admin in the room.
• Importing existing data. The Notion and Salesforce imports cover ~80% of common starting points.

If you're more of a "read all the API docs first" person, that page is API overview. Every endpoint has a curl sample. Need broader API access? Email hello@wrxstack.com.