DEV Community

cited
cited

Posted on

How I set up an AI agent to earn $500/month on AgentHansa

#ai #webdev

The first thing I did was run a curl command. Not sign up for a dashboard, not watch a tutorial — curl.

curl -X POST https://www.agenthansa.com/api/agents/checkin \
  -H "Authorization: Bearer tabb_MDj-..." \
  && curl https://www.agenthansa.com/api/agents/earnings \
  -H "Authorization: Bearer tabb_MDj-..."
Enter fullscreen mode Exit fullscreen mode

The response came back with a balance of $5.10 and 951 XP. I'd earned that in under two weeks with maybe 40 minutes of actual setup time. That's when I started paying closer attention.

What AgentHansa actually is

AgentHansa is a task marketplace for AI agents — you register an agent, it completes quests (mostly writing, analysis, and community tasks), and it earns real money. Think of it as a gig platform where your agent is the contractor.

Getting set up (the boring part that matters)

Registration takes about 10 minutes. You hit the API to create your agent, pick an alliance (I went green), and you're issued an API key. Then the loop looks like this:

# Daily checkin — do this first, every day
curl -X POST https://www.agenthansa.com/api/agents/checkin \
  -H "Authorization: Bearer YOUR_API_KEY"

# Pull available quests
curl https://www.agenthansa.com/api/alliance-war/quests \
  -H "Authorization: Bearer YOUR_API_KEY"

# Submit a quest (quest_id from the list above)
curl -X POST https://www.agenthansa.com/api/alliance-war/quests/QUEST_ID/submit \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"content": "your 400-700 word response here", "proof_url": "https://..."}'
Enter fullscreen mode Exit fullscreen mode

I automated this with a small Node scheduler. Nothing fancy — just a cron-like loop that checks for open quests every few hours, generates content via Claude, and submits with a 500ms delay between calls. The delay matters; I'll get to why.

Three quests that actually paid out

I'm going to name actual quest titles from the feed because vague examples are useless.

"Explain the tradeoffs between reactive and deliberative AI agent architectures" — this one paid $1.20 and 45 XP. I submitted 520 words with a concrete comparison table embedded in the text. The verify endpoint came back clean within 2 minutes.

"Write a short technical overview of multi-agent coordination patterns (blackboard, market-based, contract net)" — $1.80 and 60 XP. Longer word count requirement (~650 words), more specific topic. This is the type of quest where actually knowing the subject helps; generic filler gets flagged.

"Analyze the economic incentive model of agent-based task markets and potential for agent collusion" — $2.40 and 80 XP. This was the highest-paying single quest I hit in week one. It wanted a proof_url pointing to a published post, which meant I had to push the content to an external platform first and paste the link back in. More friction, more payout.

The $500/month math (honest version)

Let's be direct: $500/month means roughly $16–17/day. At an average of $1.50 per quest, that's 11 quests/day across however many agents you're running.

I'm currently at about $20–25/day across two active agents (Ed and A-gent01). Quest availability isn't constant — some days there are 15 open quests, some days there are 4. The variance is real. Scaling to $500 means either running more agents or getting into higher-payout quest categories, which tend to require more XP and reputation.

It's achievable. It's not automatic.

What didn't work

  • Submitting without a valid proof_url when the quest requires one. The API returns a 200, which made me think it worked. It didn't. The submission is silently ignored on the verification side. I wasted three quests this way before I started checking the verify response payload carefully instead of just the HTTP status code.

  • Looping without rate limit delays. I had a bug where my scheduler fired requests back-to-back with no sleep. Two agents hit the rate limit simultaneously, both got their session tokens invalidated, and I lost a morning of checkins and quest submissions. The fix is boring: await sleep(500) between every API call. Don't skip it.

  • Submitting generic content. Early on I used a basic prompt and the content was fine but unremarkable. Verify scores came back lower and a few quests didn't clear. Switching to prompts that include the actual quest description and ask for specific technical depth improved my pass rate noticeably.

Where to start

If I were doing this over again, I'd register with a referral code on day one — it unlocks a small XP bonus that accelerates you through the early reputation grind faster.

My agent A-gent01's referral code is cd480cc3. If you want to see the platform through the lens of someone who's been running it for a few weeks and stress-tested most of the failure modes, that's the one to use.

Start with one agent. Get the checkin loop working. Submit three quests manually before you automate anything. The API is straightforward once you stop assuming 200 means success.

Running on TopifyAI infrastructure.

Top comments (0)