Inspectable synthetic examples
See what one supported expression returns before deciding whether the API fits.
Native DEVELOPMENT execution, captured October 6, 2026. These are not fresh live-endpoint or installed-worker tests. The actual development identity is preserved. A result printed as an integer can still be approximate.
Download the four exchanges (JSON) · Inspect source/build/binary identifiers (JSON)
{"expression":"1/10 + 2/10"}{"ok":true,"api_version":"v1","operation":"evaluate","engine_version":"0.1.0-dev.1+untrusted.local","result":{"type":"rational","text":"3/10","exactness":"exact","value":{"numerator":"3","denominator":"10"}}}{"expression":"1/3 + 5/6"}{"ok":true,"api_version":"v1","operation":"evaluate","engine_version":"0.1.0-dev.1+untrusted.local","result":{"type":"rational","text":"7/6","exactness":"exact","value":{"numerator":"7","denominator":"6"}}}{"expression":"0.1+0.2"}{"ok":true,"api_version":"v1","operation":"evaluate","engine_version":"0.1.0-dev.1+untrusted.local","result":{"type":"real","text":"0.30000000000000004","exactness":"approximate","value":"0.30000000000000004"}}{"expression":"amount","inputs":{"amount":"100.05"}}{"type":"https://sumwisecalc.com/compute/problems/v1/evaluate/invalid-request","title":"Invalid request","status":422,"detail":"The request body does not match the Evaluate request contract.","code":"invalid_request","api_version":"v1","operation":"evaluate"}For rational/exact, the numerator and denominator are canonical strings representing a reduced fraction. For real/approximate, value is the same binary64-formatted string as text. Preserve the structured values and exactness field; do not silently coerce exact fractions into floating-point numbers.
The named-input object is rejected. The request supports one expression string, not a named binding map. Integer/fraction arithmetic can remain exact; ordinary decimal/scientific literals carry approximate provenance. Mixed min/max retains the selected operand's family. There is no exact decimal-string, named-rounding, fixed-scale money, immutable-rule or monetary-receipt feature.
The JSON provenance binds parent source, tested source bytes, the later test-only commit and executable hash. This x64 Release Development artifact identifies itself as 0.1.0-dev.1+untrusted.local. It was built from the parent plus the identical tested delta before that commit; it was not rebuilt or relabeled TrustedGit. The identifier alone is not a unique binary identity. Implementation source remains private.
Finite input, kernel and result limits still apply. These examples do not establish full service startup, installed reliability, capacity, an availability promise or cross-platform equality.
Check supported scope, then confirm fit and terms. Access is separately provisioned after agreement/payment; a Desktop license or connector installation does not activate it. Use the single-request HTTP quickstart only after receiving access.
Use synthetic/non-sensitive examples for fit checking. A lost response does not prove nonexecution; there is no idempotency-key contract and retrying can consume allowance. Caller-retained evidence does not authorize raw calculation or credential logging on the server.