HN Explorer

Show HN: X402 Agent Starter Kit: AI agents that pay for their own APIs (gitlab.com)

3 points by peiyaooo ↗ HN
Hey HN, we built a set of production-ready AI agent templates with x402 micropayments baked in.

The problem: agents that need multiple APIs face signup/KYC/key-management overhead that doesn’t scale. x402 replaces all of that with HTTP-native payments.

Currently supporting USDC on Base, more integrations soon.

The kit includes 5 agent templates (web scraper, image gen, search, translation, code review). Clone, configure a wallet, run. 93 tests passing. Built on Coinbase Developer Platform.

This is the first project from our “1 app per week” studio experiment.

Repo: https://gitlab.com/artificial-lab/x402-agent-starter Docs: https://x402-kit.vercel.app Protocol: https://x402.org

Would love feedback on the architecture and the agent templates. What x402 use cases would you want to see next?

5 comments

[ 2.3 ms ] story [ 27.1 ms ] thread
pylonai
Cool to see more x402 tooling emerging. We've been running a production x402 gateway (Pylon — pylonapi.com) with 20 capabilities live on Base mainnet: web extraction, search, translation, code execution, image gen, etc.

One thing we learned building it: the real value isn't just "agent pays for API" — it's eliminating the entire API key lifecycle. An agent discovers a capability, pays $0.001, gets the result. No signup, no billing dashboard, no rate limit negotiations.

The starter kit templates map well to what we expose. Happy to compare notes on architecture — especially around payment validation latency and how you handle retries on 402 responses.

alfredz0x
Nice work. I run x402 endpoints in production (httpay.xyz) — currently 100+ endpoints covering web scraping, search, image gen, LLM inference, etc. all behind 402 paywalls on Base USDC.

A few observations from the operator side:

1. Discovery is the real bottleneck. The protocol itself works well, but agents need a way to find x402 endpoints. We built an MCP server that lets Claude/other agents discover and call x402 APIs without hardcoding URLs. Your starter kit + an MCP discovery layer would be a strong combo.

2. Wallet UX matters more than you'd think. Most friction we see isn't the 402 handshake — it's agents managing wallet balance, gas, and chain selection. Curious how your CDP integration handles low-balance scenarios.

3. Testing against real endpoints: if anyone building with this kit wants live x402 endpoints to test against, httpay.xyz has a public catalog. Easier than spinning up your own server just to validate the client flow.

liad
would policylayer.com be helpful to you?
liad
Nice kit. One gap in x402 flows: no standard way to express "this agent can spend up to $X/day on these API categories." Payment primitive works, but the authorization/policy layer is ad hoc. Working on this at PolicyLayer — programmable spend policies for agent wallets.