Skip to main content
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.

​
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

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

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.
The verification, end to end.
It ships upstream under Apache-2.0, to everyone, with the sponsor named on the release note.
Ships upstream Apache-2.0 when sponsored.