# Tasks (/docs/api/gateway/tasks)

Outcome billing: list the tasks your requests opened and confirm or reject their result.

A task is opened by the first request of a piece of work and settled by its outcome. Confirmation needs the owner's own key — there is no act-as path. Money fields are micro-EUR integers. How tasks and spend interact: [tasks & spend](../../agents/tasks-and-spend.mdx).

Agents read tasks through the MCP server tools `tasks_list` (`status`, `limit`), `tasks_get` (`id`) and `tasks_stats` (`since`). There is no confirm tool: settling a task is billing and stays with a human.

<OpenAPIPage document="./openapi/en/gateway.yaml" operations={[{path: '/v1/tasks',method: 'get'},{path: '/v1/tasks/pending',method: 'get'},{path: '/v1/tasks/stats',method: 'get'},{path: '/v1/tasks/{id}',method: 'get'},{path: '/v1/tasks/{id}/confirm',method: 'post'}]} />