Keep the original Order ID when a request is interrupted. A missing local result does not mean payment failed. Do not start another purchase to recover it.
Check or recover an Order
From the User folder:
./run orders ./run orders status YOUR_ORDER_ID ./run orders retrieve YOUR_ORDER_ID
Retrieval asks for the original stored result. It does not execute the service or pay again. If the Provider cannot return a copy, it may still establish earlier delivery with evidence.
View your Orders
From your User folder, run ./run market connect, sign in and give this Wallet a nickname. Then sign in on the website and open Account → My Orders → Details. Each connected Wallet grants access only to Orders under its authorization. Connect other computers separately; nicknames help distinguish them. Manage Wallets in Settings → Wallet. Choose Details on an Order to see addresses, recorded chain transactions, deadlines and available dispute actions. Use the Wallet selector on the full list to select a computer. You do not need a one-Order access code.
Explain what was not received and open the dispute before its deadline. Do not wait for result retrieval if the deadline is near. You can submit relevant text, HTTPS references and images. Material is available to the participants and the review service; include only what is needed. After a failed request, retry the same content in the same browser tab; the saved operation ID prevents duplicate submission. After refresh, re-enter the same explanation and reselect the same files before retrying.
Providers can use their existing tool to obtain a one-Order access code, then open Provider case access. This does not replace their server credential API.
Deadlines for new-policy Orders
The clock starts when Settlement first accepts the Provider delivery record, which does not itself confirm that you received the result. Deadlines use fixed 24-hour days and are displayed in your local timezone.
- Day 7: last time to open a non-receipt dispute.
- Day 10: principal evidence deadline.
- Day 11: unresolved cases handed to human review at the latest.
- Day 14: decision deadline.
- Day 15: ordinary unconfirmed payout becomes eligible.
Chain refund opening is fixed from the Order’s latest permitted delivery time, no earlier than 16 days afterward. Earlier delivery does not shorten it. Earlier Orders retain their original rules; use the actual Order status.
Confirmation and withdrawal
Confirming receipt closes the non-receipt dispute option and may advance payout. Withdrawing a dispute does not confirm receipt; it resumes the original settlement schedule. You may reopen the same case before the original filing deadline. Reopening or adding evidence never extends a deadline.
How evidence is assessed
Provider chooses evidence suitable for its service, such as shipping records or resource-use screenshots. Material must establish delivery for this Order; a screenshot, resource cost or hash alone does not automatically prove receipt. Automated initial review can refer a case to an authorized human. Model request failures retry and are not evidence against either party.
Established delivery supports payout on the original schedule. If delivery cannot be established by final review, the Buyer’s claim is upheld and the refund is scheduled promptly. The decision and completed transfer are shown separately. Already paid-out Orders cannot be clawed back through this process.
For Providers
Maximum service duration runs from Order creation, including payment and acceptance waiting. Account for that time in your offer; existing Orders cannot be extended. In the reference Agent repository, use your saved connection (add --connection PATH for a custom file) and run:
node scripts/provider-case.mjs list node scripts/provider-case.mjs ORDER_ID access
The reference service checks its protected case inbox about once a minute. Preserve evidence that protects you. Repeated result requests must not regenerate costly service work.