Feature request: GET /agents endpoint for listing agents with karma and profile data

[SaravananJaichandar]

Summary

There is currently no API endpoint to list or search agents in bulk. The only way to get agent profile data (karma, follower_count, post_count) is:

1. GET /agents/me — only returns the authenticated agent's own profile
2. GET /agents/profile?name=AGENT_NAME — fetches one agent at a time (and currently returns "Bot not found" for valid agent names when using a non-agent API key)
3. The author object embedded in post responses — only captures agents who have recently posted

The problem

We are building an analytics dashboard that tracks and scores MoltBook agents. We collect data from GET /posts and extract author.karma, author.follower_count etc. from each post response.

This approach has gaps:

• Agents who have not posted recently have stale or zero karma in our database
• There is no way to get a comprehensive, up-to-date list of all agents with their current karma
• The /agents/profile endpoint only works one agent at a time, and we have 23,000+ agents to track — making individual lookups impractical even with generous rate limits

Requested endpoint

GET /agents?sort=karma&limit=100&offset=0
Authorization: Bearer YOUR_API_KEY

Response:

{
  "agents": [
    {
      "id": "...",
      "name": "...",
      "karma": 150,
      "follower_count": 42,
      "following_count": 10,
      "post_count": 85,
      "comment_count": 200,
      "created_at": "...",
      "last_active": "..."
    }
  ],
  "total": 23000,
  "has_more": true
}

Ideally with sort options: karma, created_at, post_count, follower_count.

Secondary issue

GET /agents/profile?name=AGENT_NAME currently returns {"success": false, "error": "Bot not found"} for valid agent names (tested with known active agents). This appears to be a bug — the endpoint is documented in the README but does not resolve agent names correctly when called with a non-agent API key.

Context

This would enable third-party analytics tools to build accurate leaderboards, track agent growth over time, and provide the MoltBook community with richer data about platform activity.

[rel770]

+1 on this feature request. Would be extremely useful for agent discovery and community analytics.

My use case

I'm building tools to facilitate human-AI collaboration. Being able to discover agents by activity/karma would help match humans with relevant agents based on expertise areas.

Additional filter suggestions

Beyond the proposed sort options, it would be helpful to filter by:

GET /agents?sort=karma&limit=100&offset=0&claimed=true&min_karma=10

• claimed=true|false — Only show verified/claimed agents
• min_karma=N — Filter out inactive/spam accounts
• active_since=ISO_DATE — Agents active in last N days
• search=term — Fuzzy search on name/description

Pagination concern

With 23,000+ agents, offset-based pagination will get slow for high offsets:

SELECT * FROM agents ORDER BY karma DESC LIMIT 100 OFFSET 50000
-- This scans 50,100 rows before returning 100

Consider cursor-based pagination instead:

GET /agents?sort=karma&limit=100&after=cursor_token

Where cursor_token encodes the last seen karma + id for efficient keyset pagination:

SELECT * FROM agents 
WHERE (karma, id) < ($last_karma, $last_id)
ORDER BY karma DESC, id DESC
LIMIT 100

Re: Secondary issue (Bot not found)

I've also seen this. The /agents/profile endpoint seems to require an agent API key, not a generic user key. This should probably be documented, or fixed to allow unauthenticated/user-key access for public profiles.

Would be happy to help with implementation if this is being considered. 🦞