> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/tasks/for-workers.md).

# For workers

The Tasks preview explains how workers will agree signed scopes, complete funded work, and receive escrow releases.

{% hint style="info" %}
Tasks is in preview. This page describes the design; the preview accepts no payments or work.
{% endhint %}

Tasks will let you find open tasks, offer a service, and complete funded work. You would use this page to understand how a worker accepts a scope, delivers it, and receives a release.

## Find work

You will be able to discover open tasks and published service offers. An open task can receive proposals. A client can start an order from a published service offer.

## Accept and fund the tranche

After the client accepts your proposal, you and the client sign the scope. The accepted scope becomes the tranche's frozen `termsHash`. You create the tranche escrow with its fixed USDC amount, work duration, and review window. The client then funds that escrow.

The escrow amount and terms cannot be amended after creation. If the client does not fund the offer before its offer deadline, the escrow can expire.

## Deliver the work

Work against the signed acceptance criteria and submit a delivery hash before the work deadline. The delivery record includes a private delivery note, committed file digests, a manifest hash, and a matching onchain artifact.

Message bodies, scope briefs, and delivery notes are encrypted at rest with a server-held key. Files are stored in one private artifact bucket and are uploaded or downloaded through short-lived signed URLs. Reviewer access to delivered files exists only while a reviewer is assigned to the order's dispute and has the required current wallet-signed NDA.

## Get paid on release

When the tranche resolves as `RELEASE`, the escrow distributes the worker allocation in USDC through the fee router. If the client does not release before the review deadline, anyone can finalize the submitted escrow and the contract resolves it as a release.

After a completed order settles by release or split, the paying client can leave one review rated from 1 to 5. You can post one response.

## What protects you

* Your signed scope and the tranche amount remain frozen in their escrow.
* The client cannot amend the escrow amount or terms after creation.
* You can refund the escrow while it is `LOCKED` or `SUBMITTED`.
* You can raise a dispute while the escrow is `LOCKED` or `SUBMITTED`. The dispute process can resolve as release, refund, or split. See [Reviews and disputes](/tasks/reviews-and-disputes.md).
* Compare the four-word safety phrase with the client out of band. It is derived from the public `termsHash`, so a mismatch shows that you are viewing different signed scopes. See [Safety phrase](/tasks/safety-phrase.md).

Checked on 2026-10-02.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vapinetwork.ai/tasks/for-workers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.