HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
waylaidwanderer
node-chatgpt-api
JavaScript2023–2023
waylaidwanderer / node-chatgpt-api

node-chatgpt-api

A client implementation for ChatGPT and Bing AI. Available as a Node.js module, REST API server, and CLI app.

2Distinct people
2Mentions
0Explicit recommenders
4.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A client implementation for ChatGPT and Bing AI. Available as a Node.js module, REST API server, and CLI app.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval2 dated mentions

Observed mentions: 2023-02-01 19:43:43 UTC to 2023-02-04 14:25:44 UTC.

012023-02-01 18:00:00 UTC to 2023-02-01 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 1, 18:002023-02-01 21:00:00 UTC to 2023-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 00:00:00 UTC to 2023-02-02 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 03:00:00 UTC to 2023-02-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 06:00:00 UTC to 2023-02-02 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 09:00:00 UTC to 2023-02-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 12:00:00 UTC to 2023-02-02 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 15:00:00 UTC to 2023-02-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 18:00:00 UTC to 2023-02-02 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-02 21:00:00 UTC to 2023-02-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-03 00:00:00 UTC to 2023-02-03 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-03 03:00:00 UTC to 2023-02-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 3, 03:002023-02-03 06:00:00 UTC to 2023-02-03 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-03 09:00:00 UTC to 2023-02-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-03 12:00:00 UTC to 2023-02-03 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-03 15:00:00 UTC to 2023-02-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-03 18:00:00 UTC to 2023-02-03 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-03 21:00:00 UTC to 2023-02-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-04 00:00:00 UTC to 2023-02-04 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-04 03:00:00 UTC to 2023-02-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-04 06:00:00 UTC to 2023-02-04 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-04 09:00:00 UTC to 2023-02-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-02-04 12:00:00 UTC to 2023-02-04 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 4, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 1, 18:002023-02-01 18:00:00 UTC2023-02-01 21:00:00 UTC101
Feb 1, 21:002023-02-01 21:00:00 UTC2023-02-02 00:00:00 UTC000
Feb 2, 00:002023-02-02 00:00:00 UTC2023-02-02 03:00:00 UTC000
Feb 2, 03:002023-02-02 03:00:00 UTC2023-02-02 06:00:00 UTC000
Feb 2, 06:002023-02-02 06:00:00 UTC2023-02-02 09:00:00 UTC000
Feb 2, 09:002023-02-02 09:00:00 UTC2023-02-02 12:00:00 UTC000
Feb 2, 12:002023-02-02 12:00:00 UTC2023-02-02 15:00:00 UTC000
Feb 2, 15:002023-02-02 15:00:00 UTC2023-02-02 18:00:00 UTC000
Feb 2, 18:002023-02-02 18:00:00 UTC2023-02-02 21:00:00 UTC000
Feb 2, 21:002023-02-02 21:00:00 UTC2023-02-03 00:00:00 UTC000
Feb 3, 00:002023-02-03 00:00:00 UTC2023-02-03 03:00:00 UTC000
Feb 3, 03:002023-02-03 03:00:00 UTC2023-02-03 06:00:00 UTC000
Feb 3, 06:002023-02-03 06:00:00 UTC2023-02-03 09:00:00 UTC000
Feb 3, 09:002023-02-03 09:00:00 UTC2023-02-03 12:00:00 UTC000
Feb 3, 12:002023-02-03 12:00:00 UTC2023-02-03 15:00:00 UTC000
Feb 3, 15:002023-02-03 15:00:00 UTC2023-02-03 18:00:00 UTC000
Feb 3, 18:002023-02-03 18:00:00 UTC2023-02-03 21:00:00 UTC000
Feb 3, 21:002023-02-03 21:00:00 UTC2023-02-04 00:00:00 UTC000
Feb 4, 00:002023-02-04 00:00:00 UTC2023-02-04 03:00:00 UTC000
Feb 4, 03:002023-02-04 03:00:00 UTC2023-02-04 06:00:00 UTC000
Feb 4, 06:002023-02-04 06:00:00 UTC2023-02-04 09:00:00 UTC000
Feb 4, 09:002023-02-04 09:00:00 UTC2023-02-04 12:00:00 UTC000
Feb 4, 12:002023-02-04 12:00:00 UTC2023-02-04 15:00:00 UTC101

What Hacker News says

2 sources
The real work happens here: it looks like this library has figured out the secret model name that allows you to make API calls to the ChatGPT model in the same way you would usually make calls to the other GPT-3 models: https://github.com/waylaidwanderer/node-chatgpt-api/blob/mai... That project's README (and the commit history to that README) tells the full story: sounds like people have been hanging out on Discord collaborating on reverse engineering ChatGPT: https://github.com/waylaidwanderer/node-chatgpt-api One thing to note: you still have to provide your own OpenAI API key in order to call the model, so if/when OpenAI decide to shut this hole down it will likely be easy for them to restrict who can call the model and potentially take measures against accounts that have used it in this way.
In Deploy your own GPT-3 API with Docker and fly

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.