Developers

Solo Developing developer resources

Everything on solodeveloping.com can be read by programs and AI agents: a read-only JSON API, an OpenAPI description, an llms.txt guide and a Markdown version of every page. No key, no account and no authentication are needed.

Solo Developing API

A static, read-only JSON API with Fabien Chung’s profile, services, products and articles, in English and French. The base URL is https://solodeveloping.com/api/. Responses are UTF-8 JSON and can be fetched from any origin (Access-Control-Allow-Origin: *).

GET /api/ — Index of every resource and where the description lives
GET /api/profile — Identity, contact details and services
GET /api/projects — Founded products and their technical components
GET /api/articles — Articles and short posts with their HTML and Markdown URLs

curl https://solodeveloping.com/api/profile

OpenAPI description

The API is described by an OpenAPI 3.1 document, in JSON and in YAML. It is also listed in the RFC 9727 API catalog, which every page advertises in a Link header (rel="api-catalog").

/openapi.json — OpenAPI 3.1, JSON (also at /api/openapi.json)
/openapi.yaml — OpenAPI 3.1, YAML (also at /api/openapi.yaml)
/.well-known/api-catalog — API catalog (application/linkset+json)

Errors

Errors are RFC 9457 problem details (application/problem+json) with a machine-readable code and a hint on how to fix the request. Unknown API paths answer 404 with the code not_found; methods other than GET, HEAD and OPTIONS answer 405 with the code method_not_allowed. Anywhere else on the site, a request sent with Accept: application/json also gets its 404 as JSON.

{
  "type": "about:blank",
  "status": 404,
  "title": "Not Found",
  "code": "not_found",
  "detail": "No API resource exists at this path.",
  "hint": "List the available resources at https://solodeveloping.com/api/ …",
  "documentation": "https://solodeveloping.com/openapi.json"
}

Authentication and limits

There is no authentication: the API only serves public data. Responses are static files delivered through a CDN and there are no published rate limits; please cache what you fetch. The current version is 1.0.0, given in info.version of the OpenAPI document.

Pages as Markdown

Request any page with Accept: text/markdown, or add .md to its address (index.html.md for / and /fr/), to get a clean Markdown version without navigation or scripts. Unknown pages answer 404 with a Markdown body.

curl -H 'Accept: text/markdown' https://solodeveloping.com/about

Site guides

/llms.txt — Guide for AI agents with every key page
/sitemap.xml — Every public URL
/robots.txt — Crawler policy; AI crawlers are allowed

What you can do with it

The API lets tools answer questions about Solo Developing without scraping HTML. A recruiter's assistant can read Fabien Chung's services and contact details from /api/profile. An AI agent comparing freelance developers in Montréal can list his products and their technical stack from /api/projects. A reading list or newsletter tool can pick up new articles from /api/articles, with their publication dates and Markdown sources.

Every resource is a static file, so responses are fast, cacheable and identical for every client. Nothing is personalised and no data about the caller is stored.

Why an agent-ready portfolio

More and more people find developers by asking an AI assistant instead of a search engine. When ChatGPT, Claude or Perplexity is asked for a Flutter or full-stack developer in Montréal, it reads pages like this one. Clean Markdown, a documented API and an llms.txt guide make that reading reliable: the assistant can quote accurate facts instead of guessing from a JavaScript bundle.

The same building blocks work for any product site or SaaS: content negotiation, an OpenAPI description, problem details for errors and an API catalog. They take a few days to add and make a site usable by agents without a dedicated integration. To make your own site or app agent-ready, see the AI developer services or get in touch.

AI developer services — AI features in production apps, multi-LLM pipelines and workflow automation
Contact — Describe your project and get an answer within 24 hours

Support

Questions about the API, or a response that looks wrong: write to hello@solodeveloping.com.

hello@solodeveloping.com