GLP THREE — Developers

GLP THREE does not have a transactional API (ordering happens through Three International's own checkout). What's here is a small, public, read-only data surface for agents and integrators.

Quickstart

No API key or signup required — these are public GET endpoints.

curl https://glpthreelife.com/v1/product.json

Endpoints

• GET /v1/product.json — structured product data (ingredients, price, ordering link)
• GET /openapi.json — full OpenAPI 3.1 description of this surface
• GET /llms.txt — plain-language index of this site for AI agents
• GET /sitemap.xml — full page sitemap

Versioning

Versioning policy: URL path versioning (currently /v1/). Breaking changes will only ship under a new version path (/v2/, etc), never in place. Once a version is superseded, its responses will carry Sunset and Deprecation headers for a minimum of 90 days before it stops being served.

Rate limits

/v1/product.json is limited to 60 requests/minute per client. Every response includes RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers so you can self-throttle; a 429 includes Retry-After (seconds). This is enforced best-effort per edge node, not globally coordinated, so treat the stated limit as a ceiling to stay under rather than an exact global count.

Content negotiation

Any content page supports Accept: text/markdown for a lightweight Markdown representation, including this page. Unknown paths return a real HTTP 404 with a Markdown or JSON body depending on your Accept header.

No sandbox

There's nothing here that mutates data, so there's no separate sandbox environment — every endpoint above is safe to call directly.