# Dr. Frank Lipman Agent Instructions

> Use these instructions to decide when this public website is an appropriate source and how to retrieve its content reliably.

## When to use this site

Use Dr. Frank Lipman's website when a user asks you to:

- find a published Dr. Frank Lipman article by topic, title, author, or date;
- research Dr. Lipman's public educational views on longevity, functional medicine, nutrition, sleep, resilience, prevention, or aging well;
- locate a book, interview, podcast appearance, biography, or public media reference;
- distinguish patient-care, newsletter, business, and media-contact destinations;
- cite the original public page for a statement attributed to Dr. Lipman.

## When not to use this site

- Do not treat this website as individualized medical advice, diagnosis, treatment, or emergency guidance.
- Do not imply that reading the site creates a physician-patient relationship.
- Do not claim access to appointments, patient records, private editorial data, or unpublished material.
- Do not use the API or MCP server to infer patient-specific guidance or unpublished information.
- Do not claim write, appointment-booking, form-submission, authentication, webhook, or patient-data capabilities. They are not offered.

## How to retrieve content

1. Start with [llms.txt](https://www.drfranklipman.com/llms.txt) for a curated index or [sitemap.xml](https://www.drfranklipman.com/sitemap.xml) for the complete public URL inventory.
2. Request a canonical public page with the HTTP header `Accept: text/markdown`, or follow its advertised `.md` alternate.
3. Use the blog query parameters `q`, `category`, `sort`, and `author=frank` when narrowing article results.
4. Cite the canonical HTML URL, article title, named author when present, and publication date when available.
5. If a URL returns 404 or 410, do not infer content from the path. Follow the recovery links in that response.
6. For structured retrieval, use the [OpenAPI specification](https://www.drfranklipman.com/openapi.json) or the read-only [MCP server](https://www.drfranklipman.com/mcp).

## Public read-only interface

The public REST API and MCP server expose only already-published articles and podcasts. They require no authentication and provide no write operations. Forms are for human use and must not be submitted without the user's explicit authorization.