IST
Public JSON · Cloudflare Pages Functions · Version 2

The wire /api

Everything published on this site, as JSON: profile, security research areas and methodology, the five products, the research papers, credentials, skills and links. The pages and the API read the same data file, so they cannot disagree.

20Endpoints
19Commands
5Products
3Papers
27Credentials
v2Version
Quickstart

Request a route
Read the JSON

Every response uses the same envelope: ok, data and meta with the version and a timestamp. Pick a command to run it against the live API in the console.

Me
Work
Meta
GET /api
Requesting /api …
idle
Endpoint index

Every route

All GET except the contact form, all CORS-open, all cached at the edge for five minutes. Run any of them in the console above.

Use it

curl · fetch · python · command

No keys, no sign-up. The envelope is stable across versions and the data is the same the pages render.

curl
curl -s https://abhnv.in/api/summary | jq
curl -s https://abhnv.in/api/security | jq '.data.method'
curl -s https://abhnv.in/api/projects/clex-ai | jq
curl -s "https://abhnv.in/api/search?q=authorization" | jq
fetch (browser)
const res = await fetch("https://abhnv.in/api/projects");
const { ok, data, meta } = await res.json();
if (!ok) throw new Error("API error");
console.log(data.map((p) => `${p.title} · ${p.liveUrl}`), meta.version);
python (requests)
import requests

base = "https://abhnv.in/api"
areas = requests.get(f"{base}/security").json()["data"]["areas"]
for a in areas:
    print(a["title"], "·", a["short"])
command surface
// One endpoint, pick the command by name
const cmd = "security"; // summary, projects, research, links, search, help
const url = `https://abhnv.in/api/command?cmd=${cmd}`;
const { ok, data } = await fetch(url).then((r) => r.json());
Response shape

One envelope

Success

{
  "ok": true,
  "data": …,
  "meta": {
    "version": "2.0.0",
    "build": "2026-09-02",
    "generatedAt": "2026-09-02T10:21:08.000Z",
    "source": "abhnv.in/api",
    "docs": "https://abhnv.in/api",
    "cmd": "profile"
  }
}

Error

{
  "ok": false,
  "error": "Unknown command \"foo\".",
  "hint": "Available: profile, skills, projects, …",
  "meta": {
    "version": "2.0.0",
    "generatedAt": "2026-09-02T10:21:08.000Z",
    "cmd": "foo",
    "commands": ["profile", "skills", "…"]
  }
}
Why it exists

One data file, two readers

Single source

The pages and the API import the same file. A change to a product, a credential or a research area is live in both at once.

Read only

Every route is GET. The only write is the contact form, and it accepts nothing but a message.

Edge cached

Responses are cached for five minutes with stale-while-revalidate, so embeds stay fast and a burst of traffic never reaches a function.

What is not here

No deployment metadata, no request geography, no reports, no private programs. The API publishes what the site publishes and nothing more.

Built by Abhinav Raj on Cloudflare Pages Functions · Need a field that is missing?