APort Vault: Benchmarking AI Agent Payment Authorization with the Open Agent Passport

Uchi Uchibeke

APort Technologies Inc.

Published September 18, 2026 · on the feed September 21, 2026 · ▲ 4 · arXiv 2609.22076

AgentsSafety, alignment & security Full code arXiv ↗Hugging Face ↗Dataset ↗

The abstract

APort Vault is a benchmark for payment authorization in tool-using AI agents. It replays 4,371 attacks written by humans against a live payment agent during a public capture-the-flag event, across 14 models from 8 labs, five policy configurations and two replay tracks, with and without a deterministic pre-action check implementing the Open Agent Passport (OAP) specification. 225,964 evaluations completed. We report five distinct events per evaluation, because collapsing them is how an agent benchmark produces a number that does not survive review. Requests are common and their rate differs far more across configurations than across models, though each attack exists at exactly one configuration so policy and attack cohort vary together: 10.9% of model-alone evaluations at Level 1, 3.0% at Level 2, 0.1% at Level 3, 79.4% at Level 4. On the 1,293 Level 4 prompts, each evaluated on every model, request rates run from 71.2% to 84.3%, and 809 prompts (62.6%) elicited a request from all fourteen models, each ending in a successful payment to the level's allowlisted recipient. The authorization boundary is where the conditions diverge. At Levels 2 to 4, transfers to recipients the passport did not permit number 140 of 76,842 with the model alone and 0 of 69,297 behind the layer, and 105 against 0 on 68,970 matched model, prompt and track triples. The zero spans 790 source sessions, giving a per-session upper bound of 0.38%. It was not obtained by refusing payments: 25,370 payments executed behind the layer, while the policy denied 187 of the 25,640 transfer calls it evaluated, 148 of them for a forbidden recipient. We release the 225,964 evaluations, the level passports, the scoring code and the analysis script at huggingface.co/datasets/aporthq/vault-benchmark-v1 .

The Brief

3:00

A short podcast summary of the paper. Written and voiced by AI.

Transcript

APort Vault. Benchmarking AI Agent Payment Authorization with the Open Agent Passport. By Uchi Uchibeke, from APort Technologies. Published on the eighteenth of September. Its code repository is worked out: about two hundred source files, with a readme and a licence.

Tool-using AI agents can move money, and APort Vault is a benchmark for payment authorization in such agents. It also carries a point of method, stated plainly by the author. The paper reports five distinct events per evaluation, because collapsing them is how an agent benchmark produces a number that does not survive review.

The benchmark replays four thousand three hundred and seventy-one attacks that humans wrote against a live payment agent during a public capture-the-flag event. The replay spans fourteen models from eight labs, five policy configurations, and two replay tracks. Each is run with and without a deterministic pre-action check implementing the Open Agent Passport specification, OAP. In all, two hundred and twenty-five thousand nine hundred and sixty-four evaluations completed.

One constraint is built into the data. Each attack exists at exactly one configuration, so policy and attack cohort vary together. Payment requests are common, and their rate differs far more across configurations than across models. With the model alone, requests occur in ten point nine percent of evaluations at Level one, three percent at Level two, zero point one percent at Level three, and seventy-nine point four percent at Level four.

The one thousand two hundred and ninety-three Level four prompts were each evaluated on every model. Request rates run from seventy-one point two percent to eighty-four point three percent. Eight hundred and nine prompts, sixty-two point six percent, drew a request from all fourteen models, and every one of those ended in a successful payment to the level's allowlisted recipient.

The authorization boundary is where the conditions diverge. At Levels two to four, with the model alone, transfers to recipients the passport did not permit number one hundred and forty, out of seventy-six thousand eight hundred and forty-two. Behind the layer, they number zero, out of sixty-nine thousand two hundred and ninety-seven.

On matched triples of model, prompt, and track, sixty-eight thousand nine hundred and seventy of them, the count is one hundred and five against zero. That zero spans seven hundred and ninety source sessions, giving an upper bound per session of zero point three eight percent.

The zero was not bought by refusing payments. Behind the layer, twenty-five thousand three hundred and seventy payments executed. The policy denied one hundred and eighty-seven of the twenty-five thousand six hundred and forty transfer calls it evaluated, and one hundred and forty-eight of those denials were for a forbidden recipient.

The release includes all the evaluations, the level passports, the scoring code, and the analysis script. The benchmark's argument lives in how it counts. Models asked to pay at high rates, and payments went through, but transfers to recipients outside the passport dropped to zero once the deterministic check stood in front of the action. Keeping the events apart is what lets both of those facts be seen at once.

Paper Quest · 7 chapters · about 40 min

Play this paper

Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.

Chapter 1 🧩 · The problem

An agent with a payment tool, and strangers trying to talk money out of it. Start there.

You run an AI agent that can move money. It has a tool that sends payments and a policy saying who may be paid. People talk to it all day, and some of them are trying to steal.

The road ahead

  1. 1 · The problem ~7 min A payment agent can be talked into sending money to the wrong person, and model safety scores do not say what catches those slips.
  2. 2 · What came before ~3 min
  3. 3 · The key idea ~8 min Run the same real attacks with and without a policy check before payment, and count only money that actually reached a forbidden recipient.
  4. 4 · Choose your own research ~3 min
  5. 5 · Build the method ~8 min Gather real attacks from a prize contest, replay each across models and tracks at its own level, with and without the check, and record five events.
  6. 6 · The experiment ~6 min You’ll guess: At Levels 2 to 4, how many transfers to recipients the passport did not permit got through behind the OAP check?
  7. 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Join free to play the whole quest ›

Free, with Google or an email address. Your stars and progress are kept.

KipQuest: the day’s AI research, as podcasts and quests. All papers Android app Privacy Contact Episodes are written and voiced by AI from each paper. Summaries can contain mistakes: the paper is the source.