A small service
on purpose.

Why it exists

Agents are good at deciding what to compute and bad at computing it. Ask a model for a compound interest figure and you get a confident number that is sometimes wrong. Ask it for the third Tuesday of next month and you get a paragraph. The usual fix is more tools with more credentials, which turns a small problem into a large attack surface.

axon is the smaller fix. One endpoint, no account, no key, no storage. The model writes a few lines of JavaScript, the answer comes back as JSON, and the arithmetic is done by an interpreter instead of a probability distribution.

Three principles

• Stateless. A new runtime per request. Nothing to leak between callers because nothing is kept. This is also why there is no dashboard: there would be nothing on it.
• No retention. The Worker does not log code, does not write bodies and has no database. The only durable state in the deployment is the package cache at Cloudflare's edge, which holds public library code, not yours.
• One job, done well. Logic, not compute. Ten milliseconds of CPU is a design constraint, not a limitation to apologise for. When a request needs more, the honest answer is a different service.

How it is built

A Cloudflare Worker on the free plan, TypeScript, static assets served from the same deployment, no framework and no build step for the site. The sandbox is QuickJS compiled to WebAssembly, driven by quickjs-emscripten. Packages are resolved through esm.sh before evaluation. There is no queue, no Durable Object and no database, because all three are paid products and none of them are needed for a stateless function.

The source is MIT licensed at github.com/naas1201/axon. If you would rather not depend on someone else's endpoint, deploy your own copy. It takes three commands.

The studio

LPP Development Studio builds small, durable software: static sites, internal tools, automation, and the occasional strange utility like this one. Independent, based in France, contactable at qmpro@outlook.com.