Developers

A public, read-only API and WebMCP tools for Jilian Garette Abangan's portfolio. No API key. No sign-up. JSON over HTTPS.

When to use it

You are hiring or vetting a freelance React, TypeScript and Supabase developer.
You need proof of shipped work: live products, roles, stack and case studies.
You want Jilian's own answer to a question about his experience or availability.
You need his contact details to start a conversation about a project.

Not a fit:

This is a portfolio, not a product. There are no accounts, plans or private data.
The API is read-only. You cannot book, pay or send messages through it. Email him.

Quickstart

The API is read-only, so production is the sandbox. Run any of these now.

curl https://2026.jilian.dev/api/profile

Endpoints

GET

/api/profileWho Jilian is: role, base, availability, career timeline and contact links.

GET

/api/projectsEvery project on /work: slug, title, summary, stack and live link.

GET

/api/projects/{slug}One project with its full case study in Markdown.

POST

/api/chatAsk Jilian a question. Answers in first person. 10 requests a minute.

POST

/api/agent/identityOptional anonymous agent token. Gives your agent its own chat rate limit.

API keys and auth

You need no API key. Every endpoint is public. An agent can mint an optional anonymous token at POST /api/agent/identity and send it as Authorization: Bearer <token>. The token gives the agent its own chat rate limit instead of sharing its IP address's limit. The steps are in auth.md.

WebMCP tools

In a browser with WebMCP, every page registers these tools through document.modelContext.registerTool():

get_profile: Jilian's profile, availability and contact links.
list_projects: Every project in the portfolio, newest work first.
get_project: One project's case study, by slug.
ask_jilian: Ask Jilian a question about his work and get his reply.

Machine-readable docs

Support

Questions or a bug? Email jiliangarette@gmail.com.