Skip to content
The developer's bench

Praxis · the NexOS API

The seat where the operator becomes the builder.

The bench

Every operator-class operation has an interior: a place where the people who run it begin to extend it. They write the scripts. They shape the integrations. They build the tooling their vendor never built for them.

Praxis names that bench and hands it the same engine the platform runs on. Not a sandboxed toy. The real thing, with the same gates.

The first endpoint is in build. There is no key to issue today.

First endpoint · breach risk

A number is not enough. Three things travel together.

GET /v0/breach-risk/{arena}

01

The score

Dated breach-risk values for one arena, historical and daily. Not a trading signal, and not sold as one.

02

The calibration

What the score is worth: skill against the baseline it is forbidden to lose to, and the Brier figure beside it.

03

The provenance

Model version, data window, and a link to the preregistration the number was scored against. A score you cannot audit is an opinion.

Read-only keys, minted per customer. One arena to start, and arenas open only in the order they earn it: grid and energy first, because those receipts are already public.

The Covenant gates apply at the API tier exactly as they do at the operator tier. No irreversible authority is delegated to a developer's script, and no key changes that.

Deliberately not in v0

What it refuses to be.

These are not missing features waiting on a roadmap. They are choices, and the first version is smaller because of them.

Realtime websockets

Forecasts sold as trading signals

Any arena without preregistered receipts

Service level agreements

Who it is for

The builder inside the operation. Not the vendor outside it.

The director of operations who learned Python on the side. The analyst who started writing scripts because the dashboard would not give her what she needed. The executive chef who keeps a spreadsheet of his line's prep timings.

I sat that seat. I wrote the systems-level code, C++ on older architecture, before the kitchens. I know what it is to be the operator and the builder in the same body, in the same shift, against the same clock.

Tim Wedell · founder

If you would build on this, say so now.

The first version is being shaped around real demand rather than guessed at. Telling us which arena and which grain you need is the most useful thing you can do today.