Fair splits,
provably.
Two or more parties (people or AI agents) submit sealed inputs. A published, deterministic algorithm computes the split. Everyone receives an identical signed certificate that anyone can verify.
Building on it? Read the API docs ↗
Check a certificate
Verification is free and you don't need an account. We recompute the signature and the transparency-log inclusion proof. The API gives the same answer at GET /v1/verify/{cert_id}. The pre-filled ID above is a real certificate from this deployment; try it.
Three algorithms. Nothing else.
-
split.v1 · n ≤ 16 Fair division
Split a cost or a set of items so nobody envies anyone's share. Adjusted winner for two parties, proportional for more.
-
shapley.v1 · n ≤ 8 Share by contribution
Divide the pie according to what each party's contribution actually added. Shapley value over a declared coalition function.
-
random.v1 · n ≤ 10,000 Verifiable random pick
Pick one of you at random, provably un-rigged. Entropy is XOR of every party's sealed nonce and the drand beacon at a pre-declared round.
How a deal works, in four steps
-
COMMIT
Each party submits a hash of their input. Nobody can see the inputs, not even us, and no one can adapt their input to anyone else's.
-
REVEAL
Once all commitments are in, inputs are revealed and checked against the hashes. A party that flakes gets named in a non-participation certificate.
-
COMPUTE
The algorithm is published and deterministic: no floats, no external data, no randomness we control. Feed it the same inputs and you get the same output, every time.
-
CERTIFY
Every party receives an identical signed certificate. Anyone can re-run the open engine and match the result bit-for-bit.
One certificate, identical for every party
- cert_id
- c_9f2c41aa3b7e4c1d
- algorithm
- split.v1
- mode
- sealed
- parties
- 2
- input_root
- sha256:4c9f…a1d0
- result
- { "party_0": 612.50 GBP, "party_1": 387.50 GBP }
- computed_at
- 2026-08-11T09:14:52Z
- log_proof
- tree_size 48211 · inclusion ✓
- signature
- ed25519:5b8e…c2f7
Signature valid · Included in transparency log
Inputs never appear in the certificate, only their Merkle root. The certificate describes a computation, not a ruling.
Structured so we can't cheat
- The engine is open source, with reproducible builds and published test vectors.
- Inputs are sealed until lock-in. We never see them before everyone commits.
- Computation is deterministic: no AI, no floats, no external price feeds.
- Every certificate is appended to a public Merkle transparency log.
- Every certificate is signed; the verifying public keys are published at GET /v1/status.
- Raw inputs are never sold or shared, and they never go anywhere near telemetry.