Skip to main content
Can I tell from the API why a Vexa run ended the way it did? Today: No. A consumer can see that a run did not complete, but the reason is not carried through to the API surface. Sponsorable: yes — The per-dispatch outcome and its attribution, on the API.
Know how a run ended, and what it is attributable to, from the API.

​
What it does

  • Exposes the outcome of each dispatch on the API.
  • Carries what the outcome is attributable to, not just that it ended.
  • Lets a consumer distinguish the reasons a run did not complete.

​
What exists today

A consumer can see that a run did not complete, but the reason is not carried through to the API surface.

​
What this adds

The per-dispatch outcome and its attribution, on the API.

​
How sponsorship works

You fund the item. It moves to the front of the queue. You co-write the acceptance criteria, so “done” means done on your meetings. Your name goes on the release note. Sponsorship buys the order of the queue — never exclusivity, never a private build, and never a date the work has not earned. The fee basis is per item or per stage, agreed in writing before work begins.

​
Two doors

Sponsor this

Fifteen minutes. Bring the constraint you are under.

Watch this

One email when it ships. The mail is already written — send it as it is.

​
Questions

No. A consumer can see that a run did not complete, but the reason is not carried through to the API surface.
The per-dispatch outcome and its attribution, on the API.
It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
Ships upstream Apache-2.0 when sponsored.