FluxyMed Developer Portal

Public, read-only API for agents and integrations.

Everything published on fluxymed.com is also available as JSON and as Markdown. No account, no API key and no rate-limit negotiation: the API is public, read-only and served from the same dictionaries that render the website, so it can never disagree with the pages.

Last updated: 28 August 2026

Quickstart

Every endpoint answers an unauthenticated GET. Start with the health probe, then read the OpenAPI document to discover the rest.

Discover the API in two calls

curl https://fluxymed.com/api/health
curl https://fluxymed.com/openapi.json

Authentication and limits

There are no API keys, tokens or sign-up. Every endpoint is public and unauthenticated, and the OpenAPI document declares this explicitly with an empty security requirement list.

There is also no separate sandbox, and none is needed: the API exposes only information already published on the public website, and it rejects every write method with HTTP 405. Calling production is safe.

Responses set Access-Control-Allow-Origin: *, so browser-based agents can call the API directly.

Endpoints

Endpoint	Description	Parameters
GET /api/health	Service availability probe.	—
GET /api/site	Company, contact channels, locales and legal page URLs.	—
GET /api/faq	Frequently asked questions with their answers.	locale=es\|en (default es)
GET /api/pricing	The published plan and everything it includes.	locale=es\|en (default es)
GET /openapi.json	OpenAPI 3.1 description of this API. Alias: /api/openapi.json.	—

Markdown content negotiation

Every public page serves a Markdown representation to clients that ask for one, following the acceptmarkdown.com convention. Send Accept: text/markdown and you get text/markdown; charset=utf-8 back instead of HTML, at the same URL.

Negotiated responses carry Vary: Accept, Accept-Encoding so caches keep the two representations apart, and HTML responses advertise their Markdown alternate with a Link header using rel="alternate".

Quality values are honoured, and an Accept header that cannot be satisfied returns HTTP 406 rather than a surprise representation.

Read the home page as Markdown

curl -H "Accept: text/markdown" https://fluxymed.com/

Errors

Every response under /api/ is JSON, including errors. There are no HTML error pages in the API namespace.

code: Stable machine-readable identifier for the failure.
message: Human-readable explanation of what went wrong.
hint: A concrete action that resolves the error.
status: The HTTP status code, repeated in the body.
documentation_url: Where to look next.

A 404 from the API

{
  "error": {
    "code": "not_found",
    "message": "No API endpoint matches GET /api/nope.",
    "hint": "Fetch https://fluxymed.com/openapi.json for the list of available endpoints.",
    "status": 404,
    "documentation_url": "https://fluxymed.com/openapi.json"
  }
}

Error codes

not_found: No endpoint matches the requested path. HTTP 404.
method_not_allowed: The API is read-only; retry with GET, HEAD or OPTIONS. HTTP 405.
invalid_parameter: A query parameter is outside its accepted values. HTTP 400.
internal_error: Unexpected server-side failure. HTTP 500.

Machine-readable resources

https://fluxymed.com/openapi.json - OpenAPI 3.1 description of this API.
https://fluxymed.com/llms.txt - Index of the site for language models.
https://fluxymed.com/sitemap.xml - Every indexable URL.
https://fluxymed.com/robots.txt - Crawl policy. All AI agents are explicitly allowed.

Support

Questions about the API, or a field you need that is not exposed yet: write to ventas@fluxymed.com or message +1 829 204 0510 on WhatsApp.