💧 Moist as a Service 💧

The world's premier moisture detection API

What is this?

Moist as a Service analyzes your requests and determines if they're moist, wet, or dry. Because the internet needed this.

⚠️ This is a parody / novelty API in the style of No as a Service. It does fuzzy text matching against word lists for fun — it is not a real moisture sensor or a scientific measurement tool of any kind.

Response Codes

Examples

Moist Request (200)
curl https://maas.insecure.co.nz/cake
curl https://maas.insecure.co.nz/sponge
Wet Request (418)
curl https://maas.insecure.co.nz/ocean
curl https://maas.insecure.co.nz/api?q=swimming+pool
Dry Request (404)
curl https://maas.insecure.co.nz/desert
curl https://maas.insecure.co.nz/api?q=dust
Browser Request
Visit: https://maas.insecure.co.nz/sponge
Visit: https://maas.insecure.co.nz/waterfall

Browsers get pretty HTML responses!

How It Works

The service fuzzy matches your request path and query params against dictionaries of moist, wet, and dry things. Content negotiation means curl and API clients get JSON while browsers get HTML.

FAQ

Is this a real moisture sensor or scientific tool?

No. It's a parody/joke API inspired by projects like "No as a Service". It does fuzzy text matching against word lists, not any physical or scientific measurement of moisture.

How does the classification actually work?

It extracts text from the request's URL path, query parameters, and POST body, then fuzzy-matches (with 1-character typo tolerance) against three word dictionaries: moist, wet, and dry.

What do the response codes mean?

200 OK = matched "moist". 418 I'm a teapot = matched "wet" (too wet). 404 Not Found = matched "dry", or nothing at all (moist not found).

Do I get JSON or HTML back?

Content negotiation: curl/wget/httpie get JSON, browsers get a styled HTML page with the same classification.