Developers
AURA Elite Nutrition API
A public, read-mostly HTTP API over the supplement catalog, delivery estimates and store details — plus an MCP endpoint for agent runtimes. No API key, no signup, no authentication on anything documented here.
- openapi.jsonOpenAPI 3.1 specification
- openapi.yamlSame document, YAML
- agent-instructions.mdWhen to use this store
- llms.txtStore context for LLMs
- sitemap.xmlEvery indexable URL
Authentication
None. Every endpoint on this page is public and read-mostly, so there is no key to manage and no token to rotate. Nothing here takes payment either: calculate_order_payloadprices a basket and returns a checkout link and a pre-filled WhatsApp message, and a human completes the purchase. Endpoints that do move money or touch a customer’s account sit behind a session and are deliberately absent from the specification.
Endpoints
| Method | Path | operationId | What it does |
|---|---|---|---|
| GET | /api/agent/tools | listAgentTools | The WebMCP manifest — every callable tool with its JSON Schema parameters. |
| POST | /api/agent/tools | invokeAgentTool | Run one tool by name and get its result. |
| POST | /api/agent/mcp | callMcpJsonRpc | Model Context Protocol bridge over JSON-RPC 2.0: tools/list and tools/call. |
| GET | /api/products | listProducts | Paginated, filterable catalog listing. |
| GET | /api/products/search | searchProducts | Typeahead search, at most six results. |
| GET | /api/combos | listCombos | Currently merchandised product bundles. |
| GET | /openapi.json | getOpenApiSpec | This API as an OpenAPI 3.1 document. YAML at /api/openapi.yaml. |
Agent tools
Each of these is invoked by name through POST /api/agent/tools, or through tools/call on the MCP endpoint. The parameter schema for each one is in the manifest and in the OpenAPI document.
- search_supplements
- Search authentic supplements by keyword, fitness goal, category, brand, budget, and real-time inventory availability.
- get_product_details
- Retrieve comprehensive specifications for a specific supplement: exact price, flavor and weight variants, stock counts, and clinical nutrition facts.
- check_delivery_pincode
- Estimate delivery turnaround, courier partner, and express dispatch eligibility for any 6-digit Indian PIN code.
- calculate_order_payload
- Calculate itemized cart totals, validate free shipping threshold (₹1,500+), and generate a 1-click WhatsApp order URL and checkout deep link.
- get_store_info
- Retrieve physical retail store details, official address in Muradnagar, operating hours, GPS directions, and customer support channels.
Example requests
curl -s https://auraelitenutrition.com/api/agent/tools \
-H 'Content-Type: application/json' \
-d '{
"tool": "search_supplements",
"parameters": { "query": "creatine", "maxPrice": 2000, "limit": 3 }
}'curl -sH 'Accept: text/markdown' https://auraelitenutrition.com/productsErrors
Every failure — including a 404 on an unmatched /api path — comes back as JSON, never as an HTML error page. Branch on errorCode; the hint field names the call that would have worked.
{
"success": false,
"error": "No supplement found matching 'nope'.",
"errorCode": "PRODUCT_NOT_FOUND",
"message": "No supplement found matching 'nope'.",
"hint": "Slugs are not guessable. Run search_supplements and use the 'slug' field from a result.",
"documentation": "https://auraelitenutrition.com/developers"
}Rate limits & caching
No per-key quota is enforced, because there are no keys. Keep sustained traffic under roughly 60 requests per minute per IP and cache catalog reads for at least 60 seconds; bursts beyond that may be throttled at the edge. Prices and stock are read live on every request, so do not cache a price for more than an hour before re-checking. To enumerate the catalog, paginate GET /api/products or read the sitemap rather than crawling product pages.
Using this from an agent
agent-instructions.md spells out when this store is the right thing to call — pricing an Indian supplement, checking real stock, estimating delivery to a PIN code — and, just as importantly, when it is not. Read it before wiring the tools into a planner. For the machine-readable surface, generate your function definitions from openapi.json rather than transcribing this page.
Something missing or wrong? Tell us.