Human context. Machine-readable by design.

Bring your AI.
Get the whole picture.

Give your tools a connected account of my work: experience, education, skills, projects, contribution credit, and the sources behind them.

The pages you read here and the data your assistant reads come from the same shared records. My structured profile is a feature of this site, ready to use without an account or API key.

01 / Start with one link

Paste this URL into an assistant that can open web links, or use it directly in a script, hiring tool, or research workflow.

Open the data

02 / Give it useful context

A good introduction.

Copy this as a starting instruction. Add your own question—for example, how my experience relates to a collaboration, a research problem, or a role.

Shared records, several ways in

What you get.

23

Experience records

Current work and complete career history, with dates and the context behind each role.

83

Work & publications

Projects, writing, contributor credit, results, and links to the full onsite work and supporting sources.

50

Skills in context

Skills alongside education, credentials, and work. Degree completion and contribution status remain explicit.

Profile sources observed 2026-10-29. Individual publications and results retain their own dates and evidence boundaries. This is the public profile; it does not provide access to private accounts.

03 / Use it in your workflow

A small, open interface.

JSON

Structured profile

Fetch the complete profile in one request. Use the schema to discover fields and validate the response.

Profile JSON JSON Schema Schema version 2.3.0
BROWSER TOOL

get_professional_profile

In browsers that support the site’s tool registration, call this tool with an empty object. It returns {ok: true, profile: …} with the same profile.

Tool contract Agent manifest Read-only · No arguments · Browser support varies
Examples for developers

The JSON endpoint uses ordinary HTTP GET. The profile is the response body; the browser tool wraps it in profile.

For browser tools, use get_professional_profile(). An HTTP client should fetch the JSON endpoint above; the tool contract is a description, not a remote invocation endpoint.