gitwtfhub

wtf is api.near.ai-retirement?

nearai/api.near.ai-retirement — explained in plain English

Analysis updated 2026-07-18 · repo last pushed 2025-10-31

JavaScriptAudience · developerComplexity · 1/5QuietSetup · easy

TL;DR

A tiny Cloudflare Worker that responds to any request to the old NEAR AI API with a clear 'this service is gone' message instead of silently timing out.

Mindmap

mindmap
  root((repo))
    What it does
      Retirement notice
      Returns HTTP 410
      Intercepts all requests
    Tech stack
      Cloudflare Workers
      JavaScript
      Wrangler
    Use cases
      Deprecate an API cleanly
      Signal shutdown clearly
      Avoid confused timeouts
    Audience
      Developers
    Notes
      Retired Oct 31 2025
      Minimal cost to run
    Setup
      Test with Wrangler
      Deploy to Cloudflare

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

See exactly what code powers a clean 'API retired' response, as a template for deprecating your own service.

REASON 2

Test locally with Wrangler and deploy a lightweight worker that replaces a shut-down backend.

REASON 3

Understand why an old NEAR AI integration now returns a 410 Gone instead of timing out.

What's in the stack?

Cloudflare WorkersJavaScriptWrangler

How it stacks up

nearai/api.near.ai-retirement3rd-eden/ircb.ioa15n/a15n
LanguageJavaScriptJavaScriptJavaScript
Last pushed2025-10-312016-11-162019-04-07
MaintenanceQuietDormantDormant
Setup difficultyeasyeasyeasy
Complexity1/52/52/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

Just a Cloudflare Worker, test locally with Wrangler, no other infra needed.

Yoink these prompts

Prompt 1
Show me how this Cloudflare Worker intercepts requests and returns an HTTP 410 response.
Prompt 2
Help me write a similar retirement-notice worker for an API I'm shutting down.
Prompt 3
Explain how to test this Worker locally with Wrangler before deploying it.

Frequently asked questions

wtf is api.near.ai-retirement?

A tiny Cloudflare Worker that responds to any request to the old NEAR AI API with a clear 'this service is gone' message instead of silently timing out.

What language is api.near.ai-retirement written in?

Mainly JavaScript. The stack also includes Cloudflare Workers, JavaScript, Wrangler.

Is api.near.ai-retirement actively maintained?

Quiet — no commits in 6-12 months (last push 2025-10-31).

How hard is api.near.ai-retirement to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is api.near.ai-retirement for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.

Other repos in this lane