Home · Use cases · Jobs · Track a product's open-source and launch momentum

Track a product's open-source and launch momentum

For: developer-relations, product-marketing and growth teams, for their own product or a competitor's. One run is 4 calls and 5 credits.

Get an API key   Run a step free

The job

You want to know whether a project is gaining or losing attention: who maintains it, how active the maintainer is, and what people said when it was posted for discussion. Doing that by reading web pages means one parser per site and a break every time a layout changes.

Web data or web intelligence?

Web data hands you the page and leaves the reading to you. Web intelligence hands you named fields: the repository's title and description, the maintainer's follower count and account age, a discussion thread's author, date and comment count. You store the fields and compare them from week to week.

The calls, in order

StepCallWhat it gives youCreditsDocs
1POST /v1/developer/github/repothe repository: title, description, owner, created date1Call and code
2POST /v1/developer/github/userthe maintainer: name, company, followers, public repositories, account age1Fields
3POST /v1/developer/hackernews/postthe discussion thread: title, author, date1Call and code
4POST /v1/developer/hackernews/commentsthe comments under it, with their authors2Fields

What one run costs

fact The credits per call are the catalog's: 1 + 1 + 1 + 2 = 5 per run, so 5,000 credits per 1,000 runs. calculated At the plan prices on the pricing page that is about $39.80 per 1,000 runs on Production and $49.00 on Builder (plan price divided by its monthly credits, times the credits). The Free plan gives 100 credits a month with no card.Formula

Your runs a month

Real responses, step by step

fact Captured from https://api.foxapis.com on 19 November 2026 with the documented sample input of each call; every value below is from that response, shortened where long. The nightly check on the status page lists each of these calls as working.

Step 1: POST /v1/developer/github/repo

The input: {"url":"https://github.com/torvalds/linux"}. A real response had these fields.

FieldValue in that response
titletorvalds/linux
author_nametorvalds
published_at2011-09-04T22:48:12Z
modified_at2026-11-18T20:23:07Z
likes256,193
views256,193
curl -X POST 'https://api.foxapis.com/v1/developer/github/repo' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://github.com/torvalds/linux"}'

Step 2: POST /v1/developer/github/user

The input: {"user_id":"torvalds"}. A real response had these fields.

FieldValue in that response
logintorvalds
nameLinus Torvalds
companyLinux Foundation
locationPortland, OR
public_repos12
public_gists1
curl -X POST 'https://api.foxapis.com/v1/developer/github/user' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"user_id":"torvalds"}'

Step 3: POST /v1/developer/hackernews/post

The input: {"url":"https://news.ycombinator.com/item?id=8863"}. A real response had these fields.

FieldValue in that response
titleMy YC app: Dropbox - Throw away your USB drive
author_namedhouston
published_at2007-04-04T19:16:40+00:00
published_at_unix1,175,714,200
likes104
comments_count71
curl -X POST 'https://api.foxapis.com/v1/developer/hackernews/post' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://news.ycombinator.com/item?id=8863"}'

Step 4: POST /v1/developer/hackernews/comments

The input: {"url":"https://news.ycombinator.com/item?id=8863"}. A real response had these fields.

FieldValue in that response
post_id8863
comments_count5
curl -X POST 'https://api.foxapis.com/v1/developer/hackernews/comments' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://news.ycombinator.com/item?id=8863"}'

All of it as one script

The same 4 calls chained, with a key placeholder. Swap the inputs for your own.

// 4 calls, one job run. Put your key in YOUR_API_KEY.
const KEY = "YOUR_API_KEY", BASE = "https://api.foxapis.com";
async function call(method, path, input) {
  const url = BASE + path + (method === "GET" ? "?" + new URLSearchParams(input) : "");
  const r = await fetch(url, { method, headers: { Authorization: "Bearer " + KEY, "Content-Type": "application/json" }, body: method === "GET" ? undefined : JSON.stringify(input) });
  if (!r.ok) throw new Error(path + " answered " + r.status);
  return r.json();
}
const step1 = await call("POST", "/v1/developer/github/repo", {"url":"https://github.com/torvalds/linux"});   // the repository: title, description, owner, created date
const step2 = await call("POST", "/v1/developer/github/user", {"user_id":"torvalds"});   // the maintainer: name, company, followers, public repositories, account age
const step3 = await call("POST", "/v1/developer/hackernews/post", {"url":"https://news.ycombinator.com/item?id=8863"});   // the discussion thread: title, author, date
const step4 = await call("POST", "/v1/developer/hackernews/comments", {"url":"https://news.ycombinator.com/item?id=8863"});   // the comments under it, with their authors
console.log({ step1, step2, step3, step4 });

What you could build

Limits, plainly

The repository and thread are named by their addresses; the maintainer by login. We tested one repository, one maintainer and one thread on 19 November 2026; what a field holds depends on what the source shows for that item.

Field lists and the rest of each data type: Every developer field. Single calls with code in six languages: task APIs.

Other jobs: Build a crypto and DeFi dashboard · Write a biomedical research brief · Analyse players and games for a gaming community · Watch artists for a label or a playlist curator · Give an AI agent structured answers instead of raw pages · Enrich a lead list with company and developer signals · Check a UK company and who controls it · Compare your app with a rival's on both phone stores · Profile a creator before a sponsorship · Check an open-source model and its repository before you adopt it · Profile a developer expert before you hire or sponsor · Check a person's claims before you hire or partner · Score a candidate against a role you describe · Prepare a sales brief on a company and score a prospect's message · Check how AI assistants show your domain · Research an investor before you pitch.

Source: live calls to https://api.foxapis.com on 19 November 2026. Values reflect that moment and those inputs. Credits per call are the catalog's.

How we calculate

Data: the FoxAPIs catalog and plans, read 19 November 2026. Every other figure on this page is copied from the record, not calculated by us.

Run this free, then pay per call

Free to start: 100 credits, no card. Then from $10. Credits you buy never expire. Use them at your own pace. Get my free key

One call costs 1 credit. That is $7.96 per 1,000 calls on the Production plan and $9.80 on Builder (plan price divided by its monthly credits). The Free plan gives 100 credits a month with no card.

Run this freeBuy credits

Building an AI agent?

See the MCP server