# AvianSuite. Agent setup

This origin is AvianSuite: a current-state workspace on a Stellar Jay store. Aim a client at https://dev.aviansuite.com/llm.txt.

An agent connection is a live API/writer credential on the workspace (a current writer token). It is not a linked Magpie, Martin, or Grok app. Opening this page does not create a connection.

## Connect over MCP (recommended)

Add https://dev.aviansuite.com/mcp as a remote MCP server (Streamable HTTP) and send an agent token as Authorization: Bearer. Mint one at https://dev.aviansuite.com/account/agents; each token is its own agent, so every change it makes is kept, attributed to it, and can be undone on its own.

Tools: record_fact, correct_fact, retract_fact, get_entity, list_changes, undo_changes (a dry run unless confirm is true), save_checkpoint, status. Give every write an operation_id that stays the same when you retry it.

Do not build a separate MCP server per app. A new inventory (or any other) tool should be a CLI on the same Stellar Jay store, or use these tools.

## Connect

The Stellar Jay store is the source of truth. Magpie and Martin are the public CLIs on this store.

```sh
export STELLARJAY_URL='https://dev.aviansuite.com'
export STELLARJAY_TOKEN='writer-token-for-this-store'
# Magpie and Martin still read the pre-rename names:
export JAYBASE_URL="$STELLARJAY_URL" JAYBASE_TOKEN="$STELLARJAY_TOKEN"
```

- STELLARJAY_URL is an HTTPS origin only (no path, token, query, or fragment).
- STELLARJAY_TOKEN lives only in the environment. Never put it in a flag, URL, payload, log, or prompt.
- This is the Stellar Jay writer/reader token (32-512 characters), the same token the MCP server takes. It is not an AvianSuite password, not a Magpie MCP bearer (MAGPIE_MCP_TOKEN), and not a workspace registry id.
- Workspace ids look like agt_… / ten_… / usr_… and are exactly 20 characters. Stellar Jay rejects anything under 32 characters with 401 valid bearer token required. If the value you were given is 20 characters, it is the wrong secret.
- AvianSuite does not display this token on the standing Agents page. After you sign in, mint a reader or writer at https://dev.aviansuite.com/account/agents. AvianSuite shows the plaintext once on that POST, then never again. This is not writer-initial from stellarjay-server init and not an AvianSuite password.
- Operators can still mint on the store host with add-token if the one-time reveal was lost:
```sh
stellarjay-server add-token /path/to/secrets/auth.json agent-writer writer
```
Then export the printed token as STELLARJAY_TOKEN. Recreate the Stellar Jay process so it reloads auth.json. Do not put the new token in this prompt.

Prove the store:

```sh
curl -fsS "$STELLARJAY_URL/health/ready"
curl -fsS -H "Authorization: Bearer $STELLARJAY_TOKEN" "$STELLARJAY_URL/v1/root"
```

Ready must be Stellar Jay JSON ({"status":"ready"}). If you see the workspace UI ready JSON instead, you pointed STELLARJAY_URL at the UI host. The UI is https://dev.aviansuite.com. The operator/bootstrap store is https://dev.aviansuite.com.

If TLS verification fails, fetch the host CA from https://dev.aviansuite.com/aviansuite-stellarjay-ca.crt and pass it to curl --cacert.

A token minted after sign-in is valid only on that workspace origin. This document does not list workspaces.

## Spaces

Spaces are the types stored in this workspace. Magpie is the books CLI. Martin is the CRM CLI. Point either CLI at the store with the variables above. Install only what you need.

```sh
magpie --actor owner state
martin --actor owner state
```

Do not pass --store when the store URL is set. --actor is a domain identity, not authentication.

The aviansuite binary is not a public command.

## Humans

Sign in at https://dev.aviansuite.com/login. Source: https://dev.aviansuite.com/source.