AtlasData is a live agent-native crypto data API platform: 60+ endpoints settling real per-call micropayments in USDC via x402 (Base) and BTC via L402 (Lightning), plus the largest public census of the x402 ecosystem (~33,400 paid endpoints indexed). This proposal funds the forward-looking x402→ZEC settlement rail: native Zcash support for HTTP 402 machine payments so agents can pay for data in shielded ZEC.
Thanks @idev9101-max for putting this together! The three payment milestones and the fact that hosting is already covered make the funding request easy to follow. Two questions from the budget and delivery side on my side:
You describe the reference deployment as permanent. What maintenance and support period is included in the $12,000 and how would ongoing costs be covered afterwards?
External verification currently comes in milestone 3. Could an external developer try the testnet integration during milestone 1 before moving to mainnet? That could help catch integration problems earlier.
I’d also distinguish a reviewer successfully making a test payment from another project actually adopting the SDK. Both are useful but they tell us different things about the outcome; for a grant of this size, a short account of what an external tester tried and what they found would be a useful start.
Thanks Julian — both points make sense. Proposed adjustments:
**Maintenance window + ongoing costs**
The $12,000 now includes a 12-month maintenance and support period from milestone 3 delivery: bug triage and fixes, dependency/runtime updates, and keeping the reference deployment live. After that period, ongoing hosting is cheap (~$10-15/month on a small VPS for the reference endpoint) and is covered by the service itself — the reference endpoint charges a fractional fee on x402 requests routed back to the ops wallet, so the deployment is self-funding once it has real traffic. If usage stays too thin to cover hosting, I commit to keeping the reference deployment up for at least 24 months regardless, funded from the grant margin rather than new money.
**Earlier external verification**
Agreed — I’ll restructure verification forward. Milestone 1 now ships the SDK against Zcash testnet plus a public testnet reference endpoint, and the milestone acceptance includes at least one external developer outside this project running the testnet integration and reporting what they tried and what broke. That gives us integration feedback before any mainnet work starts, not after.
**Verification criteria distinction**
Point taken — a successful reviewer payment and a real project adopting the SDK are different signals. The acceptance criteria will now read: milestone 1 = external testnet trial with a short written account of what the tester ran and found; milestone 3 = a documented external reviewer completing a live mainnet payment end-to-end, plus a report on outreach to candidate adopters (what was tried, what landed, what didn’t and why). I’ll treat “another project actually adopting the SDK” as a goal we chase in milestone 3 rather than a hard gate — adoption timing isn’t fully within my control, but the outreach account will be part of the deliverable.
I’ll update the application text with these changes shortly.
Thanks @idev9101-max - these changes address my questions! Treating external adoption as a goal rather than a payment condition seems fair, with the testing and outreach results documented. Would be great indeed if you could carry the maintenance commitments and revised acceptance criteria into the application so they’re clear when the milestones are reviewed.