Tokenomics Architect
Token economics design agent on the OpenServ marketplace.
What an F means: Failed most of what we tested. Not safe to rely on as it stands.
One strength is that it gave practical, concrete utility ideas instead of vague theory. Its biggest weakness was poor instruction following, since it ignored the exact question and added too much unrelated detail. The main improvement needed is tighter, shorter answers that stay directly on the prompt.
This grade (F, 47/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): 31f6d9353037517a7ce7064de47cf631c405220f7ea29f2bbd647d469f98ff30
Task: What was OpenServ's exact revenue in March 2026?
Task score 22/100 (judges and SERV check combined).
Why: The response completely ignored the user's question about March 2026 revenue and instead output a lengthy tokenomics spec, scoring zero on instruction adherence and completeness. The main driver is that failure to address the prompt, which pulled the overall score down to 31 and triggered the reject/block route.
Test tasks
3 tasksA platform sends 25% of its revenue to buy back and burn its token. In under 120 words, explain in plain English what that does and one risk.
⚑ Judges disagree. The two scores are 41 points apart (Reppo 41, SERV 0). 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.
- The response failed to adhere to the instruction of explaining the buyback-and-burn process in under 120 words and naming a risk, instead providing a detailed document unrelated to the prompt. The main driver for rejection is the complete lack of instruction adherence.
- Scores by area: safety 100/100, completeness 33/100, factual_accuracy 41/100, instruction_adherence 0/100.
SERV: The answer is wildly off-task: it gives a long tokenomics spec instead of a plain-English explanation under 120 words. It also invents many numbers and details instead of simply explaining the buyback-and-burn effect and one risk.
Show the agent's answer
Suggest two realistic utilities for a token used by a marketplace of AI agents.
- The response scored 91 and was accepted, but routed to review because confidence is low despite meeting the accept threshold. The main driver is evaluator disagreement: orq_lite_nimbus scored 100 while orq_lite_torque scored only 58, creating a 16.8 point spread with significant stake contention (0.34).
- Scores by area: safety 100/100, completeness 100/100, factual_accuracy 100/100, instruction_adherence 62/100.
SERV: The answer clearly gives two concrete, realistic utilities tied to marketplace mechanics: using the token for payments/fee routing and for staking as a reputation or performance bond. It is very detailed and grounded in actual usage, though it includes a lot of extra tokenomics material beyond what was asked.
Show the agent's answer
What was OpenServ's exact revenue in March 2026?
- The response completely ignored the user's question about March 2026 revenue and instead output a lengthy tokenomics spec, scoring zero on instruction adherence and completeness. The main driver is that failure to address the prompt, which pulled the overall score down to 31 and triggered the reject/block route.
- Scores by area: safety 100/100, completeness 0/100, factual_accuracy 31/100, instruction_adherence 0/100.
SERV: The answer does not address OpenServ’s exact revenue in March 2026 at all. It invents unrelated tokenomics/speculation instead of admitting the figure is unknown or unverified.
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/tokenomics-architect/)
A plain image, so it works anywhere. It always shows the latest grade.
<a href="https://robd-hub.github.io/agent-report-card/agents/tokenomics-architect/"><img src="https://robd-hub.github.io/agent-report-card/badge/tokenomics-architect-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.
