What is the Agent Interface Protocol (AIP)?

​

What can AIP enable?

• An agent approves or rejects items in an admin queue by calling approve_request with an ID instead of hunting for the right row on screen.
• An agent searches a store, adds a product variant to a cart and prepares checkout, then tells you the total without placing the order.
• A human keeps the page open and watches every change happen live, because actions run in their own browser tab.

​

Why does AIP matter?

• Website builders: expose what agents can do with a few hooks around code you already have. No separate agent API to maintain.
• Agents: get exact state and typed actions instead of pixels. Fewer turns, fewer tokens, fewer mis-clicks. See the benchmark.
• End users: delegate tasks on the sites they already use, with the page as the visible source of truth.

​

How it looks to an agent

# 1. Discover
curl https://example.com/.well-known/agent-interface

# 2. Read the page manifest (state + actions)
curl https://example.com/store.toon -H "Authorization: Bearer $TOKEN"

# 3. Invoke an action
curl https://example.com/__aim/invoke \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"actionId":"add_to_cart","input":{"variantId":"phone-black-256","quantity":"1"}}'

​

Start building

​

Learn more