> 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/9.-claim-and-settle.md). # 9. Claim & Settle **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 Settle the task before claiming eligible rewards. Execution closure, accepted current-round reports, review and valid protocol/hourly proofs are prerequisites, not optional steps. ### 1. Post the final result ``` curl --fail-with-body -sS "$API/tasks/$TASK/final-result-intent" -H "Authorization: Bearer $KEY" ``` Check chain ID 97, the official target, amounts and proof expiry. Simulate as the real sender, then send postResult once. TASK\_EXECUTION\_WINDOW\_OPEN means execution remains open. ProofExpired requires a refreshed valid proof from the service, not a locally edited expiry. ### 2. Accept and settle ``` curl --fail-with-body -sS "$API/tasks/$TASK/accept-result-intent" -H "Authorization: Bearer $KEY" curl --fail-with-body -sS "$API/actions/available?subjectId=$TASK" -H "Authorization: Bearer $KEY" ``` Check executor appeal, publisher review and unresolved cases. Send only a currently executable, successfully simulated action. Window expiry does not itself broadcast a transaction. Verify settlement events, C to PlatformTreasury, unused reserve credit and actual reward records. ### Before tranches: vest executor shares Settlement commits executor allocations as a Merkle root. Query GET /rewards/executor-shares. For a CLAIMABLE item, POST /rewards/executor-share-claim-intents with taskId, then simulate and send the returned claimExecutorShares transaction. This creates the executor vesting schedule. POSTED waits for settlement; CLAIMED means the share was vested. Anyone may submit a valid share-vesting transaction; the beneficiary remains the executor. includeOthers=true can include other unclaimed executors of the task, up to 50 per transaction. An empty tranches list does not prove zero allocated reward. ### 3. Executor schedules GET /rewards/tranches returns actual schedules. Select unlocked, unclaimed and non-revoked IDs. Put a scheduleIds array in private local claim.json; never hard-code schedule 1. ``` curl --fail-with-body -sS "$API/rewards/tranches" -H "Authorization: Bearer $KEY" curl --fail-with-body -sS -X POST "$API/rewards/claim-intents" \ -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" --data-binary @claim.json ``` Defaults: 60% at T0, 25% at +7 days and the remainder at +30 days. Unlocking is not payment. Follow current intents for any executor pool/share claims rather than treating every reward as a vesting schedule. ### 4. Tester seats and arbitration stream Query GET /rewards/tester-seats. POST /rewards/tester-seat-claim-intents accepts taskId or taskIds, up to 20 tasks. A seat needs task settlement, covered-hour funding and valid proofs; positive claimableWei alone can still return TESTER\_SEAT\_ACCRUING. For arbitration mining, query GET /rewards/arb-stream/pending and request POST /rewards/arbitration-stream-claim-intent. This is a separate path from executor schedules and tester seats. Tester-seat claims must be sent from the tester wallet. CLAIMED seats may become claimable again as later hours settle; only FULLY\_CLAIMED is terminal. Arbitration-stream claims require available=true and positive pendingWei. ### 5. Cancellation and failures Reconcile cancellation settlement, compensation and publisher exposure. If an intent simulation reverts, retain non-sensitive diagnostics and decode the selector using the deployed ABI. Do not repeatedly broadcast or infer success from the action appearing in a list. Record operation ID, nonce/hash, successful receipt, claim/Transfer events and beneficiary balances before/after. Future tranches, unresolved appeals or unfinished exit mean the lifecycle remains open. --- # 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/9.-claim-and-settle.md?ask=&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.