# Interface Consistency Check v1 — service terms

**Owner-approved launch: October 10, 2026.** The private paid task API is deployed with checkout enabled. Live funded fulfillment remains unverified for both payment methods; authenticated CDP seller access, settlement and billing remain unverified. Enabled checkout is not evidence of a successful paid fulfillment.

Each purchase covers one supplied snapshot of public llms.txt contents, OpenAPI JSON and product-offer metadata. The fixed selected prices are USD 1.00 (100 cents) through Stripe MPP or 0.10 USDC (100000 atomic units) through x402 on Base. Choose one method. No subscription, human assistance, gift entitlement or Manifest Kit purchase is included. Any buyer-provider fees are governed by the buyer's provider; the merchant does not promise a zero-fee issuer or wallet.

The service validates the submission and prepares/persists a deterministic report before requesting payment. Unsupported, unprocessable or oversized requests are rejected before financial dispatch. Documentation inconsistencies are successful findings and remain part of the purchased result. The report checks selected rules only; it is not full OpenAPI validation, live endpoint verification, a security certification, legal advice or a guarantee that an agent will discover or use an interface. Suggested corrections require caller review. No documents are fetched, model calls purchased or source files edited.

The exact private report is released only after independently reconciled confirmation of the selected payment. A submitted payment, provider response, HTTP status, transaction hash or pending authorization alone does not establish confirmation. Uncertain payments remain preserved for reconciliation. The client and server must not submit another charge or settlement because a reply was lost or an idempotency key aged out. A payment in review is not authority to start a replacement job.

The **report-recovery period is 30 days beginning at payment confirmation**. The capability may retrieve the same saved report bytes during that period without another payment. At expiry the API stops returning the report; bounded maintenance deletes its bytes, which can lag during quota exhaustion. Keep your local verified copy. Unpaid reports expire after 24 hours. Unresolved attempted-payment reports and required reconciliation evidence remain until resolved, counting toward fixed storage bounds. Compact hashed order/recovery/payment audit markers remain to prevent reuse. Admission stops at capacity rather than discarding unresolved financial evidence.

Save the cryptographically random recovery capability before preparation/payment and protect it like an access credential. The seller stores its hash, not the raw capability. Recovery can locate an original order even if the order-ID response was lost. The service provides no public order lookup and no replacement capability recovery. Do not email credentials, tokens, full payment headers or private reports. Losing the capability or disclosing it to another party can prevent secure recovery; save the report locally after verification.

Only public interface documents should be submitted. Raw submitted contents are discarded after preparation where feasible; the private result, input/report digests, exact purchase binding and sanitized payment state/receipt are stored. A result may disclose supplied field names, pointers or suggested values. Cloudflare processes connection data and hosts the private SQLite-backed Durable Object; Stripe, buyer issuers and x402 infrastructure process their own payment data. Base payment addresses and transfers are public on-chain. No raw card data, exported wallet key or payment credential is stored in public artifacts.

Fixed request, result, rate and storage limits are published in the API/offer. The service allocates at most 20000 SQL/alarm writes per UTC day and checks physical SQLite storage plus conservative payment-state reservations against a 768 MiB ceiling. Shared account limits can still affect availability. Capacity rejection stops new admission and first financial dispatch; it preserves existing attempted-payment evidence and the recovery period. A capacity or availability rejection grants no payment authority. No uptime or response-time guarantee is provided. Confirmed payment without an available retained report is a fulfillment exception: preserve the original order and sanitized receipt rather than charging again. The resolution route is [email Ben](mailto:buscheo@gmail.com) within seven days of noticing an exception, including only the order ID, report digest and a short description. Never email a capability, token, full payment credential or private report. Ben will manually review the confirmed payment and fulfillment evidence, attempt to restore the originally purchased report where feasible, and consider a refund when confirmed paid fulfillment cannot be restored within its retained period. This is a manual review policy, not an automatic refund or response-time guarantee. Any refund requires a separately authorized merchant action through the original payment method where supported; this API implements no automatic refund or cancellation charge.

AI agents act under their owner's authority. Reading discovery, preparing a report or retrieving a quote does not authorize spending. The owner must approve the exact purchase and payment method under their own policy. User-Agent strings confer no identity or authority. Support Ben gifts remain voluntary personal support with no deliverable, service, access or priority entitlement, under a separate hosted checkout and provider terms.