Documentation.
Start where it costs you nothing: check one of our proofs before you take anything else here on trust.
Quickstart
Verify a proof
Post an attestation and the result it covers. You get back whether it is valid and which anchored root it was checked against. No account, no licence, no key.
What a pass means. The computation ran as specified and the evidence is unaltered. It does not mean the output was useful, correct for your purpose, or accepted by a buyer. Proof of execution, never proof of quality.
[CONFIRM: request and response example, once the endpoint is final. We are not shipping a sample that might be wrong.]
Resolve an identity
Ask whether an address belongs to a licence-backed root identity and who provably owns it. Also open, also free.
Read the answer carefully. It establishes sameness — that addresses share an owner. It does not establish that two parties are unrelated. If your design assumes independent counterparties, that assumption is still yours to discharge.
Fetch an inclusion proof
Retrieve the proof, the anchored root and the history around it. Measurements are captured sub-second and folded into roots every 6 to 30 seconds.
What is anchored is node availability and utilisation — not the energy or cost of a specific job. Capture is internal to the node, so anchoring makes the series tamper-evident, not the reporter disinterested.
Submit a paid job
One call returns the result and the attestation, and payment settles against the attestation rather than a promise. Requires a licence-backed identity.
Settlement is final. There is no acceptance step, no dispute process and no refund. Design for that before your first call, not after it.
Machine-readable
Four files, and they are the real documentation.
llms.txt
The whole proposition in prose, including every limit. Where this site and that file disagree, that file is correct.
OpenAPI
Every callable endpoint, typed. The limits are encoded as constant response fields, so a client cannot skim past them.
MCP server
Four tools. Three read-only and open; the settlement tool is marked destructive because it spends money and cannot be reversed.
Not documented yet
Listing this is cheaper for both of us than letting you find out at integration time.
- Authentication. Job submission needs a signature from a licence-backed identity. The scheme, canonical signing string and replay protection are not published yet, so do not guess at them.
- Rate limits. Not published.
- Acquiring an identity. A licence transaction, not an API call. Talk to us.
- Replayable execution. Pinning model weights, runtime version, sampling settings and seeds is not covered. If you need bit-identical re-runs, we cannot give you that today.
- Per-job resource receipts. What is measured is node availability, not the cost of your specific job.
- Reputation. In development. Do not plan against it.