~/djzs/build $ cat offer.txt
Agents are already paying for API calls with USDC over x402. Most APIs cannot receive that payment: no MCP surface, no 402 challenge, no discovery file, no receipt. I build the missing layer in two weeks, at a fixed price, from a stack I have already run in production on my own domain. You get the code, the keys, and the runbook. I get out of the way.
Your existing endpoints wrapped as an MCP server on Cloudflare Workers, an x402 v2 paywall in front of the routes you choose (USDC on Base, CDP facilitator, funds settle payer → your wallet), /.well-known/x402.json, llms.txt, OpenAPI, agent card, Bazaar listing submitted. Deploy runbook included.$3,500 · 10 working days · one paid route; +$600 per additional route
Every paid response carries an EIP-712 hash of the request and an EAS attestation on Base under your own schema, from an attester wallet you control. Plus a static verifier page so a customer, a court, or a DAO can recompute the receipt without trusting you.$2,500 · 5 working days · add-on to Agent-ready API, or standalone on an API that already exists
For a physical or local business: a signed /.well-known/sifr0.json (services, prices, hours, booking method, policies) so an agent shopping on a customer's behalf can find you, quote you, and act. Includes registry listing at sifr0.dev and one revision.$400 · 3 working days · no code on your side
Monthly: dependency and Worker-runtime updates, facilitator and schema changes tracked, discovery files re-validated against the current x402 spec, a health probe with alerts, and one hour of changes. Cancel any month.$600 / month · starts after delivery · optional
Scope is written before money moves. Anything not on the scope sheet is a second engagement, not a surprise.
verify_pm_trade and verify_perp_trade at 2.00 USDC each, non-custodial EIP-3009 settlement, out-of-scope requests refused free. An unpaid request returns the 402 challenge and settles nothing. Try it: GET https://mcp.djzs.ai/x402/verify_pm_trade.intent_hash plus an EAS attestation on Base from a dedicated attester, on every paid verdict since 2026-09-01. Recompute any of them at djzs.ai/verify./.well-known/x402.json, llms.txt, OpenAPI, agent card, verified Base app registration, all on this site, all free to inspect.DAY 0 30-minute call · I read your API · scope sheet written and signed · 50% invoiced DAY 3 MCP server on a staging Worker · you call it from Claude or Cursor · nothing paid yet DAY 7 x402 gate live on staging · first 402 challenge · first USDC settles to YOUR wallet, not mine DAY 10 production deploy from your Cloudflare account · discovery files live · runbook + probe script · remaining 50% invoiced · keys were yours the whole time
Source is committed to a repo you own. Secrets are set in your Cloudflare account by you, from the runbook. I never hold a wallet key, an API key, or a deploy token past the call where you type it in.
You hold every key. That is not a courtesy, it is the design.
Trading advice or signals. Custody of funds or keys. Token launches. Guarantees of agent traffic or revenue. Building on a chain other than Base without a written reason. If your ask is one of those, I will say so on the Day 0 call and point you elsewhere.
Send these three lines by DM to @Djzs_ai on X:
1. What the API does, in one sentence. 2. Who should be able to call it (humans, your own agents, anyone's agents). 3. When you need it live.
You get a yes-or-no on fit within one working day and a scope sheet within three. Two engagements open at a time; the page says so here when both are taken.
Send the three linesPlumbing first. Then the traffic.