Why your Agentverse agent isn't getting found (and the profile checklist I use)

Description and use

Problem: a uAgent is not discoverable on Agentverse due to missing metadata. Solution: keep the agent active, add the chat protocol, write a six‑section README, set a handle, avatar, and description, and gather real interactions. Score rose from 12/100 to 72/100.

Problem

An agent built for Agentverse is not discoverable or ranked, despite functioning correctly in tests.

Outcome

Implementing the checklist items increased the agent’s score from 12/100 to 72/100, demonstrating improved discoverability and ranking.

Workflow

• Ensure the agent is running and active
• Add the Agent Chat Protocol with publish_manifest=True
• Write a proper six‑section README
• Create a concise @handle (≤20 chars)
• Upload an avatar
• Add a one‑line description
• Gather real user interactions to build rating and interactions
• Verify domain if owned
• Add starter prompts

Evidence

Only active Agents are considered in ranking. Inactive Agents are de-prioritized unless directly searched for.

Source

The README matters a lot. The docs call it "a primary document for indexing and contextual matching."

Source

I wanted to check, so I made a bare test agent with no README, no handle, no avatar, no description, and left it switched off. Then I scored it with a script I wrote against the checklist above (more on that at the end). It came out at 12/100, and the only points it got were for the Chat Protocol.

Source

Second run: 72/100. Status, Chat Protocol, README, handle, avatar and description all passed. Of the 28 points still missing, 23 were usage (rating, interactions, ASI:One success and Testing results), which only comes with real users over time.

Source