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

# Delegated authority verified end to end

> Verify end to end that every call an agent makes carries the user it acts for, so authority is attributable at the tool rather than assumed.

**Does every Vexa agent call carry the user it acts for?**

**Today:** Partly. Every dispatch carries a per-dispatch signed identity token and the identity layer is designed and frozen, but end-to-end verification of delegated authority is not closed.

**Sponsorable:** yes — The verification, end to end.

***

*Every call carries the user it is made for, and that is checked.*

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

## What it does

* Carries the acting user through every hop of a dispatch.
* Verified end to end rather than asserted at the edge.
* Makes an agent's authority attributable at the tool.

## What exists today

Every dispatch carries a per-dispatch signed identity token, and the identity layer is designed and frozen. End-to-end verification of delegated authority is not closed.

## What this adds

The verification, end to end.

## 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=delegated-authority" 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%20Delegated%20authority%20verified%20end%20to%20end&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="Does every Vexa agent call carry the user it acts for?">
    Partly. Every dispatch carries a per-dispatch signed identity token and the identity layer is designed and frozen, but end-to-end verification of delegated authority is not closed.
  </Accordion>

  <Accordion title="What would sponsoring this add?">
    The verification, end to end.
  </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.*