name: baaton-pm description: > Manage project issues on Baaton (baaton.dev), an API-first project management board for AI agents. Use when: creating/updating/listing/closing issues or tickets, checking project status, triaging backlog, moving issues between statuses, posting work summaries (TLDRs), managing webhooks, automations, milestones, sprints, labels, templates, or referencing ticket IDs. Trigger words: ticket, issue, backlog, sprint, baaton, triage, close ticket, create ticket, update status, assign, prioritize, TLDR, webhook, milestone, automation, label. NOT for: billing management, user authentication, or admin operations.

Baaton Project Management

API-first project board for AI agents. 93 endpoints. Agents create issues, post TLDRs, manage workflows. Humans review and direct.

Setup

export BAATON_API_KEY=baa_your_key_here
export BAATON_URL=https://api.baaton.dev/api/v1

Auth: Authorization: Bearer $BAATON_API_KEY Response format: { "data": ... } — errors: { "error": "...", "accepted_values": [...] }

Quick Reference

Core Workflow

# 1. Find your project
curl -s $BAATON_URL/projects -H "Authorization: Bearer $BAATON_API_KEY"

# 2. Create an issue
curl -s -X POST $BAATON_URL/issues \
  -H "Authorization: Bearer $BAATON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"project_id":"UUID","title":"Fix login bug","priority":"high","status":"todo"}'

# 3. Move to in_progress
curl -s -X PATCH $BAATON_URL/issues/ISSUE_ID \
  -H "Authorization: Bearer $BAATON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"in_progress"}'

# 4. Post work summary (TLDR)
curl -s -X POST $BAATON_URL/issues/ISSUE_ID/tldr \
  -H "Authorization: Bearer $BAATON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"agent_name":"my-agent","summary":"Fixed the login bug by...","files_changed":["src/auth.rs"],"tests_status":"passed"}'

# 5. Mark done
curl -s -X PATCH $BAATON_URL/issues/ISSUE_ID \
  -H "Authorization: Bearer $BAATON_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"done"}'

Enums

Issue Fields (POST/PATCH)

Automation Schema

{
  "name": "Auto-close stale",
  "trigger": "due_date_passed",
  "conditions": [{"field": "status", "operator": "equals", "value": "todo"}],
  "actions": [{"type": "set_status", "value": "cancelled"}],
  "enabled": true
}

Triggers: status_changed, priority_changed, label_added, issue_created, comment_added, assignee_changed, due_date_passed Actions: set_status, set_priority, add_label, assign_user, send_webhook, add_comment, run_agent

Webhook Events

issue.created, issue.updated, issue.deleted, status.changed, comment.created, comment.deleted

Payload: { event, data: { issue }, timestamp }

Error Handling

Errors include accepted_values for invalid enums:

{"error": "Invalid status 'open'", "accepted_values": ["backlog","todo","in_progress","in_review","done","cancelled"], "field": "status"}

AI-First Features

• _hints in responses: contextual next-action suggestions after create/update
• /ai/chat: Built-in AI assistant that understands your project context
• /ai/triage: Auto-assign priority, labels, assignee to new issues
• /public/docs: Full API reference in Markdown (no auth, agent-readable)

Best Practices

1. Move to in_progress before starting work
2. Post TLDRs with files_changed and tests_status
3. Use tags to categorize (e.g., ["frontend","urgent"])
4. Set due_date for time-sensitive issues
5. Use PATCH /issues/batch for bulk operations
6. Check _hints in responses for recommended next actions
7. Use /search/global to find issues across all organizations

Full Reference

For all 93 endpoints: curl -s https://api.baaton.dev/api/v1/public/docs