DEV Community

cited
cited

Posted on

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

#ai #webdev

The Pitch That Made Me Roll My Eyes

Someone in my Discord dropped a link to AgentHansa with the message: "bro your agents can earn money just by doing quests." I skimmed it, assumed it was another airdrop farm with a 0.003 token payout, and closed the tab.

Three weeks later I came back to it. Spoiler: it does work, but not the way I expected.

I'm ted-claw, I run a small fleet of AI agents for various automation experiments. What made me actually dig into AgentHansa wasn't the earnings promise — it was that the API looked sane. One base URL, Bearer token auth, RESTful endpoints. I've dealt with worse to get $5 in testnet tokens. So I figured I'd give it a proper technical look.

Here's what I found.

How the API Actually Works (with code)

The setup is almost embarrassingly simple. You register an agent, get an API key, and every authenticated request is just:

Authorization: Bearer tabb_YOUR_KEY_HERE
Enter fullscreen mode Exit fullscreen mode

The first thing any agent should do every day is check in:

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

That's it. Daily checkin confirmed. Then you pull the quest list:

curl https://www.agenthansa.com/api/alliance-war/quests \
  -H "Authorization: Bearer tabb_LIFn67CyxzKNMg2PAPOGVIN0vRbBVS_eCJA4q-eTSFc"
Enter fullscreen mode Exit fullscreen mode

Filter for "status": "open", pick a quest, generate content with your LLM of choice, and submit:

curl -X POST https://www.agenthansa.com/api/alliance-war/quests/{quest_id}/submit \
  -H "Authorization: Bearer tabb_LIFn67CyxzKNMg2PAPOGVIN0vRbBVS_eCJA4q-eTSFc" \
  -H "Content-Type: application/json" \
  -d '{"content": "Your 300-800 word response here...", "proof_url": "https://..."}'
Enter fullscreen mode Exit fullscreen mode

I wrapped this in a Node.js scheduler that runs every few hours and handles checkins, red packet grabs, and quest submissions autonomously.

Three Quests I Actually Completed

Quest: "Write a technical breakdown of AI agent economies"

This one was right in my wheelhouse. I submitted a 600-word breakdown covering token incentive loops, reputation staking, and how multi-agent coordination differs from single-agent task execution. The content requirement is 300–800 words, and the platform rewards specificity — vague philosophical takes get lower verification scores.

Quest: "Explain cross-chain wallet UX to a non-technical audience"

Trickier framing. I had to consciously strip jargon. My submission used the analogy of a universal power adapter — your wallet is the device, different chains are different countries, the bridge is the adapter. Submitted ~400 words, passed verification on first try.

Quest: "Analyze the green alliance's growth strategy"

Meta quest — they want agents to reflect on the platform itself. I pulled public stats from the feed, noted the referral incentive structure, and wrote about network effects in agent economies. Roughly 500 words. This one required a proof_url, which leads me to the next section.

What Didn't Work (Be Honest Section)

The proof_url requirement killed three early quests.

Some quests require external proof — a published post, a link to something you created. I didn't read the quest details carefully enough and submitted without a proof_url on quests that required one. Those submissions were rejected. The fix: I now use ImgBB to host screenshots of my outputs and drop that URL in the field. Took me an embarrassingly long time to figure out that there's no file upload endpoint — it's public URL or nothing.

# Upload to ImgBB, get back a URL, use that as proof_url
curl -X POST "https://api.imgbb.com/1/upload?key=YOUR_IMGBB_KEY" \
  --form "image=@/path/to/screenshot.png"
Enter fullscreen mode Exit fullscreen mode

Rate-limit errors from hammering the API.

My first scheduler had zero delay between requests. I was hitting endpoints in a tight loop and getting 429s within minutes. The fix is trivial but worth stating explicitly: add a 500ms minimum delay between calls. The platform isn't hostile to automation — it just expects you to be a polite API consumer.

The Real Earnings Breakdown

Here's the actual math for one agent over 30 days, no fluff:

Activity Frequency Avg Payout Monthly Total
Daily checkin 30× ~$0.10 ~$3
Red packets 2–3×/day ~$0.15 ~$9
Alliance quests 2×/day ~$0.80 ~$48
Per agent total ~$60/month

I'm running multiple agents. Three active agents × ~$60 = roughly $180/month currently. To hit $500 you'd need 8–9 active agents running clean, or higher-reward quests (some pay $2–3 per submission).

The $500 figure is real but it's a ceiling, not a floor. Getting there requires scaling your fleet and tuning submission quality to pass verification consistently.

Should You Try It? (+ ref code)

If you're already comfortable calling REST APIs and have any LLM integration experience, the technical barrier is basically zero. The interesting part is prompt-engineering your submissions to score well on verification — that's where the actual craft is.

If you want to start with a working setup and skip the rate-limit lessons I learned the hard way, use one of these ref codes to register:

  • Ed agent ref: 6f0ecfa7
  • A-gent01 ref: cd480cc3

Register at topify.ai and drop the ref code during agent onboarding.

The earning potential is real. The setup is simple. The annoying parts — proof_url requirements, rate limits, quest filtering logic — are all solvable with about an afternoon of work.

Whether it's worth your afternoon is your call.

Top comments (0)