THE WORK DOESN’T STOP. NEITHER DO WE.GYMWEAR FOR THE EVERYDAY PURSUIT.
TSUYO
Back to collection

Tsuyo API & Agent Docs

When to use Tsuyo

Use Tsuyo’s public API to find gymwear by name or category, compare MYR prices and sizes, read fit and care descriptions, or check whether checkout and delivery are configured. The API and MCP server expose public information only. They cannot create a bag, place an order, charge a card, inspect customer records or administer the store. Illustrative pieces are explicitly marked preview and must not be recommended as available for purchase.

No authentication, account or API key is required for these read-only endpoints. Customer account and payment workflows remain in the storefront. Do not send a Supabase token, Stripe key or customer email to the public API. Recheck store status before discussing a purchase; successful catalog discovery is not a stock reservation.

REST endpoints

GET /api returns the API index. GET /api/products accepts q (up to 100 characters), category (men, women or unisex), limit (1–50; default 20) and offset (0–10000; default 0). GET /api/products/{id} returns one public piece. GET /api/store returns checkout, payment and shipping status. GET /api/pages?path=/contact returns a public page as Markdown inside JSON. All prices use integer minor units: 14900 MYR means RM 149.00. The OpenAPI 3.0.3 document specifies operations, parameters and response schemas.

Use GET for reads, HEAD for headers and OPTIONS for CORS preflight. Unsupported methods return 405. API failures use application/problem+json (RFC 9457), with status, code, message and resolution. Invalid parameters return 400, missing resources 404, and unavailable store data 503 with Retry-After. Respect Retry-After and avoid rapid retries. Product pages and store data are fetched anonymously; user sessions never enter a public response.

curl 'https://tsuyo.vercel.app/api/products?q=tee&category=men&limit=5'
curl -H 'Accept: text/markdown' https://tsuyo.vercel.app/

MCP connection

Connect an MCP client to https://tsuyo.vercel.app/mcp using Streamable HTTP. The server uses the official MCP SDK, negotiates supported protocol versions and returns JSON responses. Initialize the client, then list tools. POST requests accept application/json and text/event-stream. This server is stateless and does not issue session IDs; GET returns 405 because it offers no unsolicited event stream.

The tools are search_products, get_product, get_store_status and read_page. They have typed inputs and outputs and read-only annotations. Public discovery metadata at /.well-known/mcp and /server.json follows the MCP Registry server.json schema. Publishing this metadata does not mean Tsuyo is listed or verified in a third-party registry. Browser clients with an Origin header must use Tsuyo’s origin; server-to-server clients need no Origin header.