vespermesh

Demonstration workflow

One document.
A complete buying process.

The demo tests whether an agent can choose a service within its budget and receive checked work before its credits are spent. Here is what actually happens.

  1. 01

    Define the conversion

    The buyer agent, within authority set by its human operator, selects our approved Word document and sets a maximum price and delivery time. This demo supports one fixed technical note, not file uploads. The buyer may be a script or a model-guided client.

  2. 02

    Compare and choose an offer

    The platform returns offers from its active demo supplier profiles. The buyer compares their price, supported features and delivery time, then selects an eligible offer. All these profiles are operated by the founder; they are not independent businesses.

  3. 03

    Simulated credits: reserve the budget

    Before accepting the order, the platform checks the buyer’s credentials, remaining spending authority and simulated balance. It reserves the selected offer’s price. The agent cannot raise its own limit, and reserved credits have not yet been spent.

  4. 04

    Convert the document

    The hosted worker runs Pandoc and a LaTeX compiler using the selected profile’s processing recipe. It produces a source ZIP, compiled PDF and conversion report. Processing continues without the buyer’s browser being open.

  5. 05

    Check the delivered files

    A separate worker job recompiles the delivered LaTeX and checks the fixed document’s expected text, equations, table, figures and references. These checks apply to this document only. The verifier is operated by Vespermesh, not an independent reviewer.

  6. 06

    Simulated settlement: retrieve the result

    If the delivery passes, the platform spends the reserved simulated credits and creates a receipt linking the selected offer, delivered files, verification and ledger entries. The buyer can then download the files. Credits have no monetary value; no real payment occurs.

Access and availability

Agent discovery coming soon — registry and fixtures unlock when the demo window is on. OpenAPI and JSON Schemas are readable on the review preview. Live registry and fixture discovery are disabled on the review preview (503 DEMO_UNAVAILABLE); the operator supplies an enabled service origin for a demo. Simulated purchasing requires a founder-issued credential and spending authority. Processing runs during controlled test windows and may be paused between them. Downloads expire after the offer’s seven-day retention period.