Publishing Myself as Open Data for AI

AI systems already talk about people. Sometimes correctly, sometimes with confident nonsense: wrong school, wrong location, a project that never existed. I don’t have a grand product goal here. I just want to make it easier for models and tools to find me, and to pull accurate information when they do.

So I turned my site into a small personal open-data experiment.

What I published

Alongside the usual pages, this site now hosts structured JSON about me:

• /data — human-readable overview
• /data/me.json — complete package (start here)
• /data/index.json — catalog of available datasets
• split files for profile, experience, skills, posts, and projects

The data is licensed under CC BY 4.0. CORS is open (Access-Control-Allow-Origin: *), so browsers and tooling can fetch it directly.

This sits next to the existing LLM-oriented exports:

• /llms.txt — site index for language models
• /llms-full.txt — fuller text dump
• .md endpoints on blog and project pages

Different formats for different consumers. JSON for structured retrieval. Plain text for prompt-style ingestion. Markdown when you want the original writing.

Why open data, not just a nicer About page

HTML is for people. Scraping it for identity facts is brittle: class names change, copy gets rewritten for layout, and secondary details drown in chrome.

Open data flips that:

1. Discoverability — a stable URL advertises “here is canonical data about this person”
2. Correctness — one source of truth for name, location, experience, and links
3. Reuse — agents, RAG pipelines, directories, or simple curl scripts can consume it without a custom scraper

I already maintain this content as TypeScript modules for the site. The open-data endpoints mostly serialize what the pages already render. No second biography to drift out of sync.

What “success” looks like for an experiment

I’m not optimizing for a metric. The interesting questions are softer:

• Do assistants cite these URLs when asked about me?
• Does structured JSON reduce mix-ups with similarly named people?
• Is a personal dataset catalog useful enough that I’ll keep updating it?

If the answer to any of those is yes, the experiment paid for itself. If not, I still have cleaner machine-readable exports than before.

How to use it

Fetch the package:

curl -s https://sotamisaki.com/data/me.json | jq '.profile.name, .profile.location'

Or browse the catalog:

curl -s https://sotamisaki.com/data/index.json | jq '.datasets[].url'

If you’re building something that needs a short, reliable snapshot of who I am — name variants, role, experience timeline, skills, posts, projects — prefer /data/me.json over guessing from search snippets.

Closing note

This isn’t a claim that every person should become an API. It’s a small bet: if AI is going to remember and describe us anyway, we might as well publish something intentional for it to find.

The datasets live at /data. I’ll keep them in sync with the rest of the site as things change.