AP2 (Agent Protocol)
The protocol in Google’s Gemini agentic stack; SkuLift supports it as future-proofing.
What is AP2?
AP2 (Agent Protocol) is the protocol used in Google’s Gemini agentic stack. SkuLift supports AP2 as future-proofing: current usage is narrow, but the wire format is implemented so the brand is ready as Gemini’s agentic commerce matures.
AP2 is the Gemini-side agent protocol — the channel through which a Google agent would discover and transact with a brand.
The Agent Protocol defines the structured exchange between Google’s Gemini agents and the merchants or services they act on. As the third pillar alongside ACP (OpenAI) and MCP (Anthropic), it covers the same problem from Google’s side: letting an agent move from a buyer’s intent to an action without a human clicking through a site.
SkuLift’s stance on AP2 is deliberate future-proofing. Gemini’s agentic commerce is still emerging, so usage today is narrow — but supporting the wire format means a brand is reachable the moment Google’s agents scale, rather than scrambling to integrate after the fact.
Speaking all three protocols matters because buyers do not pick one engine. A brand that is citable in AEO/GEO terms and transactable across ACP, AP2 and MCP is covered wherever the agentic conversation happens.