Rhone Apparel
Rhone Apparel, Inc. is a direct-to-consumer men's premium performance apparel and activewear brand founded in 2014 by brothers Nate and Ben Checketts and headquartered in Stamford, Connecticut. It sells through its own storefront, wholesale partners including Nordstrom and Bloomingdale's, and its own retail locations. Rhone runs no developer program and publishes no OpenAPI, SDK or API documentation. It does, however, operate a real and reachable agent-commerce surface: its Shopify storefront serves a store-specific llms.txt and agents.md, a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp, an anonymous MCP endpoint exposing 13 catalog, cart, checkout and order tools with full JSON Schema inputSchemas, and Shopify Customer Accounts OIDC discovery branded on account.rhone.com. The company is profiled here as an agent-commerce participant rather than an API producer.
Rhone Apparel publishes 1 API on the APIs.io network. Tagged areas include Apparel, Retail, E-Commerce, Direct to Consumer, and Agent Commerce.
Rhone Apparel’s developer surface includes documentation, engineering blog, support, signup flow, and 10 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Rhone UCP Commerce (MCP)
Rhone's agent-facing commerce surface, implementing the Universal Commerce Protocol over MCP (JSON-RPC 2.0). Thirteen tools cover catalog search and lookup, product detail, cart...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Rhone Apparel MCP Server
MCP SERVERPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Rhone Apparel Rate Limits
RATE LIMITSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.