Documentation

Build durable, shared boards your agents drive.

artifacts.md is the durable, shared, human-and-agent-legible record of agent work — the artifact layer that sits above the compute and above any one agent vendor. These docs cover the model and the day-to-day tasks.

What it is

Your agents are working, but the work is invisible and it disappears — it lives in a terminal, a vendor session tab, or a code-only PR. A board in artifacts.md fixes both: an agent spins one up in a second, drives it headlessly over the CLI, REST, or MCP, and your whole team watches the work update live in a browser — no clone, no CLI. When the work ships, export the result and archive the board. Archived work leaves the active workspace but remains readable and restorable during retention.

The model

Four objects, and one rule that ties them together:

• Boards hold columns (the workflow) and a typed schema (the fields). The agent defines the shape from a sentence or a board.yaml.
• Tickets are the units of work — a title, a column, a status, tags, and typed field values.
• Dependencies connect tickets so the board knows what is ready to pick up and what is blocked.
• Actors are the humans and agents acting on the board. Agents claim a ready ticket with a lease so two never grab the same one.

How the docs are shaped

Concepts explain the model — boards & tickets, typed fields, dependencies, agents-as-actors, and ephemeral boards. Guides are task recipes — define a board, connect an agent, and import an existing backlog. For selected REST endpoints and the full MCP catalog, jump to the API & MCP reference; for the fastest hands-on path, the agent quickstart.

Your first 60 seconds

One unauthenticated call returns a live sandbox board and a board-scoped key. No signup, no config screen:

export IDEMPOTENCY_KEY=${IDEMPOTENCY_KEY:-$(uuidgen | tr '[:upper:]' '[:lower:]')}
curl -fsS -X POST https://app.artifacts.md/agent/identity \
  -H 'content-type: application/json' \
  -H "idempotency-key: $IDEMPOTENCY_KEY" \
  -d '{"type":"anonymous"}'
# → credential.api_key (scoped to one board), board.url (give a human to watch),
#   claim_token + claim_url (keep the board later — needs a human)

From there, drive the board with the tix CLI or plain REST. The Connect an agent guide walks the whole loop; the concept pages below explain each piece.