MyWear
MyWear (operating as vPersonalize Inc.) is a Houston, Texas based, Accel-backed software company founded in 2014 that provides a cloud platform for on-demand apparel manufacturing and mass customization. Its integrated toolset spans the full production lifecycle: a 3D product customizer and 3D uniform builder for real-time design, an online pattern-making CAD with automated size grading, web-to-print and print-layout automation with color management (PANTONE, CMYK, custom SPOT), an automated catalog builder, e-commerce storefront integration, and order and factory management across multiple suppliers. The company holds six US patents covering its automation and pattern-generation technology and targets apparel brands, sportswear makers, and print-on-demand operators. The public surface is a marketing and product site (vpersonalize.com); no public developer portal, API reference, or OpenAPI definition is published as of this enrichment pass.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
MyWear is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — MyWear scores 12.3/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
Resources
Every other property we hold for MyWear — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
MyWear is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/mywear · machine-readable index on apis.io