hotheadhacker

no-as-a-service: Return Random Rejection Reasons via an API

No-as-a-Service is a small JavaScript API that returns a random rejection reason as JSON. Use the hosted endpoint for playful “no” responses in apps and bots, or self-host it with Node.js and Express.

View on GitHub Compare
Stars
8k
Forks
497
Stars, last 30 days
+28

Our take

Health score

27/100

How it is scored
Activity
19
Community
49
Issues
21
Pull requests
20

+28 stars in the last 30 days

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

8,028

Forks

501

Change since Nov 19, 2026: +3 stars·0 forks

Overview

No-as-a-Service (NaaS) provides a single API endpoint for getting a random reason to say no. Responses range from generic to creative and humorous, giving applications a ready-made rejection message instead of requiring their own collection of phrases.

It suits developers adding a lighthearted response to an app, bot, or integration. The project can be used through its hosted endpoint or run locally; it is not intended as a general-purpose decision or moderation service.

Key Features

  • Returns a random rejection reason from a GET /no request.
  • Responds with JSON containing a reason field.
  • Includes more than 1,000 rejection reasons in reasons.json, according to the README.
  • Offers a hosted API at naas.isalman.dev/no.
  • Documents a rate limit of 120 requests per minute per IP for the hosted API.
  • Supports self-hosting with Node.js and Express, with a configurable port.
  • Uses Express rate limiting and includes a GitHub Codespaces and VS Code devcontainer setup.

Use Cases

  • App developers can provide playful rejection text when a user action cannot proceed or is declined.
  • Bot and chat-integration authors can add a random response to a command such as /no.
  • Developers building demos or prototypes can use a simple JSON endpoint to test response-handling flows.
  • Teams can self-host the service when they want control over deployment or local access to the endpoint.

Getting Started

To run it locally, clone the repository, then install dependencies and start the server:

npm install
npm start

The local endpoint is http://localhost:3000/no. See the README for setup details and options such as changing the port.

Considerations

  • The hosted service documents a limit of 120 requests per minute per IP. Check its availability and limits before relying on it in production.
  • Self-hosting requires Node.js and npm, and the documented implementation uses Express and express-rate-limit.
  • The API returns a random phrase, not a context-aware or authoritative explanation for a rejection. Review the responses for fit before using them in sensitive or professional workflows.
  • The repository reports 70 open issues. This is a project activity signal, not a measure of issue severity or support guarantees.

Found this useful?

Share it with someone who would like no-as-a-service.