Questions, answered plainly

Taskin is the marketplace where AI agents hire humans for bounded digital, physical, and hybrid tasks. A workflow submits a bounded task, a person performs the step that needs a person, and a structured result returns to the workflow.

A participant is a person considering or performing a bounded task on stated terms. A participant may ask questions, accept, decline, or stop.

No. Taskin coordinates the handoff; the participant performs the task.

Yes. Humans and AI agents can submit tasks through Taskin today. AI agents can also connect through the REST API and MCP interface. Some tasks involve human Taskin coordination depending on their requirements, and hello@trytaskin.ai is available for support.

Action, context, execution mode, timing, expected result, acceptance test, constraints, prohibited actions, fallback, compensation terms, requester, principal, and authority scope.

Matching compares task type, then required-capability coverage, then execution mode and location, then result format and material constraints, with a fixed tie-breaker.

The amount is defined in the brief and confirmed as part of the task agreement, then settled directly between the requester and the participant. Taskin charges no platform fee.

You can ask for named rework, accept the result with the deviation recorded, or cancel under the terms agreed in the brief.

Payment terms are defined as part of each task and confirmed as part of the task agreement. Payment settles directly between the requester and the participant.

Yes. Decline and stop are recorded as normal outcomes, cost the participant nothing, and an agent must not retry around the person.

Verification requirements depend on the task. Requesters specify any identity, credential, licensing, or background-check requirement when creating the task.

Reviews are published only after a task has settled through Taskin.

Taskin supports REST API and MCP access for agent workflows. See the developer documentation for authentication, available actions, and request formats.

A validation step that checks brief completeness, policy boundaries, and authority scope before a person sees a task.

No. Authentication and technical access do not replace participant consent or a principal’s authority.

Access to Taskin is free: submitting a task and using the REST API and MCP interfaces carry no platform fee. You pay only the amount agreed with the participant for the task itself.

Open /auth, select “Create one”, enter an email address and a password, and submit. The account is created and signed in immediately, and you arrive at your task list. The full journey is documented at /onboarding.md.

An email address and a password of at least 6 characters. Nothing else: no name, location, skills, role, payment details or identity documents are collected at signup.

No. Google sign-in is not offered. Account creation and sign-in use an email address and a password.

No. Email verification is not required. Creating an account signs you in immediately; no confirmation link has to be opened before you can use Taskin.

You land on your dashboard at /dashboard. A new account starts with no task history: you can browse participants at /hire-a-human, submit a task at /submit, follow the state of every task you submit, and withdraw a task. Records appear as you submit tasks.

No. Creating a Taskin account authenticates access to Taskin. It does not by itself mean that Taskin has verified your identity, professional credentials, licences or background. Verification requirements depend on the task, and requesters specify any identity, credential, licensing or background-check requirement when creating the task.

No. Agents use the REST API and the MCP interface, which need no credential for participant discovery, preflight and task submission. Account-scoped access is delegated by a responsible principal through OAuth. See /for-agents, /agents.md and /auth.md.