0200project
We run an x402 seller in production. Sometimes that’s worth renting.
Two fixed-price engagements, both paid on delivery. What’s for sale is time and a production vantage point — not expertise you couldn’t assemble yourself, and not an opinion about whether your system is sound.
The arrangement, before the detail: fixed scope, fixed price, and you pay after you have the thing. If we don’t deliver what the engagement describes, you owe nothing and there is nothing to cancel — no deposit, no payment method held, nothing that recurs. How payment works →
Settlement diagnosis
$250–$500 in USDC · delivered within 72 hours of a yes
Everything we have observed about a specific failure, written up in one place: the payload class that gets rejected and the exact rejection as the SDK surfaces it, the divergences between facilitators that only a merchant running more than one would ever see, and the failure shapes we’ve learned to tell apart in production — verify-stage rejection, settle-stage failure, and the quiet one where a call is served but never settles.
It includes the dead ends. What we ruled out, what we tried that didn’t work, and where our own instrumentation was blind. These are observations with the evidence attached, not a judgement about whether your integration is correct — and the absence of an observation is not a statement that nothing is there.
A fair objection, pre-answered: some of this resembles bug reports you’d expect for free. The free version is the issues we file as a merchant anyway, and those keep coming either way. What’s for sale is the whole record in one document — payload-level, with the dead ends and the mitigations — which nobody writes up as an issue.
Integration, proven by settlement
$1,500–$2,000 fixed · one week
Your existing API sells over x402: the challenge, the facilitator wiring, settlement, reconciliation, and a payer harness so you can prove it yourself afterwards without asking us.
Acceptance is unfakeable and it isn’t ours to declare. The engagement is done when a real settlement lands on your own payout wallet. The receipt is the acceptance test. If that never happens, you owe nothing.
How the work reaches you
- As pull requests you review and deploy yourself, wherever it touches your code
- We never deploy to your production. A payment path carrying your settled revenue should stay under exactly one party’s control, and that party is not us
- With a rollback note, because a change you can’t reverse isn’t one you should merge
What this is not
- Not a review that issues a verdict. We report what we observed with the evidence for each observation. Nothing here certifies that a system is correct, safe, or compliant, and no absence of a finding should be read as clearance
- Not a retainer, and not ongoing. Each engagement is one agreed amount, once. Nothing renews, because nothing is held that could renew it
- Not a promise of availability. We don’t offer response times or uptime commitments on this work, and we’d rather say so than imply otherwise
- Not something you couldn’t do yourself. You could. What’s for sale is it being done this week while you build product — and if that isn’t worth the money right now, that’s a complete answer
Who is doing this?
The same operation that runs base-transaction-decoder — a live x402 seller on Base, settling through a keyless facilitator with a second configured as fallback, in production since August. The vantage point is the product: things only visible to a merchant actually taking payments through more than one stack. We are a small operation and we don’t pretend otherwise.
Can I see evidence of how you work?
Yes, on request. A third party ran our public payer harness end to end against us and published their own report of the experience with the on-chain settlement; separately, an independent conformance tester published a case study of our fix turnaround after putting us through their conformance pass. We’ll send both links if you ask — we’d rather hand them to you directly than point the whole internet at someone else’s thread.
How do I pay?
USDC on Base, settled on-chain over x402 — the settlement receipt is the invoice. Payment is due on delivery, never before. Other arrangements are possible on larger engagements; ask and we’ll tell you plainly what it involves. The mechanics are here, including the part that actually takes time if you’ve never held USDC on Base.
What if it goes wrong?
You owe nothing for work you didn’t receive, on either engagement. If money has moved and you didn’t get what you paid for, that’s ours to fix — email contact@0200project.com.