Put procurement expertise
into your workflow.

01 · PREPARE

Start with the decision and its evidence.

1. Choose the outcome. The workbench currently offers eleven first-party services. Sixteen imported ProcureAI procedures are shown as held while commercial-use rights are verified. Transcript vs RFP evidence checks a supplier conversation; Finance business case explains supplied costs; a category service structures your MRO, indirect, software, hardware or telecom decision.
2. Complete the required fields. Keep requirement IDs, speaker names, timestamps, units, dates and currencies. Supply actual supplier evidence and an approved rubric where requested. URLs are references; these services do not fetch them.
3. Review the selected backend and payment state. For wallet checkout, create an ADA invoice without signing in, save its private receipt, pay with Lace, verify the transfer, and consent to external processing before running. An illustrative sample can be explored without sending your documents or creating a saved run.

02 · REVIEW

A deliverable with its limits visible.

A verified quote means the words occur in the supplied text. It does not verify the source's truth, interpretation, completeness or fulfillment. Read the limitations, resolve missing evidence and approve decisions through your normal procurement process.

Live runs save a summary, deliverable, findings, next actions and a delivery record. Signed-in teams can reopen organization runs in Your runs. Wallet buyers should save their private receipt and use it to retrieve the result, review and artifact. Keep the original source versions together with either receipt.

Download .md for a readable report. Download outcome JSON or choose JSON in Copy as to retrieve the saved successful artifact: its original outcome, run provenance, metadata-only trace and server SHA-256 digest travel together. Generated context is not primary evidence or human approval. A local example is clearly marked and cannot be handed to another service as a saved artifact. If retrieval fails, an explicitly labeled displayed snapshot can be saved without a server digest.

03 · COMPOSE

Available fixed routes through the work.

These recipes chain services in this application. A SmythOS deployment is a separately configured execution backend for a service: operators connect reviewed deployed agents or Studio exports, then buyers choose an allowed deployment. Connecting an export does not add a new recipe. Buyers cannot upload arbitrary executable workflows or define their own stage graph through this interface.

The workbench shows the resolved SmythOS deployment name and ID before a run. Expand the saved workflow trace afterwards to inspect reported response identities, response references, duration and any authenticated bridge runtime or export hash. An outer deployment identity does not prove its internal models or inference costs. Direct OpenRouter token counts and cost credits appear only when reported; credits are not presented as USD.

Each stage uses its own source requirements and saved run. Earlier generated analysis is passed as context, with its provenance; it does not become buyer approval or primary evidence. The bid review still needs your approved rubric.

Set a maximum prepaid invoice value before submitting. Completed stages retain their charge if a later stage fails. A failed stage restores any reserved service credit. After a connection failure, inspect the recorded runs and resubmit the unchanged workflow with the same key. A recorded failure is replayed. A fresh workflow request uses a new key, reruns every stage and needs new invoices for previously completed paid stages. There is no automatic background continuation or whole-workflow rollback.

04 · PURCHASE

Confirm the invoice before sending funds.

For a wallet-only purchase, choose a service in the workbench and create an ADA invoice. Save the private receipt before paying. Lace can connect, check Cardano mainnet, prepare the exact transfer and submit it after you approve it in your wallet. Another mainnet wallet can pay the displayed address. Verify the transfer hash, run the paid agent, and use the receipt to retrieve its outcome and delivery review. The wallet API follows the same steps under /api/v1/agent-services/wallet/invoices; it needs no organization API key. The transaction hash alone cannot unlock the result.

Payment methods become available when the operator has configured receiving wallets, verification and durable storage. Invoice creation also checks the selected service's readiness. The displayed list price is in USD; a purchase creates a time-limited cryptocurrency quote.

Signed-in organization billing: the following USDT or ADA invoice steps use organization access. Wallet-only buyers use the ADA flow above and keep their private receipt.

1. Create an invoice for the chosen service. Select USDT on Ethereum mainnet ERC-20 or ADA on Cardano mainnet. Check the receiving address, exact amount and 30-minute expiry. Transaction fees are additional.
2. Send the exact displayed amount. Its fractional part identifies the invoice. Lace checkout prepares the payment for your wallet approval; manual transfers must match the address, amount, network and expiry. Send once, then submit the transaction hash for verification. Never share a wallet seed phrase or private key.
3. Wait for confirmed payment. USDT requires Ethereum finalized status plus 12 confirmations. ADA requires 15 canonical block confirmations; settlement remains probabilistic. A submitted hash or pending transaction is not confirmed payment.
4. Use the paid invoice for its service. A successful run consumes it. If the run fails, refresh the invoice to check its restored credit before a fresh attempt.

Restored credit is permission to retry the service, not an automatic cash refund. Wrong amounts, wrong networks and late transfers require operator reconciliation. A transfer mined before expiry can still be verified afterwards; do not send a new transfer to an expired invoice. Preserve invoice IDs and receipts. Each paid workflow stage needs its own matching invoice.

This implementation collects payments for services. An independent agent marketplace with operator payouts, revenue sharing and automatic settlement is a separate capability.

05 · DATA & CAPACITY

Know where your sources go.

Consent applies to the selected provider and workflow. A live run sends source text to OpenRouter or the configured SmythOS endpoint; optional remote KNWLER extraction sends text to its worker and inference provider. Use documents your organization authorizes for that processing and check provider retention and contractual terms.

The direct OpenRouter route is fixed to openrouter/free and uses the operator's server-held key with provider data collection denied. Available models and free capacity can change; that setting does not promise zero retention, a processing region or an SLA. The service does not rotate keys to avoid limits or silently switch to a paid model. SmythOS exports can have their own model, tool and storage policies.

Live runs persist inputs, outcomes and traces on the server. Wallet purchases are accessed with a private receipt; signed-in organization runs use scoped history. There is no automatic retention deletion in this release. Agree retention and removal with the operator before supplying sensitive material. Local extraction and local knowledge import/query are stateless and do not send text to inference.

Check current backend status before submitting. Configuration and a successful storage probe do not prove provider reachability or available inference capacity. Setup-needed services can be explored through the catalogue and sample; a live outcome requires configured credentials and working providers.

06 · OPERATORS

Connect a backend without exposing credentials.

Inference and payment credentials belong in the production server environment at /opt/aiprocurement-club/.env, never in this browser, a customer API request, a prompt or Git. Update that file through your private operator process, then recreate the affected Compose services with the normal deployment procedure.

1. Enable direct inference. Set OPENROUTER_API_KEY. The service uses openrouter/free, makes up to four outer calls per run, and does not silently switch to a paid model. Free capacity is shared and provider availability changes; configuration is not a service-level guarantee.
2. Connect SmythOS if needed. Set SMYTHOS_API_KEY, AGENT_SERVICES_SMYTHOS_ALLOWED_HOSTS and a reviewed server-owned AGENT_SERVICES_SMYTHOS_WORKFLOWS_JSON mapping. Only explicitly mapped, allowlisted deployments become selectable. A visible workflow definition is not proof of a live deployment.
3. Add KNWLER extraction optionally. Deploy the separate worker, then set KNWLER_WORKER_URL, KNWLER_WORKER_TOKEN and KNWLER_ALLOWED_HOSTS. This adds source-tagged graph extraction; it does not supply current market data or a prebuilt procurement corpus.
4. Configure the payment rail separately. Keep AGENT_SERVICES_REQUIRE_PAYMENT=1. USDT requires PAYMENT_USDT_ETH_ADDRESS and PAYMENT_ETH_RPC_URL; ordinary ADA requires PAYMENT_ADA_ADDRESS and a Cardano-mainnet PAYMENT_BLOCKFROST_KEY. Cardano x402 additionally requires AGENT_SERVICES_X402_ENABLED=1, X402_PUBLIC_ORIGIN, X402_FACILITATOR_URL and X402_FACILITATOR_ALLOWED_HOSTS for a reviewed facilitator.

After the operator redeploys, check public service readiness. Then run the read-only activation doctor with node scripts/agent-services/activation-doctor.mjs --origin https://aiprocurement.club. Report-only success confirms public contracts, not live inference, payment, a funded pilot or revenue; strict activation also needs an existing paid invoice and its successful matching run.

Never test launch readiness by disabling payment enforcement or sending real buyer documents. Start with a synthetic case, verify the chosen provider and privacy terms, then complete a deliberately authorized pilot through the normal invoice and run flow.

07 · INTEGRATE

Let any paying AI agent call a specialist.

Discover listed services through the public catalogue, tool manifest or OpenAPI contract. Each tool's walletInvocation gives its keyless invoice, verify, run, result, review and artifact contract; the separate invocation is for organization keys. Any HTTPS client that can pay a Cardano mainnet invoice can use the wallet flow when checkout is configured. An organization API key is not required. Keep the returned receipt token private; it is the credential for that purchase and its result.

The illustrative RFP request below shows the three write steps. Replace the sample inputs, save the invoice receipt before payment, wait for chain verification, and obtain explicit authorization to share source text with OpenRouter and its model provider.

POST /api/v1/agent-services/wallet/invoices
Content-Type: application/json

{
  "agentId": "rfp-evidence"
}

Save receiptToken from this response. Pay the invoice's exact ADA amount.

POST /api/v1/agent-services/wallet/invoices/:id/verify
X-Wallet-Receipt: <private-receipt-token>
Content-Type: application/json

{ "txHash": "<cardano-mainnet-transaction-hash>" }

After status is paid:
POST /api/v1/agent-services/wallet/invoices/:id/run
X-Wallet-Receipt: <private-receipt-token>
Content-Type: application/json

{
  "inputs": {
    "rfp": "R-1: Hardware support is required for 36 months.",
    "transcript": "00:12 Alex: We offer hardware support for 24 months."
  },
  "consentExternalProcessing": true
}

Poll GET /api/v1/agent-services/wallet/invoices/:id/run until the run succeeds or fails. Then retrieve /review for the high-level delivery check and /artifact for the saved result and digest. Send X-Wallet-Receipt on every invoice request after creation. Never put it in a URL, public prompt or log. Reconcile an uncertain wallet submission before attempting another payment.

08 · OPERATIONS

Follow the work and its accounting.

Open agent operations after sign-in to see your organization's saved activity, service earnings, confirmed transfers and prepaid credit. Choose a UTC window, inspect a bounded run timeline, pause refresh or export the displayed snapshot.

A confirmed deposit becomes earned service revenue when its matching paid run succeeds. Available credit and running reservations remain separate. USDT and ADA amounts retain their exact historical units; they are not current wallet balances or agent payouts.

Model identities, token counts and OpenRouter cost credits appear when actually reported. Missing values stay unknown, and an outer workflow response does not reveal every internal inference call. The USD 100,000 twelve-month target and price scenarios are planning assumptions.

09 · CATALOGUE

Eleven services, one workbench.

Eleven first-party procurement services cover central buyer outcomes and categories, including transcript evidence, finance, negotiation, knowledge, MRO, indirect materials, IT software, hardware and telecom.

Sixteen imported ProcureAI procedures remain held from paid app access while commercial-use rights are verified. Review their current terms and original materials at procureai.tech.