Water Warriors: Turning Drought Data Into an AI-Powered Water Risk App

Water is becoming a traded commodity, but the tools around water risk still feel fragmented.

Markets live in one place. Drought indicators live somewhere else. Subsidy programs are buried in government workflows. AI assistants usually sit on top of generic SaaS data and do not understand the actual decision environment.

Water Warriors, also called Water Futures AI, was my attempt to bring those pieces into one interface.

The live demo is here: v0-water-warriors.vercel.app
The code is here: github.com/ravejedii/water-warriors

What It Is

Water Warriors is an AI-powered water risk management app built for the Crossmint hackathon.

The product combines four domains that usually do not meet in the same workflow:

water-sector markets
drought and climate indicators
blockchain-based subsidy payments
natural-language AI assistance

The app gives an agricultural stakeholder a single place to monitor water-related market exposure, review AI-driven futures signals, claim drought-triggered subsidies, and ask an assistant for help.

That sounds broad, but the underlying thesis is simple:

if water risk is financial risk, the interface should treat it like an operating system, not a PDF report.

What Shipped

The application includes:

a trading dashboard for water-sector equities through Alpaca paper trading
a drought subsidy flow using USDC transfers on Ethereum Sepolia via Crossmint
a futures analysis view grounded in a drought-prediction ML pipeline
a floating AI assistant for natural-language commands and explanations
a bring-your-own-key settings panel for live integrations
demo mode that works immediately with realistic sample data
a polished responsive dark UI for desktop and mobile

The important part is not just that these features exist.

The important part is that the app is usable without setup.

A visitor can open the demo and see a complete product experience immediately. If they want to connect real services, they can add API keys inside the app and individual features switch from demo mode to live mode.

No broken empty states. No mysterious config wall. No “trust me, it works on my machine.”

The Design Decision I Care About

The best technical decision in the project was the credential model.

Each feature resolves credentials in this order:

per-request browser-provided key
server environment variable
built-in demo data

That gives the public demo a real product feel while staying honest about what is live versus simulated.

If there are no keys, the app uses labeled demo data. If the user enters a key, that feature goes live. The keys stay in the browser and are sent per request; they are not saved server-side.

That matters because portfolio projects often fail at exactly this point. They either expose secrets, ship broken unauthenticated flows, or hide the actual product behind setup instructions no one will follow.

Water Warriors avoids that trap.

The Technical Stack

The app is built with:

Next.js 15
React 19
TypeScript
Tailwind CSS v4
shadcn/ui and Radix UI
Anthropic Claude for the assistant
Alpaca paper trading APIs
Crossmint REST APIs
Ethereum Sepolia for USDC subsidy transfers

The futures analysis is grounded in a research notebook using NQH2O water-index observations and GRIDMET drought indicators. The model work includes lagged and composite drought features across California water basins, then translates the output into trading signals inside the product.

This was not meant to be a perfect institutional-grade commodity platform.

It was meant to prove that climate data, financial exposure, subsidy automation, and AI assistance can live inside one coherent workflow.

Why Crossmint Matters Here

Crossmint makes the subsidy flow feel real.

The app models drought-triggered subsidies and uses Crossmint to move USDC on Sepolia. That turns the project from “dashboard about drought risk” into something closer to an operating product: detect risk, explain it, then trigger a payment workflow.

For a hackathon, that matters.

The blockchain layer is not decorative. It gives the subsidy system a concrete settlement mechanic and shows how climate-triggered assistance could become more programmable.

What I Would Build Next

The next version would go deeper on three things:

better risk scoring for farms, municipalities, and water-exposed businesses
richer agent workflows for claiming, hedging, and explaining water exposure
more live data integrations across markets, weather, and public subsidy programs

There is a real product direction hiding here.

Water is not just an environmental topic. It is an economic input, a financial risk, and increasingly a market signal. The tooling around it should be much better than scattered dashboards and static reports.

Final Thought

Water Warriors started as a hackathon build, but I refactored it like a portfolio product because the concept deserved more than a throwaway demo.

It is polished, responsive, type-safe, and clear about the line between demo mode and live integrations.

That is the standard I care about now: not just “can this idea work,” but can someone open it, understand it, and believe there is a real product hiding underneath?

For Water Warriors, I think the answer is yes.