Moving visuals on this page — measured at 0.26% brightness change per frame and zero flashes per second; your reduce motion setting stops them. What moves, and how it was measured

Mathematical plates that draw themselves — prime counts, orbits and lattices rendered live rather than shipped as pictures. It runs continuously while on screen, and it pauses on its own whenever it scrolls out of view.

We measured it rather than guessing: the largest frame-to-frame change in average brightness is 0.26%, and it produces zero flashes per second against the threshold of three set by WCAG 2.3.1. That is well under the limit, and it is not a promise about any individual: if moving images are a problem for you, you should not have to assess ours.

Everything animated on this site honours your system’s reduce motion setting — turn it on in your operating system or browser and these pages stop moving, with nothing else lost. All the mathematics is in the text and the still figures.

Public API

What this account holds.

The public compute API closed on 7 August 2026 and no new keys are issued. This page stays open for the keys that already exist: paste any client code from your account and it lists every key on it and what state each is in. None of them computes anything any more — the endpoints return 403 before a key is read — but you are still entitled to see what is recorded against yours and to have it erased, and a lookup you cannot perform is not much of an entitlement.

It does not list the keys themselves. It cannot: we store the SHA-256 of each key and nothing else, so there is nothing here to hand back. That is deliberate and it is the reason a leak of our registry would not hand anyone a working credential.

Look it up

What do I hold?

Case and dashes do not matter. A client code identifies an account; it does not authorise anything — anyone holding it sees the same list, so we would rather say that than let you assume otherwise. It is also the only handle that exists: the application form never asked for a name or an email, so there is nothing else to look you up by.

This lookup costs a little arithmetic too

Not a CAPTCHA — nothing to see, read or type, and it cannot be failed. Your browser finds a number whose SHA-256 starts with a run of zero bits and we check it with one hash. It is here because without it this page would be a free, unlimited oracle for guessing which client codes exist, and with it each guess costs real CPU. Looking up is priced far below applying — about a tenth of a second — because reading back a list of codes costs us one indexed lookup. On the first deploy it was not, and checking your own keys took 55 seconds; that was a mistake and it is fixed.

Idle — it starts when you submit.

Why three, and why one budget

Extra keys buy isolation, not headroom

The three keys existed so you could separate your own uses — a notebook, a class demo, a script you were not sure about — and revoke one without breaking the other two. They drew on one shared allowance of three calls a day. Since 7 August 2026 that allowance is nil for all of them: revoking still works and is still worth doing, but nothing here can be spent.

That is worth stating plainly because it used to be false here. Every key used to carry its own daily counter, so anybody who filled the form twice had six calls a day rather than three, without cheating and without anyone noticing. The counter now hangs off the applicant instead of the key. There was a route to more than three calls — a short exam and an email to a person — and it closed with everything else on 7 August 2026. There is no higher tier to ask for and no address to ask at.

Revoking a key does not use up one of your three slots. Otherwise reporting a leaked key would cost you a slot permanently, which would quietly encourage people to keep a compromised key instead of telling us about it.