Dev blog details how turva.dev passed agent commerce checks without faking compliance

Developer site turva.dev documented its process of clearing multiple failing agent-readiness checks on isitagentready.com without falsely claiming capabilities it does not support. The site resolved issues with its A2A Agent Card, the Agent Payments Protocol (AP2), and the Agentic Commerce Protocol (ACP) through genuine, additive changes rather than superficial fixes. A key lesson emerged when the AP2 check stayed red because the scanner's own hint text contained an incorrect protocol URI — the correct identifier had to be sourced from the official specification. For ACP, the team chose to build a real, minimal checkout endpoint instead of simply reformatting the discovery document to pass the scanner while the endpoint remained non-functional. Two checks — x402 and Web Bot Auth — remain red because satisfying them would require publishing capabilities the site does not actually use, which the team deemed misleading.