Your first API, MCP or CLI workflow

Find a hired Artisan, give it a specific outcome and read the resulting work:

artie artisans --profile work --query research --json
artie task create --profile work --artisan ARTISAN_UUID --instructions-file brief.txt --key project-summary-001 --wait 120 --json
artie task show TASK_UUID --profile work --all --json
artie task runs TASK_UUID --profile work --limit 5 --json
artie task result TASK_UUID --profile work --run RUN_UUID --all --json

Example brief.txt:

Summarize the product notes I selected for this task. Give me the three decisions, unresolved questions and their sources. Keep the result in this task; do not send or publish it.

All uppercase identifiers in this guide are placeholders. Replace UUID placeholders with IDs returned to your own authorized session, revisions with current returned revisions, and digests/cursors with actual returned values. Examples use placeholders and fictional work.

An accepted task is saved work, not a completed result. A result can be partial. A successful run is an execution fact, not your verdict that the outcome is good. Observe actual state, result readiness, delivery, output and human acceptance separately.

task show --all includes instructions, not every detail page. task result --all follows result collections within 100 requests and 2.4 million text characters; check complete and returned continuation values. task watch can return exit 0 when work is done or needs your input. Exit 0 alone is not proof of successful completion.