# Supplier quotes: exact arithmetic and appropriate clarification

Status: real API trials recorded on 11 September 2026 (Brisbane); provisional report awaiting human review and the baseline decision. Nothing has been published.

## Question and result

Can Grok apply explicit supplier-pack, price, discount and clarification rules to structured input?

2 of 3 pipeline attempts returned completed model output. Those outputs matched 20/20 case references. Across all attempted pipeline cases, 20/30 returned a correct answer; missing outputs remain failures of the pipeline and are not scored as model answer errors. All completed outputs matched the exact prompt and finished normally.

The recovered outputs quoted all five valid requests with the expected pack counts and cent totals, including the half-cent rounding case. All five unquotable requests were flagged for clarification. Q09 lacked a SKU and used an ambiguous product name; the clarification reasons were brief but did not invent a matching product.

## Method and evidence

Fixed [inputs](../quote-accuracy/inputs.json), [prompt](../quote-accuracy/prompt.txt), [authored reference](../quote-accuracy/expected.json), [manifest](../quote-accuracy/manifest.json) and [protocol](../quote-accuracy/PROTOCOL.md) were prepared before runs. The [dated run-plan amendment](../API-RUN-PLAN-2026-09-11.md) records the missing human baseline and infrastructure repair. Raw records were exported directly from the private dashboard’s D1 database; corresponding .score.json files and [summary](../results/2026-09-11/summary.json) are retained.

Each run requested x-ai/grok-4.3 through OpenRouter, temperature 0, low reasoning, maximum 4,000 output tokens, JSON output, no web/X search and no automatic fallback. Each trial used one fresh request with the same prompt and no answer key. Inspect the raw record for reported model/provider, generation ID, usage and settings. The trials repeat fixed cases and are not an independent sample of business documents.

| Attempt | Raw record | Outcome | Exact cases | Model latency | Reported API cost |
|---|---|---|---|---|---|
| 1 | [150053e6](../results/2026-09-11/150053e6-437d-4621-9fef-abacc078c14b.json) | uncertain | 0/10 (no output) | unknown | unconfirmed |
| 2 | [c010d172](../results/2026-09-11/c010d172-4207-41dc-bfa2-55912c13a98f.json) | completed | 10/10 | 11.715 s | US$0.00534215 |
| 3 | [b93ef0e2](../results/2026-09-11/b93ef0e2-90d6-4ce9-a4d1-683dcf5d767a.json) | completed | 10/10 | 10.527 s | US$0.00356815 |

## Time and cost

Completed model-request times ranged from 10.527–11.715 seconds. Provider-reported costs total US$0.00891030. A further US$0.10 remains reserved with no confirmed invoice cost. Provider reporting is not invoice reconciliation; the app rounds allocations upward to microdollars.

Human setup, checking, correction and baseline times were not measured. Hosting, development effort and subscription overhead have not been allocated. This is not total delivery cost, a speedup result or a profit calculation. Revenue and attributable customer interest are unmeasured.

## Limitations and decision

Only two model outputs were recovered. The first pipeline attempt failed before a usable answer. The three-successful-trial criterion was not met. The input was already structured JSON; no PDFs, OCR, real supplier updates, taxes or customer documents were tested. Deterministic arithmetic can implement these rules, so this study does not establish that a language model is needed.

The assistant reviewed references and outputs; independent human checking is still pending. The current evidence supports only the observed behavior on these fixtures. Do not infer a population-level accuracy guarantee from repeated tiny examples.

A paid assessment would need to test a customer’s permitted supplier format and checking process. Do not sell autonomous quoting or claim that these synthetic cases validate a real installation.

## Sources and reproduction

[OpenRouter model metadata](https://openrouter.ai/api/v1/models/x-ai/grok-4.3/endpoints) supplies workflow/model context, not evidence for our trial scores or commercial demand. [OpenRouter usage accounting](https://openrouter.ai/docs/cookbook/administration/usage-accounting) describes the reported cost field. Our findings come from the linked raw run records.

From the project directory, run `node scripts/score-workflow-trial.mjs quote-accuracy experiments/results/2026-09-11/RUN-ID.json` for each record. Use `node scripts/score-pilot-evidence.mjs` and `node scripts/build-pilot-reports.mjs` to regenerate scores and these reports without making provider calls.