How it works

Choose a task#

Extract, Inspect and Summarize are three presets for the same text service and fixed demo quote. Each supplies its own input, output format and prepared result. Select a preset to load its complete example, or edit the input to create a custom demo request.

A preset returns its prepared result only when the input matches that preset. An edited request is labeled Custom demo and returns a local preview rather than an inferred answer. Custom text is not submitted to an external model in this deployment.

Review the quote#

The quote separates task cost from platform service fee and shows the complete USDC total. A live quote must bind the input hash, service, provider, network, mint, recipient, token program, expiration and idempotency key.

The server must reject an expired quote or a budget below the total. The current build blocks live quoting until the required server adapter and configuration are supplied. Demo quote amounts are estimates; actual demo payment is 0 USDC.

Pay and execute#

A connected Solana wallet identifies the buyer. Connection alone does not authorize a payment. A live integration must present the exact transaction for the buyer to review and approve.

The server verifies a successful finalized transaction against the persisted quote before starting the supplier job, including its token program and quote correlation. Duplicate requests must return the same job rather than charge or execute again.

Task history and results#

Open a Job ID to inspect its status, input, quote and receipt. The selected Job is the source for the task details, result, timeline and illustrative rack focus. The Result action opens a preview with copy and download controls. Receipt and result downloads carry the same Job ID.

Demo history is stored under a versioned browser-local key and survives refresh. A clear-history confirmation removes demo jobs only. Formal jobs must be read from an authenticated durable server store and are never saved as demo records. That live store is not connected in this deployment.

Execution timeline and replay#

The Job timeline follows Request → Budget check → Execution → Result → Receipt. Browser demo jobs record the events when they occur, together with the accepted quote and the budget limit at that time. Homepage sample jobs contain labeled illustrative event records.

Replay reads these saved events and changes the timeline highlight and illustrative rack focus. It does not create a quote, execute a request or trigger payment. Replay animation duration is separate from the recorded execution elapsed time.

Get the result and receipt#

The provider response determines queued, running, completed or failed status. The receipt records what was requested, the observed usage and where the output can be fetched. A live completed label may only follow a real provider response. Demo completed is a separate, explicitly local state.