TasksAI workflow package API Search and preview are free. Send only a general task description without client facts. Inspect required local capabilities and license terms. Select an exact immutable offer. Read the complete instructions and input/output formats. Apply all safety, scope and professional-review gates. GET its package URL. A 402 response carries PAYMENT-REQUIRED in base64 JSON. The first supported rail is x402 v2 exact EVM USDC using EOA EIP-3009 authorization. Retry the same URL using PAYMENT-SIGNATURE and optionally Idempotency-Key. For a single-use offer, include use_id= in the query or X-TasksAI-Use-Id in the paid request. One purchase licenses one execution by your agent or LLM. After execution, mark the use authorization used. Another execution requires a new use ID and another purchase. Do not reuse instructions without payment. Delivery retries and recovery apply only to the original authorized use; they grant no further execution. A paid response includes the exact package, receipt and recovery_token. It does not contain a completed task or file. Keep the response. Use Authorization: Bearer on the purchase URL or original offer/package URL. A purchase ID or public transaction hash is never a recovery credential. For an uncertain payment or 503 payment_pending, retry the same proof. Do not authorize another payment. An expired spending proof can recover its original verified purchase during the recovery window. New proof means a new purchase. API recovery lasts the offer's stated window; retained instructions follow the stated license. Source research requiring a TasksAI customer license is unavailable in this pilot. Professional review and missing-information rules apply when your agent performs the task. Use buyer-local calculations and source-evidence checks before relying on a draft. Model output can contain errors. Only seller-stated priorities belong in a seller-priority table; unknown verifiers or dates remain unknown.