LifeStyles Healthcare

LifeStyles Healthcare Pte Ltd is a global sexual wellness company that owns the LifeStyles condom and personal lubricant brands, tracing its origin to the condom business founded by Eric Ansell in Richmond, Australia in 1905. The company sells a broad range of latex and non-latex condoms, personal lubricants, and pleasure products across North American and international markets, and holds the LifeStyles trademarks and intellectual property across multiple jurisdictions. Its North American direct-to-consumer storefront at lifestyles.com runs on Shopify and exposes a genuinely agent-native commerce surface: a published llms.txt and agents.md, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, a live UCP shopping MCP endpoint for agent-driven catalog search, cart and checkout, and Shopify Customer Accounts OpenID Connect for buyer-scoped access. There is no traditional developer portal or first-party REST API program.

LifeStyles Healthcare is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Healthcare, Sexual Wellness, Consumer Packaged Goods, and E-Commerce.

LifeStyles Healthcare’s developer surface includes documentation, authentication, engineering blog, support, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

23.3/100 emerging ▬ flat Agent 18/100 agent aware Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs 1 MCP Servers

Company HealthcareSexual WellnessConsumer Packaged Goods E-Commerce Agentic Commerce MCP Shopify Retail

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 23.3/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 6.1 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.7 / 9

Regulatory Posture 4.9 / 15

Agent readiness — 18/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/lifestyles-healthcare/"><img src="https://apis.io/badge/lifestyles-healthcare/card.svg" alt="LifeStyles Healthcare on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Operational Transparency scores 0.0 — up to +13.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/lifestyles-healthcare/apis.yml: open an issue on github.com/api-evangelist/lifestyles-healthcare to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Agent Skills

measured — observed by APIs.io (published)

Universal Commerce Protocol (UCP)

measured — observed by APIs.io (shopify)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

LifeStyles US UCP Shopping (MCP)

The LifeStyles US store implements the Universal Commerce Protocol for agent-driven commerce. Agents discover the merchant profile at /.well-known/ucp and then call the JSON-RPC...

LifeStyles US Storefront JSON

Unauthenticated read-only JSON endpoints over the LifeStyles US Shopify storefront - product listings, individual products, collections, search and cart state - which the store'...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

LifeStyles Healthcare MCP Server

LifeStyles US operates a live Universal Commerce Protocol (UCP) shopping MCP endpoint for agent-driven commerce over its Shopify storefront. The endpoint was probed on 2026-07-1...

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lifestyles Healthcare Authentication

3 schemes

SECURITY

Lifestyles Healthcare Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Lifestyles Healthcare Scopes

4 scopes

SCOPES

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

AgentSkill

MCPServer

WellKnown

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Conformance

Lifecycle

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: lifestyles-healthcare
name: LifeStyles Healthcare
description: 'LifeStyles Healthcare Pte Ltd is a global sexual wellness company that owns the LifeStyles condom and personal
  lubricant brands, tracing its origin to the condom business founded by Eric Ansell in Richmond, Australia in 1905. The company
  sells a broad range of latex and non-latex condoms, personal lubricants, and pleasure products across North American and
  international markets, and holds the LifeStyles trademarks and intellectual property across multiple jurisdictions. Its
  North American direct-to-consumer storefront at lifestyles.com runs on Shopify and exposes a genuinely agent-native commerce
  surface: a published llms.txt and agents.md, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, a
  live UCP shopping MCP endpoint for agent-driven catalog search, cart and checkout, and Shopify Customer Accounts OpenID
  Connect for buyer-scoped access. There is no traditional developer portal or first-party REST API program.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://cdn.shopify.com/s/files/1/0610/3810/0706/files/lifestyles-logo_726b0e33-aa28-4543-ac4a-34ce08153d2a.png
url: https://raw.githubusercontent.com/api-evangelist/lifestyles-healthcare/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- hillhouse
x-tier: enriched
x-tier-reason: agent-commerce-surface
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Healthcare
- Sexual Wellness
- Consumer Packaged Goods
- E-Commerce
- Agentic Commerce
- MCP
- Shopify
- Retail
tags_raw:
- Company
- Healthcare
- Sexual Wellness
- Consumer Packaged Goods
- E-Commerce
- Agentic Commerce
- Model Context Protocol
- Shopify
- Retail
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- name: LifeStyles US UCP Shopping (MCP)
  description: The LifeStyles US store implements the Universal Commerce Protocol for agent-driven commerce. Agents discover
    the merchant profile at /.well-known/ucp and then call the JSON-RPC MCP endpoint to search the catalog, build a cart,
    and drive a checkout to completion. Payment always requires explicit buyer approval.
  humanURL: https://lifestyles.com/llms.txt
  baseURL: https://lifestyles.com/api/ucp/mcp
  tags:
  - Commerce
  - Agentic Commerce
  - MCP
  - Universal Commerce Protocol
  tags_raw:
  - Commerce
  - Agentic Commerce
  - MCP
  - UCP
  properties:
  - type: MCPServer
    url: mcp/lifestyles-healthcare-mcp.yml
  - type: Documentation
    url: https://lifestyles.com/agents.md
  - type: Authentication
    url: authentication/lifestyles-healthcare-authentication.yml
  - type: ErrorCatalog
    url: errors/lifestyles-healthcare-problem-types.yml
  - type: Conventions
    url: conventions/lifestyles-healthcare-conventions.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
- name: LifeStyles US Storefront JSON
  description: Unauthenticated read-only JSON endpoints over the LifeStyles US Shopify storefront - product listings, individual
    products, collections, search and cart state - which the store's own agent instructions document as the read-only browsing
    surface.
  humanURL: https://lifestyles.com/llms.txt
  tags:
  - Catalog
  - Product
  - E-Commerce
  tags_raw:
  - Catalog
  - Products
  - E-Commerce
  properties:
  - type: Documentation
    url: https://lifestyles.com/llms.txt
  - type: Conventions
    url: conventions/lifestyles-healthcare-conventions.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: storefront-json
common:
- type: DomainSecurity
  url: security/lifestyles-healthcare-domain-security.yml
- type: Website
  url: https://lifestyles.com
- type: Documentation
  url: https://lifestyles.com/llms.txt
- type: LLMsTxt
  url: llms/lifestyles-healthcare-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: MCPServer
  url: mcp/lifestyles-healthcare-mcp.yml
- type: WellKnown
  url: well-known/lifestyles-healthcare-well-known.yml
- type: Authentication
  url: authentication/lifestyles-healthcare-authentication.yml
- type: OAuthScopes
  url: scopes/lifestyles-healthcare-scopes.yml
- type: Conventions
  url: conventions/lifestyles-healthcare-conventions.yml
- type: ErrorCatalog
  url: errors/lifestyles-healthcare-problem-types.yml
- type: Conformance
  url: conformance/lifestyles-healthcare-conformance.yml
- type: Lifecycle
  url: lifecycle/lifestyles-healthcare-lifecycle.yml
- type: Blog
  url: https://lifestyles.com/blogs/sexual-health-safe-sex
- type: Support
  url: https://lifestyles.com/pages/contact
- type: TermsOfService
  url: https://lifestyles.com/policies/terms-of-service
- type: PrivacyPolicy
  url: https://lifestyles.com/policies/privacy-policy
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

LifeStyles Healthcare API — frequently asked questions

Does LifeStyles Healthcare have an API?

Yes. APIs.io lists 2 APIs from LifeStyles Healthcare, including LifeStyles US UCP Shopping (MCP) and LifeStyles US Storefront JSON.

How do I authenticate with the LifeStyles Healthcare API?

LifeStyles Healthcare documents its authentication (3 schemes). The details are profiled on APIs.io as Lifestyles Healthcare Authentication.

Does LifeStyles Healthcare have an MCP server?

Yes. APIs.io lists 1 MCP server for LifeStyles Healthcare: LifeStyles US operates a live Universal Commerce Protocol (UCP) shopping MCP endpoint for agent-driven commerce over its Shopify storefront. The endpoint was probed on 2026-07-19 and responded to JSON

Is the LifeStyles Healthcare API ready for AI agents?

LifeStyles Healthcare has a Kin Score of 23.3 out of 100 (emerging) and an Agent Readiness score of 18.2 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lifestyles-healthcare"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lifestyles-healthcare/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lifestyles-healthcare/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.