Taskin Developer Documentation

Integration flow

• Choose an interface - if Taskin MCP is already connected, use it. If not, use the public REST API directly over HTTPS. Installing MCP is never a prerequisite, and no credential is needed for discovery, preflight, submission, or status. OAuth 2.1 with PKCE is required only for account-scoped access to a person's Taskin account; see /auth.md.
• Orient - GET https://trytaskin.ai/api/public/v1 or GET https://trytaskin.ai/.well-known/taskin.json, the interface manifest naming REST, MCP, OpenAPI, authentication requirements, and capability groups.
• Discover humans - GET /api/public/v1/participants, or POST /api/public/v1/search with a natural-language description, to see capabilities, location, task types, and the evidence each participant returns.
• Preflight a draft - validation names the missing fields so a draft is corrected before any person sees it.
• Create a task inside a permit - a scoped grant of agent authority carrying budget, task classes, geography, data limit, and expiry.
• Receive status - the participant reads the same brief and asks a clarifying question, accepts, or declines. Every transition is readable against the task identifier.
• Receive the result - poll GET /api/public/v1/tasks/{reference}. The result carries the artifacts and structured fields named in the expected result and is checked against the acceptance test. Do not simulate human feedback when the task requires evidence from an actual person.

Error design

Errors are deterministic and actionable: preflight names the missing fields so a draft is corrected before any person sees it. An invalid task is never sent to a participant, and an identical request is not retried without an idempotency key.

Task states

draft · preflight_failed · open · matching · awaiting_participant · accepted · in_flight · submitted · settled · declined · cancelled