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
| Step | Call | What it gives you | Credits | Docs |
|---|---|---|---|---|
| 1 | POST /v1/developer/github/repo | the repository: title, description, owner, created date | 1 | Call and code |
| 2 | POST /v1/developer/github/user | the maintainer: name, company, followers, public repositories, account age | 1 | Fields |
| 3 | POST /v1/developer/hackernews/post | the discussion thread: title, author, date | 1 | Call and code |
| 4 | POST /v1/developer/hackernews/comments | the comments under it, with their authors | 2 | Fields |
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.
| Field | Value in that response |
|---|---|
title | torvalds/linux |
author_name | torvalds |
published_at | 2011-09-04T22:48:12Z |
modified_at | 2026-11-18T20:23:07Z |
likes | 256,193 |
views | 256,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.
| Field | Value in that response |
|---|---|
login | torvalds |
name | Linus Torvalds |
company | Linux Foundation |
location | Portland, OR |
public_repos | 12 |
public_gists | 1 |
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.
| Field | Value in that response |
|---|---|
title | My YC app: Dropbox - Throw away your USB drive |
author_name | dhouston |
published_at | 2007-04-04T19:16:40+00:00 |
published_at_unix | 1,175,714,200 |
likes | 104 |
comments_count | 71 |
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.
| Field | Value in that response |
|---|---|
post_id | 8863 |
comments_count | 5 |
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
- A weekly row per project in a sheet or database: maintainer followers, public repositories, thread comment count
- An alert when a competitor's maintainer account or discussion thread jumps
- A launch-day report that pulls the thread and its comments in one run
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
- Cost per run and per 1,000 runs: The credits of each call in the run, added up (the catalog's credits per call), times 1,000 for 1,000 runs.
- Dollar figures: The plan's monthly price divided by its monthly credits, times the credits. Prices come from the plans file at build time and are never typed.
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.
Building an AI agent?
- The FoxAPIs MCP server gives your agent every tool through one connection.
- Per-call pricing in credits: you pay for the calls your agent makes, with no seats.
- Free plan: 100 credits a month, no card, no monthly fee.