Service terms

1. Case submission and payment timing

Submitting an unpaid case does not create a client relationship, reserve a delivery window, or require payment. Browser card checkout is not currently live. An accepted repair or migration case explicitly selects either a $1,000 USD Stripe card payment or exactly 1,000.000000 native USDC on Base Mainnet. Fresh-host hardening payment is exactly 1,000.000000 native USDC on Base Mainnet only; card payment is unavailable. A case-bound checkout may be issued only after Agent Rescue Desk accepts the case for technical fit and both sides accept the written scope. There is no generic wallet address or pre-fit browser payment route. A marketplace listing expressly marked as a direct paid rescue is governed by that listing and Section 2 below.

2A. Automated PDF products

The Agent-Citable PDF Extraction Pack is a one-time, settlement-gated automated extraction service for a bounded batch of authorized, non-sensitive, text-layer PDFs. The Private PDF Citation Kit is a one-time, settlement-gated delivery of a self-contained HTML tool. The kit is licensed to the purchaser for internal use only and may not be redistributed, sublicensed, published, or resold. PDF.js remains available under its Apache-2.0 license. The automated products are separate from an accepted rescue engagement and do not receive the 12-hour delivery promise.

The kit's browser-wallet route creates a random private purchase URL and requests exactly 39 USDC on Base. A successfully settled URL becomes a bearer entitlement that can reopen the same licensed download without a second charge. The purchaser must keep that URL confidential. Anyone with the complete URL may be able to retrieve the product. The optional fit-review link inside the kit does not purchase or begin a rescue; it opens the ordinary secret-free review process, and rescue payment is requested only after fit and exact written scope acceptance.

The buyer must be authorized to process every submitted file and must not submit passwords, credentials, private keys, regulated data, payment-card data, health data, or unrelated customer records. These products do not perform OCR, password bypass, document modification, legal review, accessibility certification, or layout-fidelity certification. Exact-term checking covers extractable text only and is not proof of secure redaction. A paid automated response is the complete deliverable. The API rejects unsupported filter chains, high-expansion streams, oversized string tokens, and other invalid input with a non-success response; the x402 authorization is canceled before settlement. If settlement nevertheless succeeds but a service-side error prevents delivery of the paid response, the purchase is eligible for a refund of the affected automated-product fee.

2. Accepted scope and fee

An accepted rescue covers either one written, bounded agent workflow and its directly required tools or integrations, or the separately published one-host OpenClaw hardening trial. An accepted repair or migration case explicitly selects either a $1,000 USD Stripe card payment or exactly 1,000.000000 native USDC on Base Mainnet. Fresh-host hardening payment is exactly 1,000.000000 native USDC on Base Mainnet only; card payment is unavailable. Case-bound payment instructions are issued only after acceptance under Section 1. An accepted-case Base-USDC checkout requests exactly 1,000.000000 native USDC on Base Mainnet and remains pending until settlement and finality are independently verified. The exact written scope for a fresh-host hardening trial must incorporate immutable acceptance matrix v1 and its SHA-256 b306dc0a81e8dcea0fba14f266c2d031453ed50b9d540dbe3e6ec6c52efaba48, including the selected alternatives, accepted non-critical warnings, evidence owners, and pass criteria. For a direct marketplace purchase, the marketplace listing and the buyer's submitted scope form the written offer and acceptance, and the paid response opens a private case. A direct prepayment may be refunded if Agent Rescue Desk cannot accept the submitted scope. One payer wallet is bound to one direct rescue case so retry-generated IDs and authorizations cannot create a second charge. Checkout issuance or payment alone does not start work or the delivery window; they begin only after cleared payment, accepted written scope, the agreed sanitized materials and temporary access are ready, and the applicable repair, migration, or fresh-host hardening readiness evidence in Section 3 is complete.

3. Delivery window

The 12-hour window begins when payment has cleared, the written scope is accepted, the agreed sanitized materials and access are ready, and either the failure is reproducible for a repair or the source behavior is reproducible and the agreed target outcome is testable for a migration. For the published fresh-host hardening trial, it begins only when the buyer-owned fresh pre-production Ubuntu 24.04 host, tested provider-console recovery path and a usable snapshot or equivalent rollback, agreed temporary access and change authorization, required materials, and exact testable acceptance criteria frozen to acceptance matrix v1 and its recorded SHA-256 are ready. Repair and migration windows pause while required access, information, approval, or a customer-controlled system is unavailable. The fresh-host hardening window pauses only for a documented customer-controlled loss of required access, information, approval, or host availability. A third-party outage does not pause the active hardening window or void its outcome guarantee. Delivery is complete when the agreed verified repair or migration path, or an actionable root-cause and remediation package, is provided. Hardening completion requires all five runtime-required deliverables: a redacted evidence report, a repeatable full runbook, a short screen recording, an exact version inventory, and the working hardened accepted host. Separate tested provider-console recovery proof and usable snapshot or equivalent rollback proof are also required. A diagnostic or remediation plan is not a substitute.

4. Customer responsibilities

• You must be authorized to request work on every included system.
• Provide lawful, accurate information and temporary, least-privilege access.
• Maintain backups and review production-impacting changes.
• Do not submit regulated data, payment-card data, passwords, private keys, or long-lived tokens through the public form.

5. Safety and exclusions

The service will not bypass access controls, CAPTCHAs, rate limits, security protections, platform policies, or third-party authorization. Destructive or irreversible production changes require explicit customer approval. Third-party outages and platform limitations are outside the desk's control, but they do not pause or void the fresh-host hardening outcome guarantee.

6. 12-hour outcome guarantee and refunds

Any paid direct purchase declined before scope acceptance is refunded in full. If an accepted case produces neither an agreed verified repair or migration path nor an actionable root-cause and remediation package within the applicable delivery window, the service fee is also refunded. For an accepted fresh-host hardening trial, the full fee is refunded if the agreed working hardened host and required handoff are not delivered within the applicable active 12-hour window. Only the documented customer-controlled hardening blockers described in Section 3 pause that window. A third-party outage remains active time; if it prevents complete hardening delivery by the active deadline, the full-refund obligation still applies.

For a missed fresh-host hardening deadline, Agent Rescue Desk initiates a refund of exactly 1,000.000000 native USDC on Base Mainnet to the original payer independently verified from the case-bound cleared settlement within two hours after the missed active deadline. Agent Rescue Desk pays the refund gas without reducing the 1,000.000000 native USDC returned. The private case receives the refund transaction hash and network-finality evidence. Base congestion, reorganization, or another network-finality delay after timely initiation may delay confirmation, but does not cancel, reduce, or replace the refund obligation. A diagnosis, remediation plan, or advisory package is not an alternate hardening deliverable.

For repair and migration engagements, the delivery-window promise does not apply when delivery is blocked by missing customer access, inaccurate information, expanded scope, a third-party outage, a payment dispute or partial refund, or a customer decision to stop the work. This repair-and-migration rule does not narrow the separate fresh-host hardening guarantee above.

7. Agency overflow engagements

When an agency submits and pays for a case on behalf of its client, the agency remains the customer and must be authorized to provide the relevant materials and access. Agent Rescue Desk will not solicit the end client, publish the engagement as a case study, or expand the work without the agency's written agreement. The technical handoff may be supplied without Agent Rescue Desk branding.

8. Ownership and confidentiality

You retain ownership of pre-existing code, data, and systems. After full payment, you own case-specific code changes and documentation delivered for your system. Each side retains its pre-existing tools, methods, and general knowledge. Case information is used only to evaluate and deliver the request, comply with law, and protect the service.

9. Warranty and liability

Except for the delivery promise above, the service is provided as-is without a guarantee of uninterrupted future operation. To the extent permitted by law, total liability for a case is limited to the fee paid, and neither side is liable for indirect or consequential damages.

10. Changes and governing agreement

Any case-specific written scope, security requirement, or signed agreement controls over conflicting general language here. Material changes apply only to later submissions unless both sides agree otherwise.