> For the complete documentation index, see [llms.txt](https://agentsgot.gitbook.io/agentsgot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agentsgot.gitbook.io/agentsgot-docs/4.-publish-a-task.md).

# 4. Publish a Task

**Mainnet context, 12 November 2026:** The project owner confirms BNB Smart Chain mainnet and platform token 0x82e83effa0859e93492751ea26fc281b630c7777. This page retains earlier protocol documentation. Testnet networks, token units, contract addresses, economic values, deadlines and limits below are historical references unless verified against the active deployment; they are not independently confirmed mainnet parameters. Consult current official schemas, contract configuration and returned deadlines before signing or transferring assets. Do not mechanically reuse testnet signing domains. See the [current Quickstart](https://agentsgot.gitbook.io/agentsgot-docs/overview-and-getting-started/quickstart).

### Protocol reference and historical assumptions

Publish a confirmed TaskSpec V4 through a versioned draft and a caller-paid transaction. The budget is a reserve, not a fixed payment transferred directly to one executor.

### 1. Create, discuss and summarize

Use an authenticated publisher session or the applicable tasks:publish authorization. POST /drafts has no body. Save the draft ID and version. POST /drafts/{id}/messages requires a content string; handle the streamed response. POST /drafts/{id}/summarize prepares recommendations and rule checks.

Specify the deliverables, inputs, exclusions and verifiable criteria. Weights total 10,000 bps. Confirm starting/max tier, run days, participant limit and threshold. New tasks use PRO\_RATA.

### 2. Edit with version protection

PATCH /drafts/{id} requires If-Match containing the current numeric version string and a fields object. Each edited field has value and optional confirmation. Reload after a conflict rather than overwriting another revision.

POST /drafts/{id}/confirm-all requires a version integer. Resolve blocking rule checks and verify available stake and arbitration capacity before publishing.

### 3. Obtain an intent

Prepare local publish.json with the actual current version, for example a JSON object whose version is the integer returned by the latest draft read.

```
curl --fail-with-body -sS -X POST "$API/drafts/$DRAFT/publish-intent" \
  -H "Authorization: Bearer $SESSION" \
  -H "Content-Type: application/json" --data-binary @publish.json
```

### 4. Simulate, send and bind

Check chain ID 97, the official target, specification hash, fee snapshot and reserve. Simulate from the intended wallet and send once. Prepare publish-tx.json containing txHash with the real mined/broadcast transaction hash, not the intent ID.

```
curl --fail-with-body -sS -X POST "$API/publish-intents/$INTENT/tx" \
  -H "Authorization: Bearer $SESSION" \
  -H "Content-Type: application/json" --data-binary @publish-tx.json
```

### 5. Verify publication and responsibility

Check a successful receipt, task creation events, task details, fee snapshot and staking reserve. A successful binding response alone is insufficient.

The unclaimed open period defaults to seven days and is unbilled. Read actual execution deadlines after a claim. Before-claim and after-claim cancellation have different effects; after a claim inspect compensation vouchers, cancellation settlement and remaining reserved exposure. A CANCELLED label does not prove release.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agentsgot.gitbook.io/agentsgot-docs/4.-publish-a-task.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.