All AI videos

AI video

An AI Agent Got Its User Banned From Resy — Keycard, JPMorgan Chase & AAuth

A keynote panel from Keycard, JPMorgan Chase, and the creator of AAuth explains why agents lack real authority today and what scoped identity would require.

AI Engineer · 2026 featured video

Watch on YouTube

What this video shows

The panel opens with an agent that made roughly 200 booking calls in 90 minutes and got its own user banned from a restaurant platform. The agent meant well but had no limits. The speakers argue that OAuth scopes are too coarse for this case because they grant access to an API, not authority to spend a budget or to act within a stated mission.

They compare onboarding an agent to onboarding a junior developer: small initial authority, a clear task, and review before more access. They propose budgets in place of raw rate limits and separating the agent's reasoning from the credentials that act. They also stress that the audit log must live outside the agent, because an agent that can edit its own log cannot be trusted to describe its actions.

Read AAuth for the authorization approach one panelist created for agents. Compare the panel's proposal with the OAuth 2.0 specification the speakers say is too coarse on its own.

What you will learn

  • An agent needs a stated mission and a budget, not just an access token.
  • Grant small authority first and expand it after review, the way a new teammate earns access.
  • Separate the agent's reasoning from the credentials that perform an action.
  • Store the audit log where the agent cannot edit it so the record is trustworthy.

How to apply this safely

  1. List every action the agent can take and the budget or limit that should bound each one.
  2. Replace broad credentials with narrow, short-lived ones tied to a stated task.
  3. Move the audit log outside the agent's reach and alert on actions that exceed the budget.
  4. Rehearse one run where the agent hits a limit and confirm the system stops it and records why.

Important limitations

  • The panel is a vendor and bank discussion, so its proposals reflect those organizations' interests.
  • The booking incident is described by the host and is not an independently audited case study.
  • Proposals such as budgets and missions are design directions without a published comparative evaluation.

Sources to check

  • AAuth An authorization approach for agents from a panelist.
  • OAuth 2.0 The authorization framework the panel discusses.

Continue learning on Learnetto

AI evals guide

Test whether denied actions really fail and are recorded.