MedPlus Mart API reference
MedPlus Mart catalogue: search, product prices, filters, categories and PIN codes.
The MedPlus Mart API has 5 endpoints, called the same way: POST /execute with the endpoint ID as capability and its fields as input, or pin MedPlus Mart in the MCP server and call each one as a tool. The data comes back as JSON in results[0].data, with what the call cost in billing.credits_charged.
The input most of them take is query. Every endpoint costs 1 credit per call, and a failed call costs nothing.
Endpoints
Open an endpoint for its input, the fields it returns and the request in cURL, Python and Node.js.
| Endpoint | What it returns | Price |
|---|---|---|
medplus.categories.list |
List the MedPlus Mart category tree with parent ids and depth, so a caller can pick a category and walk its products. | 1 credit |
medplus.category.products |
Read a MedPlus Mart category with brand, printed-MRP and stock filters, its sort orders and one page of up to 20 per call. | 1 credit |
medplus.pincode.check |
Resolve an Indian PIN code or area name to the MedPlus Mart localities the storefront serves, with each place id. | 1 credit |
medplus.product.get |
Read one MedPlus Mart product: selling price, printed MRP, membership price, pack size, composition, prescription need and stock. | 1 credit |
medplus.search.products |
Search MedPlus Mart medicines and health products with selling price, printed MRP, pack size, manufacturer and stock, one page of up to 20 per call. | 1 credit |
What to know
- Prices and stock are the default-catalogue values; the storefront publishes no per-PIN price or stock through these routes.
- Category filters work on brand and printed MRP; the route ignores a selling-price range, so price bands must use MRP.
- Substitutes are not returned: the field the storefront exposes was empty for every product sampled.
- Search results get fuzzier with depth, so search pages stop at page 10.
Something missing or unclear? Ask the team that builds the MedPlus Mart endpoints.