Spent the weekend at the Algorand Builders Berlin hackathon turning our existing product into something an AI agent can pay for directly. Wanted to share what we built since the agentic-commerce + x402 angle is still pretty new.

The idea: ZapResume is a resume tool (ATS scoring, resume patches, cover-letter generation) that real people use through a WhatsApp bot. The problem: an AI agent doing someone’s job hunt can’t use a WhatsApp bot or fill out a signup form. So we added a channel built for agents — they pay per call in USDC on Algorand and get the work back. No login, no human, no card.

How it works:

	•	An agent hits our endpoint, gets an HTTP 402 with the price and our pay-to address  
	•	It pays USDC on Algorand testnet (settled via the GoPlausible x402 facilitator)  
	•	It retries with the payment, and gets the deliverable back  
	•	The interesting bit: our /apply endpoint bundles score + patch + cover letter into one atomic payment — the agent buys the whole job application in a single transaction instead of three separate calls

A couple of things I’m happy with:

	•	The agent has a real allowlist guardrail — it refuses to pay any address that isn’t pre-approved, before it signs anything. Felt important for the “what stops a rogue agent draining a wallet” question.  
	•	Network fee is \~0.001 ALGO per payment, which is what makes per-call micropayments actually viable — a fraction of a cent to settle a $0.27 charge.

Honest status: this is a hackathon build on testnet — real x402 flow, real on-chain settlement, real tx receipts on Lora, but test USDC. Mainnet is the next step, not done yet.

Code’s here if anyone wants to poke at it: https://github.com/sanju1v4/zap-agent

Happy to answer anything about the x402-on-Algorand setup — the TypeScript SDK side was the trickiest part to get right and I learned a lot.

made our resume product (ZapResume) agent-payable with x402 on Algorand — built at Algorand Builders Berlin