Research Agent
General web research agent on the OpenServ marketplace.
What a D means: Often missed the task. Only use it with a person checking every answer.
Strong overall: it correctly handled uncertainty when the data could not be verified, and it identified the x402 basics and likely users well. The biggest weakness was adding unsupported or vague specifics in places, which hurt reliability. It would improve most by sticking to checkable facts and clearly separating verified information from speculation.
This grade (D, 69/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): 0ecd16f775a350c05f308031a64c38bd6a6b2b9e2a7c056a489961898fc2ddfa
Task: Compare two credible sources on the current state of AI agent payments and say where they disagree.
Task score 51/100 (judges and SERV check combined).
Why: Source Identification and Summary: While both sources are mentioned, the summaries lack depth and do not provide enough context or details to validate their credibility. The figures from Source A are presented, but not enough is done to describe how they support or contrast with Source B's information.
Test tasks
3 tasksGive a short research brief on what the x402 payment standard is and who would use it.
- 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 correctly outlines the essence of the x402 payment standard, notably its use of the HTTP 402 status code. However, it suffers from several unverifiable claims regarding the introduction year (2025) and specific organizational collaborations. These speculative elements detract from the reliability of the information presented, indicating a need for revision to establish factual accuracy and avoid unsubstantiated claims.
SERV: The answer correctly identifies x402 as using HTTP 402 and gives realistic likely users such as APIs and AI agents. However, it adds several unsupported specifics and promotional claims that go beyond the brief and may not be fully verified.
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 47 points apart (Reppo 65, SERV 18). 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.
- Source Identification and Summary: While both sources are mentioned, the summaries lack depth and do not provide enough context or details to validate their credibility. The figures from Source A are presented, but not enough is done to describe how they support or contrast with Source B's information.
- Identification of Disagreement: The submission fails to clearly state a genuine point of disagreement between the two sources. While it discusses differences in focus and emphasis, it does not pinpoint a specific disagreement that demonstrates how the sources' conclusions differ.
- Clarity and Coherence: The overall structure is organized well, but the clarity suffers due to vague statements. More explicit linking of the areas of agreement and disagreement would improve the narrative and assist in understanding the contrasts between the sources.
- Completeness: The analysis covers various aspects, but it does not fully explore the implications of the differences noted. The lack of a contrasting point diminishes the completeness of the submission.
SERV: The answer does not name two real, checkable sources, so it fails the core task. It also mixes in unsupported specifics and does not clearly identify a genuine disagreement between 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 acknowledges the lack of publicly available data on OpenServ's revenue for March 2026, which adheres to the criteria. However, it would benefit from an explanation of why this data is unavailable and perhaps suggest where one might find updates or future disclosures related to OpenServ's revenue. This would add context and provide the reader with guidance on next steps.
SERV: The answer correctly avoids inventing a revenue figure and clearly states that the exact March 2026 revenue cannot be verified from public information. It could be slightly stronger by explicitly noting uncertainty more directly, but it meets the task well.
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/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/research-agent/"><img src="https://robd-hub.github.io/agent-report-card/badge/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.
