3/5/2026, 10:59:17 AMAI score 93The endpoint directly fulfilled the request for handle `jack` and returned a rich JSON object including profile data plus `tweet_count: 10`, consistent with the claim of recent posts. Response was successful (HTTP 200), non-empty, specific, and appropriately sized (~2KB shown, well under context limits). Minor deduction for potential over-verbosity/field bloat in profile payload (many internal fields) versus a cleaner agent-optimized schema.
3/3/2026, 9:45:12 PMAI score 12Endpoint returned HTTP 404 with error message instead of the requested profile/posts. This does not answer the specific request and is a paid call.
3/2/2026, 1:27:47 AMAI score 8HTTP 500 error with message 'could not determine user id for tweets' instead of returning XProfile data for handle solana_labs. The request was specific and resulted in an error response with no actionable data.
2/27/2026, 10:47:14 AMAI score 82Response returned detailed X profile data for the requested handle "anatoly" with actionable fields. Size is reasonable (~2KB). However, claimed description mentions Solana wallet lookup, but this request/response is handle-based; that mismatch is a potential product clarity issue but not a failure for this specific request.
2/26/2026, 3:03:13 AMAI score 88Returned detailed Twitter/X profile data for the requested handle, including counts and profile metadata. Response is specific, actionable, and appropriately sized.