Home · Use cases · Jobs · Check an open-source model and its repository before you adopt it

Check an open-source model and its repository before you adopt it

For: machine-learning engineers and technical writers who pick a model and need to see how it is used. One run is 2 calls and 3 credits.

Get an API key   Run a step free

The job

Adopting a model means reading its card (task, library, licence, downloads, likes) and then checking the repository behind the tooling you will run it with, in two different places with two different layouts.

Web data or web intelligence?

Model and code pages are written for reading. Structured answers give you a model's task, library, licence, downloads last month, likes and whether it is gated, and a repository's title, description and owner, as fields you can filter on.

The calls, in order

StepCallWhat it gives youCreditsDocs
1POST /v1/developer/huggingface/modelthe model: task, library, licence, downloads last month, likes, gated or not2Fields
2POST /v1/developer/github/repoa repository in full: title, description, owner, created date1Call and code

What one run costs

fact The credits per call are the catalog's: 2 + 1 = 3 per run, so 3,000 credits per 1,000 runs. calculated At the plan prices on the pricing page that is about $23.88 per 1,000 runs on Production and $29.40 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/huggingface/model

The input: {"model_id":"bert-base-uncased"}. A real response had these fields.

FieldValue in that response
model_idgoogle-bert/bert-base-uncased
authorgoogle-bert
pipeline_tagfill-mask
library_nametransformers
downloads_last_month33,919,087
likes3,083
curl -X POST 'https://api.foxapis.com/v1/developer/huggingface/model' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model_id":"bert-base-uncased"}'

Step 2: 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"}'

All of it as one script

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

// 2 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/huggingface/model", {"model_id":"bert-base-uncased"});   // the model: task, library, licence, downloads last month, likes, gated or not
const step2 = await call("POST", "/v1/developer/github/repo", {"url":"https://github.com/torvalds/linux"});   // a repository in full: title, description, owner, created date
console.log({ step1, step2 });

What you could build

Limits, plainly

One model and one repository per call, each named by its identifier or address; the repository in our sample is a general example, not the model's own repository. Tested on 19 November 2026.

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

Other jobs: Track a product's open-source and launch momentum · 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 · 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