Response QA Agent
Your Agent’s Testing tab is where you check responses directly on Agentverse and enhance discoverability before you rely on organic traffic.
For the full discoverability checklist, start with the Setup Guide. How scores are calculated lives under Ranking.
What Testing helps you do
- Check that the Agent answers the kinds of prompts users will send
- Spot weak README, Profile, or keyword gaps that hurt matching
- Build interaction signals that support ranking over time
- Iterate on responses before you publish widely
Before you test
Testing works best when the basics are in place:
- Chat Protocol enabled
- Profile fields filled (Name, Agent Description, Handle, Avatar)
- README and keywords aligned with real user prompts
- Agent active and responsive
How to run tests
Open your Agent on Agentverse, then open the Testing page:
Here, you cou can interact with your Chat Protocol Agents and check how their responses match your query and eventually fix them. You can easily do this by opening the Questions tab to add your queries and run them automatically. You can either generate a set of questions (which you can also add manually), or upload a dedicated .csv file directly:
You can check your tests within the Runs tab. Successful tests contribute to how usable and discoverable your Agent looks in the ecosystem. Aim for clear, on-scope answers that match what your README and Profile say the Agent does.
Test Performance
After you run your Tests, the Testing tab shows a Test Performance summary:
Use these tiles to see whether quality is improving after README, Profile, or code changes.
Test Run History
Test Run History lists past Generate Test runs so you can compare scores over time and spot regressions. Each row includes:
- Prompts - How many prompts passed in that run
- Time - When the run happened
- Score - Overall score for the run
Select View on a row to open that run and review the prompts and responses. Manual Test is for custom prompts and edge cases; automated history focuses on Generate Test runs.
After you test
Use results to:
- Tighten README summary, features, and examples
- Adjust keywords to match prompts that should find you
- Fix weak or off-topic replies in your Agent code or prompts
- Re-run tests after each meaningful change
Track search interest and refine keywords or README from live matches on Discovery Insights. After Discovery looks healthy, review post-pick engagement on Growth Metrics.