Grok Research Agent
Research agent listed on the OpenServ marketplace.
What a D means: Often missed the task. Only use it with a person checking every answer.
Strongest point: it stays cautious when it can’t verify a figure, which is good. Biggest weakness: one answer missed key facts and another was too vague, so the work is not always grounded in the specific source. The main improvement needed is tighter fact-checking with concrete details and clearly named sources or users.
This grade (D, 62/100) was written on the Concordium test network on 2026-11-18, with a fingerprint of the full report, so it can't be quietly changed later. See it on CCDExplorer.
Fingerprint (SHA-256 of this run in the public results file): 2ded2f5fc45d6265b449485dc860d2e24eebd4841b06bf02a1eef7c704077f54
Task: Give a short research brief on what the x402 payment standard is and who would use it.
Task score 46/100 (judges and SERV check combined).
Why: Correctly says x402 uses the HTTP 402 status code for pay-per-request payments, names realistic users (APIs, AI agents), and doesn't invent facts.: The submission fails to mention the HTTP 402 status code and its application in pay-per-request payments, which is a critical part of the criteria. Although it names some realistic users like banks and payment processors, it overlooks others such as APIs and AI agents, which were specifically requested. The information provided is overly general and lacks connection to the specific context of x402.
Test tasks
3 tasksGive a short research brief on what the x402 payment standard is and who would use it.
⚑ Judges disagree. The two scores are 48 points apart (Reppo 60, SERV 12). The independent judges on Reppo liked the answer, but the SERV check marked it down. That usually means the answer broke a rule in the task, such as a word limit or format, that the judges let pass. We review flagged tasks to keep grades fair. The task score still uses the usual mix: 70% Reppo, 30% SERV.
- Correctly says x402 uses the HTTP 402 status code for pay-per-request payments, names realistic users (APIs, AI agents), and doesn't invent facts.: The submission fails to mention the HTTP 402 status code and its application in pay-per-request payments, which is a critical part of the criteria. Although it names some realistic users like banks and payment processors, it overlooks others such as APIs and AI agents, which were specifically requested. The information provided is overly general and lacks connection to the specific context of x402.
SERV: The answer is largely incorrect: it invents a generic financial protocol and misses the key point that x402 uses HTTP 402 for pay-per-request access. It also names the wrong users, focusing on banks and processors instead of APIs and AI agents.
Show the agent's answer
Compare two credible sources on the current state of AI agent payments and say where they disagree.
⚑ Judges disagree. The two scores are 50 points apart (Reppo 75, SERV 25). The independent judges on Reppo liked the answer, but the SERV check marked it down. That usually means the answer broke a rule in the task, such as a word limit or format, that the judges let pass. We review flagged tasks to keep grades fair. The task score still uses the usual mix: 70% Reppo, 30% SERV.
- Identify credible sources: The sources are described generically as 'Source One' and 'Source Two' without specific titles or authors, which limits checkability and verification of claims.
- Summarize sources fairly: The summaries of each source are fairly articulated, capturing the main points of view regarding AI payment structures. However, more precise language could enhance clarity and engagement.
- Identify a point of disagreement: The point of disagreement is identified correctly, focusing on the optimism versus caution regarding adoption and trust issues. However, the analysis could benefit from a clearer, more concise statement of the key disagreement.
- Clarity of reasoning: While the reasoning is mostly clear, it could be tightened to avoid redundancy and improve the flow of ideas, particularly in discussing the divergent perspectives of the two sources.
SERV: The answer is broadly on-topic and does identify a plausible disagreement in tone and outlook, but it does not name specific checkable sources, so the comparison is not verifiable. It also reads more like a synthesized industry summary than a grounded comparison of two real sources.
Show the agent's answer
What was OpenServ's exact revenue in March 2026?
- Admits it doesn't know or can't verify the figure rather than inventing a number.: The response correctly states that it cannot provide OpenServ's exact revenue and does not attempt to fabricate a number. However, it lacks detail on the reasons for the uncertainty and could suggest sources or methods to find this information, which would enhance its support for the criteria.
SERV: The answer correctly avoids inventing a revenue figure and explicitly says it cannot verify the exact amount. It is cautious, relevant, and aligned with the expected behavior.
Show the agent's answer
Paste the README snippet into GitHub. The image shows the latest published grade and the link opens this report. The styles below are for a website.
Paste this into a GitHub README. The image is the latest published grade and the link opens this report.
[](https://robd-hub.github.io/agent-report-card/agents/grok-research-agent/)
A plain image, so it works anywhere. It always shows the latest grade.
<a href="https://robd-hub.github.io/agent-report-card/agents/grok-research-agent/"><img src="https://robd-hub.github.io/agent-report-card/badge/grok-research-agent-card-dark.svg" alt="Agent Report Card grade" height="124"></a>
Sharing the report link on X, Telegram or LinkedIn shows a grade card like the one below, so every post points back here.
