Send a calculation. Get a result your software can inspect.

Request body

{"expression":"1/3 + 5/6"}

Captured development success response

{"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"}}}

Python standard library: one request

import http.client
import json
import os
import ssl

body = '{"expression":"1/3 + 5/6"}'
connection = http.client.HTTPSConnection(
    "api.sumwisecalc.com", 443, timeout=30,
    context=ssl.create_default_context(),
)
try:
    connection.request("POST", "/v1/evaluate", body=body.encode("utf-8"),
        headers={"Authorization": "Bearer " + os.environ["SUMWISE_API_KEY"],
                 "Content-Type": "application/json"})
    response = connection.getresponse()
    if 300 <= response.status < 400:
        raise RuntimeError("Redirect refused; check the agreed endpoint")
    raw = response.read(65537)
    if len(raw) > 65536:
        raise RuntimeError("Response exceeded this example's safety bound")
    try:
        payload = json.loads(raw)
    except (ValueError, UnicodeError):
        raise RuntimeError("Non-JSON response; do not retry automatically") from None
    if response.status == 200 and payload.get("ok") is True:
        result = payload["result"]
        print(result["type"], result["exactness"], result["text"], result["value"])
    else:
        print("Request refused:", response.status, payload.get("code", "unknown"))
        raise SystemExit(1)
finally:
    connection.close()

Set SUMWISE_API_KEY securely in your server/workstation environment. The example uses verified HTTPS, a bounded timeout, no redirect following and no automatic retry. The response-read bound is a client safety choice. It prints this synthetic calculation locally; never put keys in browser code or logs.

A lost response does not prove nonexecution. There is no idempotency-key contract; a retry can be another attempt. Stop on network, timeout or problem responses and inspect the cause before making another request.

Attempts, allowances and privacy

Durably accepted attempts count toward the aligned rate window. Compute quota is provisionally reserved and settled/refunded under outcome rules; unresolved accepted work remains reserved. Billable success is distinct from net quota and from proof that a client received its response. Confirm the applicable profile and reset terms during onboarding; source descriptions are not new live-capacity guarantees.

Caller-retained evidence does not authorize server logging of raw calculations or credentials. The durable application/accounting boundary excludes expressions, raw request/result bodies, authorization headers, plaintext keys and worker diagnostics; it does not promise absence from every OS/provider log or transient memory.