Skullcandy
Skullcandy is a US consumer-audio brand that designs and sells headphones, wireless earbuds, gaming headsets, and Bluetooth speakers. Its e-commerce storefront at skullcandy.com runs on Shopify, and rather than a traditional developer program the brand exposes a modern agentic-commerce surface: an agent-facing llms.txt / agents.md, a Universal Commerce Protocol (UCP) merchant profile with a hosted Model Context Protocol (MCP) endpoint for catalog search, cart, checkout and fulfillment, a Shopify Customer Account API secured with OpenID Connect / OAuth 2.0 (including a customer-account MCP scope), and read-only storefront JSON endpoints for products and collections. This profile captures that agent- and API-facing surface as discovered on the live site.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Skullcandy the way a machine reads it — 7 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
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 — Skullcandy scores 23.2/100 (emerging), with a separate agent-readiness read of 25/100 (agent aware). 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
How we profile Skullcandy
Each block below is one kind of artifact we hold for Skullcandy. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 3
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Skullcandy Agentic Commerce (UCP)
Universal Commerce Protocol (UCP) merchant surface for the Skullcandy Shopify storefront. Agents discover capabilities at /.well-known/ucp and transact against a hosted MCP endp...
Skullcandy Customer Account API (Shopify)
Shopify Customer Account API for the Skullcandy store, secured with OpenID Connect / OAuth 2.0 (authorization code + PKCE). Scopes include customer-account-api:full and customer...
Skullcandy Storefront Data (read-only)
Unauthenticated read-only storefront endpoints for browsing catalog data: product JSON (/products/{handle}.json), collection JSON (/collections/{handle}/products.json), search, ...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
skullcandy-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Skullcandy — 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.
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
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
← All providers · Data indexed from github.com/api-evangelist/skullcandy · machine-readable index on apis.io