Error Codes

Current implementation, supported use and explicit qualification limits.

Experimental Feature

This feature is experimental and may change significantly in future versions.

Current release status

Public document hashing and exact integer aggregation are live with signed results. Native consensus, mining, issuance, COMPUTE payments and rewards are inactive. Independent operation is not yet demonstrated.

Read the actual response

Health/status availability is not job verification.400/422 indicates an invalid request,413 an oversized body,429 rate limiting, and 502/503 unavailable/unconfigured upstreams. A pending job is not a successful result.

Failure behaviour

No failed request is replaced with a fake receipt, default healthy validator count, zero volume or synthetic confidence score. Check job_id, actual status, signatures and output; retain explicit errors.

Retry safely

For public read-only lookups use bounded retries/Refresh result. Never automatically retry a future financial transaction or refund a reorged payout without reconciliation and separate consent.

The real public API contract

The supported integration is HTTPS and explicit public data. There is no invented SDK package or arbitrary-code runtime behind these examples.

BoundaryImplementation / evidenceMeaning
GET /api/public-work/healthNo bodyGateway and pinned-policy observation, not worker uptime
POST /api/public-work/jobskind, input, public_data_consent:trueAccepts registered bounded public work
GET /api/public-work/jobs/:idActual returned job_idPending, failure or verified signed result
Unavailable / invalid requestActual HTTP errorNever a fake receipt or healthy fallback

Practical procedure

  1. 1POST a non-confidential input and inspect the actual response.
  2. 2Retain job_id; poll with a bounded retry policy if pending.
  3. 3Treat verified status as a claim to check, not a proof by itself.
  4. 4Download complete evidence and verify it against the known policy.
Technical reference · scope is explicit
curl --fail --show-error https://www.compute-net.org/api/public-work/jobs \
 -H 'Content-Type: application/json' \
 --data '{"kind":"integer-aggregate","input":{"values":["12","-3"]},"public_data_consent":true}'
# Then GET /api/public-work/jobs/YOUR_ACTUAL_JOB_ID
# Preserve pending/errors; verify the final signed result.

Limits and failure cases

  • Never submit keys, credentials, personal data or confidential inputs.
  • Document input is bounded to 64 KiB; vectors to 1,000 canonical integer strings, each ≤32 characters.
  • This API does not authorize or perform COMPUTE settlement.