> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vexa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Per-dispatch outcome and attribution on the API

> Expose the outcome of each Vexa dispatch and what it is attributable to on the API, so a consumer can tell why a run ended the way it did.

**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.*

|                 |                                          |
| --------------- | ---------------------------------------- |
| **Status**      | **sponsorable**                          |
| **Size**        | S                                        |
| **North star**  | 4 · Agents that act on meetings, safely  |
| **Measured by** | verified delegated authority and tracing |

## 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

<Columns cols={2}>
  <Card title="Sponsor this" icon="handshake" color="#0D9373" href="https://cal.com/dmitrygrankin/web?utm_source=docs&utm_medium=roadmap&utm_campaign=sponsor&utm_content=dispatch-outcome-attribution" horizontal arrow cta="Book fifteen minutes">
    Fifteen minutes. Bring the constraint you are under.
  </Card>

  <Card title="Watch this" icon="envelope" color="#0D9373" href="mailto:dmitry@vexa.ai?subject=Roadmap%20update%3A%20Per-dispatch%20outcome%20and%20attribution%20on%20the%20API&body=watch" horizontal arrow cta="Email me">
    One email when it ships. The mail is already written — send it as it is.
  </Card>
</Columns>

## Questions

<AccordionGroup>
  <Accordion title="Can I tell from the API why a Vexa run ended the way it did?">
    No. A consumer can see that a run did not complete, but the reason is not carried through to the API surface.
  </Accordion>

  <Accordion title="What would sponsoring this add?">
    The per-dispatch outcome and its attribution, on the API.
  </Accordion>

  <Accordion title="What happens when it ships?">
    It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
  </Accordion>
</AccordionGroup>

***

*Ships upstream Apache-2.0 when sponsored.*