Loading
Loading
Every Aurex catalog read is a public, CORS-open JSON endpoint. Built for AI agents (already allowlisted in robots.txt for ChatGPT, Claude, Perplexity, Gemini, Brave), integration partners, and the Telegram bot.
| Method | Path | Description |
|---|---|---|
| GET | /api | Discovery — list every endpoint with sample params + bot deep link. |
| GET | /api/health | Smoke check + integration presence flags. |
| GET | /api/catalog | Full machine-readable catalog dump. |
| GET | /api/stacks?slug=… | All stacks (or single by slug) with itemized retail vs stack savings. |
| GET | /api/coa?id=… | All released Janoshik COAs (or single batch detail). |
| GET | /api/search?q=… | Cross-search products + stacks + batches. |
| GET | /api/recommendations?goal=… | Map a research goal keyword to a stack + supporting peptides. |
| GET | /api/orders/[id]?email=… | Order status (email-gated, timing-safe). |
| GET | /api/research-data/[slug] | Per-SKU research reference for AI grounding (mechanism + applications + citations). |
| GET | /products-md/[slug] | Per-PDP markdown alternate for clean LLM tokenization. text/markdown content type. |
| GET | /products/[slug].md | LLMs.txt 2.0 convention — append .md to any PDP URL. Rewrites to /products-md/[slug] internally. |
| GET | /stacks-md/[slug] | Per-stack markdown alternate with savings math + per-component mechanism summaries. |
| GET | /stacks/[slug].md | LLMs.txt 2.0 convention — append .md to any stack URL. Rewrites to /stacks-md/[slug] internally. |
| GET | /wiki/peptide/[slug].md | LLMs.txt 2.0 — markdown alternate for any wiki peptide page (same body as /products-md/[slug]). |
| GET | /wiki/stack/[slug].md | LLMs.txt 2.0 — markdown alternate for any wiki stack page (same body as /stacks-md/[slug]). |
| GET | /api/wiki-graph | Full wiki edge list (nodes + typed edges) as JSON. Agents do graph traversal without HTML scraping. |
All Aurex products are research-grade compounds for in-vitro laboratory research only. Not for human or veterinary use. Not FDA approved.
API responses include catalog metadata (SKUs, prices, batch COAs, stack composition) but never dosing guidance, protocols, or therapeutic claims. Integrations should preserve this posture in any downstream copy.