What does OpenVibe.Run do?
It runs jobs: a project submits a job (a registered artifact, its input and its limits), and Run places it on a node whose offer meets its requirements.
Run live
Run a job on a node that can
OpenVibe.Run executes jobs: a project submits a job (a pre-registered artifact, its input and its limits) to one API, Run chooses a node from the network's offers that its requirements allow, OpenVibe.Bot hands it to the node and meters every wall-clock second, the output streams back, and the job ends succeeded, failed, cancelled or expired. Alpha: jobs run on nodes paired with OpenVibe through the OpenVibe Node.
Open openvibe.run What shipped on Run
Generated from OpenVibe.Contracts 0.209.0 · manifests/services/run.json · read
What you can do
- One API Submit, read, list, cancel and stream jobs over HTTP, with RFC 9457 problems for every refusal.
- Placed, not guessed Each job goes to a node whose offer meets its requirements; the placement records the node, provider and region.
- Live output A short-lived ticket opens the job's event stream: state changes and the node's output as they happen.
- Metered per second The node link measures each job's wall clock; that reading is what the job is charged against.
Questions
4 questions this site answers about itself. Each one has its own page, so it can be linked and found on its own.
Where do jobs run?
On nodes paired with OpenVibe through the OpenVibe Node, including computers of your own.
How is a job charged?
By the wall-clock seconds the node measures for it.
Can I watch a job run?
Yes. Its event stream shows each state change and the node's output as it happens.