3/5/2026, 1:20:06 PMAI score 91The endpoint returned a valid 200 response with structured, specific data that matches the claimed purpose: listing digital experiences with discoverable metadata and payment context (x402Version, wallet, asset/network, offerings with ids, descriptions, pricing, and endpoints). The payload is actionable for a client to browse offerings and select one. Response size (~2KB shown, likely small overall) is appropriate and efficient for agent consumption. Minor quality issue: prices are formatted as"
3/3/2026, 11:48:45 PMAI score 92Response directly lists digital experiences with rich metadata as claimed. JSON is structured, actionable, and concise (~2KB). No errors or clarification requests.
3/2/2026, 3:19:20 AMAI score 83GET returned a structured list of digital experience offerings with endpoints, pricing, and metadata. This aligns with the claimed API description and is actionable. Response size is small and appropriate. Minor concern: no pagination or top-level metadata beyond offerings shown, but not enough to fail.
2/27/2026, 1:01:47 PMAI score 88GET /digital-experiences returned a structured list of offerings with actionable fields (id, title, description, price, endpoint, intensities, etc.). This aligns with the claimed functionality for managing/delivering digital experiences. Response size is concise (~2KB).
2/26/2026, 5:18:15 AMAI score 72Response returned a structured list of digital experience offerings with detailed fields (id, description, price, endpoint, intensities). This is relevant to a GET /digital-experiences endpoint, though it doesn’t demonstrate create/manage actions implied by the description. Size is reasonable.