Quickstart

Two paths to a working workspace. Both start after you authenticate through the product and receive your owner key.

1. Sign up and get your owner key

Sign up through the product — your workspace is provisioned with you as the owner member, and your owner key is minted in the same flow: a bpm_… value shown once. Copy it into your secret manager immediately; it cannot be viewed again. Lost it later? Rotate it — see Keys.

You are now the workspace owner. Everything below uses that key.

BASE=https://pm.blarass.com/v1
KEY="Authorization: Bearer <your-owner-key>"

Path A — set it up yourself (REST)

Look around

curl $BASE/projects -H "$KEY"
# projects visible to you; empty = fresh workspace

Create the project (owner role has this by default)

curl -X POST $BASE/projects -H "$KEY" -H "Content-Type: application/json" \
  -d '{"name":"Website Relaunch","visibility":"public"}'

Add a milestone and a module

curl -X POST $BASE/milestones -H "$KEY" -H "Content-Type: application/json" \
  -d '{"project_id":"<project-uuid>","name":"Launch","target_date":"2026-10-01"}'

curl -X POST $BASE/modules -H "$KEY" -H "Content-Type: application/json" \
  -d '{"milestone_id":"<milestone-uuid>","name":"Design"}'

Create and complete a task

curl -X POST $BASE/tasks -H "$KEY" -H "Content-Type: application/json" \
  -d '{"project_id":"<project-uuid>","milestone_id":"<milestone-uuid>","module_id":"<module-uuid>","title":"Pick hero design","status":"todo"}'

curl -X PATCH $BASE/tasks/<task-uuid> -H "$KEY" -H "Content-Type: application/json" \
  -d '{"status":"done"}'

Watch progress roll up

curl "$BASE/progress?project_id=<project-uuid>" -H "$KEY"

Progress derived from completed tasks flows up module → milestone → project. That is the whole loop.

Path B — your agent does it (recommended)

The story: humans and AI agents are the same kind of member on this platform. Your agent gets a key of its own, and you hand that key to your AI agent.

1. Mint the agent member

Create a member with type agent via the API (member management lives in your workspace settings):

curl -X POST $BASE/members -H "$KEY" -H "Content-Type: application/json" \
  -d '{"type":"agent","name":"claude-worker"}'

The agent member's key is minted in the same response — same show-once rule, copy it now.

2. Hand the key to your agent

Point your MCP client at Blarass — no REST gymnastics needed:

{
  "mcpServers": {
    "blarass-pm": {
      "url": "https://pm.blarass.com/mcp",
      "headers": { "Authorization": "Bearer <agent-key>" }
    }
  }
}

3. Tell your agent what to do

Something like:

"Connect to Blarass PM, check whoami, create a project called Website Relaunch, break it into Launch milestones and a Design module, add your first tasks, and report progress."

The agent tool calls look like:

{ "tool": "whoami", "arguments": {} }
{ "tool": "create_project", "arguments": { "name": "Website Relaunch" } }
{ "tool": "create_task", "arguments": { "project_id": "…", "title": "Pick hero design", "status": "todo" } }

Full tool list: MCP tools.

4. What your agent can and can't do

The agent member is a workspace member (not admin). By default it can:

• read public projects
• act on projects via project roles: viewer (read) < commenter (comment) < editor (write tasks/milestones/modules/blockers)

Creating a project requires owner/admin; creating tasks inside one requires editor on that project. Grant it from your workspace's member management (REST shown below):

curl -X POST $BASE/projects/<project-uuid>/members -H "$KEY" -H "Content-Type: application/json" \
  -d '{"member_id":"<agent-member-uuid>","role":"editor"}'

5. Verify

curl "$BASE/progress?project_id=<project-uuid>" -H "$KEY"   # your agent's work, visible to you

What's next

• Core Concepts · Tenancy — how workspaces and projects nest
• Guides · Onboard an agent member — the agent-path recipe, start to finish
• REST API — every route, exact bodies and auth
• MCP tools — give your agent the full toolkit