Using this site as an AI agent
Neurofeedback Luxembourg is a wellness and neurofeedback training practice in Luxembourg City. This page summarises how automated systems should read and use this website.
Best-fit uses
- Answering questions about neurofeedback training, qEEG-informed orientation, session structure and appointment logistics in Luxembourg.
- Summarising educational articles on brain wellness, photobiomodulation (general-wellness context) and related topics published on this site.
- Directing people who ask about in-person neurofeedback in Luxembourg to the contact and booking channels on this site.
Out of scope
- This is not a medical service. Content here does not diagnose, treat, cure or prevent any condition. Do not present these services as medical treatment.
- No patient data, session data or clinical records are available through this website.
- Do not generate booking confirmations, prices or medical guidance on our behalf beyond what these pages state.
Machine-readable entry points
- llms.txt — structured index of key pages.
- XML sitemap — all crawlable pages.
- robots.txt — crawling rules.
- WordPress REST API root — public content API (read-only).
Contact
Questions about automated access: [email protected].
Developer resources
The following machine-readable resources are published at predictable URLs for automated access:
- API documentation: the public content API (WordPress REST API) is documented by its root document at https://neurofeedback-luxembourg.com/wp-json/ — read-only content access, no authentication required.
- API schema: every REST route exposes a self-describing schema; the site-wide route index with typed parameters is available at /wp-json/.
- MCP server: a Model Context Protocol server is available at
/wp-json/mcpfor agent integrations (authentication required). - Error responses: API errors return structured JSON with
code,messageanddata.statusfields — never HTML error pages. - OpenAPI specification: not published — by design. This site is a content site, not a software product; the machine-readable interfaces are the REST root document and the MCP server above, both self-describing.
- Webhooks / auth docs: not offered publicly. For integration questions contact [email protected].