Chain x402-paid HTTP endpoints into automated workflows.
Resource providers earn USDC. AI agents bring their own wallet and pay per call.
Try it → · Docs · Discord · X / Twitter
x402.jobs is a no-code workflow builder where every node is a paid x402 HTTP endpoint.
Two sides of the marketplace:
- Resource providers wrap an LLM prompt, an HTTP API, or any existing endpoint behind an x402 paywall. They earn USDC every time it gets called — no infrastructure, no per-tenant billing, no API-key handout.
- Agents and consumers discover those resources, chain them into workflows, and pay USDC per call from their own wallet. No SaaS subscriptions, no rate-limit gymnastics, no integration code beyond an x402 client.
USDC settles on Solana and Base.
| Type | What it does |
|---|---|
| Claude prompt | A reusable Claude system prompt with typed parameters. Agents pay per generation. |
| OpenRouter model | Same idea, any OpenRouter-backed model. |
| HTTP proxy | Wrap any existing REST endpoint behind an x402 paywall. |
| Link existing x402 | Register an endpoint you already host elsewhere. |
Every resource gets a stable URL, a public listing, and SDK-grade metadata (extra.outputSchema, refund support, multi-network accepts).
git clone https://github.com/rawgroundbeef/x402.jobs.git
cd x402.jobs
pnpm install
cp apps/web/env.example apps/web/.env.local
cp apps/api/env.example apps/api/.env
# Fill in: Supabase URL/keys, WALLET_ENCRYPTION_SECRET,
# INTEGRATION_ENCRYPTION_SECRET (see apps/api/env.example
# for the full list).
pnpm dev
# → web: http://localhost:3010
# → api: http://localhost:3011
# → Inngest: http://localhost:8288Per-app fallbacks if pnpm dev misbehaves:
pnpm dev:web # web only
pnpm dev:api # api only
pnpm dev:inngest # Inngest dev server onlyRequirements: Node ≥ 22, pnpm@10.6.5 (pinned via packageManager), a Supabase project, a Solana RPC endpoint.
See apps/api/env.example for every supported environment variable.
x402.jobs/
├── apps/
│ ├── web/ # Next.js 15.5 frontend — deploys to Vercel
│ └── api/ # Express + Inngest workers — deploys to Railway
├── packages/
│ ├── sdk/ # @x402jobs/sdk — public npm package
│ └── ui/ # @x402jobs/ui — internal shared components
├── .github/workflows/ # CI — path-filtered per-app jobs
├── turbo.json
├── pnpm-workspace.yaml
└── vercel.json
The @x402jobs/sdk package gives you discovery, trust scoring, and resource-management helpers for any x402 client:
npm install @x402jobs/sdkFull SDK docs at x402.jobs/docs/developer.
- Web → Vercel (auto-deploys
main) - API → Railway (auto-deploys
main, builds viaapps/api/Dockerfile)
Both apps are deploy-independent. Path-filtered CI in .github/workflows/ci.yml only runs the jobs whose code changed.
- Getting started — register your first resource
- Developer guide — SDK reference
- Resource lifecycle — pricing, refunds, output schemas
- Examples — end-to-end workflows
- x402 protocol — the underlying payment-required HTTP standard
- Discord: discord.gg/BUcC28x6BX
- X / Twitter: @x402jobs
- Issues: github.com/rawgroundbeef/x402.jobs/issues
BSL 1.1 with an Additional Use Grant (Memeputer LLC as Licensor). Converts to Apache 2.0 on 2030-05-15.
In plain English:
- ✅ Use it for internal company workflows
- ✅ Self-host for your own projects
- ✅ Fork, modify, contribute back
- ❌ Don't run a hosted x402-payments-workflow service that competes with x402.jobs
See LICENSE for the legal text.
See CONTRIBUTING.md. Conventional Commits with phase scope (feat(31): …).
Vulnerability reports go through GitHub Private Vulnerability Reporting. See SECURITY.md for the full disclosure policy.