Merchants block AI agents because they look like bots, and lose the sale. AVA Pay™ verifies the cryptographic signatures real agents already carry: ChatGPT-style Web Bot Auth, Visa Trusted Agent Protocol, Google AP2, and AVA's TAP-style profile. One verdict comes back, and your policy decides what verified identity earns. One install. Four protocols. Your rules.
Click the button. Your browser signs a real request with the public demo agent's key, sends it to /verify, and renders the verifier's verdict. No simulation. Actual Ed25519 signatures, actual RFC 9421 signature bases, verified server side. Demo visits verify but never earn a discount.
Keys resolve through a federated chain: Visa's directories, Web Bot Auth key directories, and this hosted AVA directory as the private-allowlist fallback. If you already publish a Web Bot Auth key card, AVA Pay merchants verify you with no registration at all. Lookup is a plain HTTPS GET; resolution is cached merchant-side for 5 minutes. Below is the live state of this instance's directory.
npm install @ava-pay/agentThree lines of code. Sign requests for any of the four protocols from the same SDK, or skip registration entirely by publishing a Web Bot Auth key card.
import { generateAgentKeyPair, signWithVisa } from '@ava-pay/agent';
const { privateKey } = generateAgentKeyPair();
const signed = signWithVisa({
method: 'POST',
url: 'https://shop.example.com/cart',
body: JSON.stringify({ items: [...] }),
agentId: 'agent_acme',
privateKey,
mandate: { /* user authorization */ },
});
await fetch(signed.url, {
method: signed.method,
headers: signed.headers,
body: signed.body,
});Add AVA Pay through the API, the Shopify app (live on the Shopify App Store), or the WooCommerce plugin. Every agent request returns one protocol-agnostic verdict: who the agent is, plus the buyer-scoped mandate when the protocol carries one. Your policy decides what that identity earns, and the Shopify app's dashboard shows traffic, conversion, and discount spend by agent platform.
The WooCommerce plugin is in the WordPress.org plugin directory, and its source is open on GitHub. It records the same verification and order events, with its dashboard to follow. BigCommerce and a generic JS middleware are next.