# Huckberry

> Huckberry is an American direct-to-consumer online retailer of men's apparel, outdoor gear and lifestyle goods, founded in 2010 by Andy Forch and Richard Greiner and headquartered in San Francisco with offices in Austin and Columbus. It pairs a first-party e-commerce storefront with a large editorial operation (the Huckberry Journal) and an in-house brand portfolio.

> API surface: none published. As of 2026-08-22 Huckberry publishes no developer portal, no API
> reference, no SDKs and no machine-readable specification (OpenAPI, AsyncAPI, GraphQL SDL, Postman).
> `api.huckberry.com`, `developer.huckberry.com`, `developers.huckberry.com`, `partners.huckberry.com`,
> `status.huckberry.com` and `mcp.huckberry.com` do not resolve in DNS. The company's public GitHub
> organization holds eight repositories, seven of them forks of third-party Ruby e-commerce gems
> (Solidus AvaTax, Affirm, Paperclip, omniauth-slack, rubocop-git) plus a Looker block — an internal
> storefront engineering footprint, not a published platform. This file is generated by API Evangelist
> from public pages; it is not published by Huckberry.

## Company

- [Huckberry](https://huckberry.com/): Storefront and editorial home. Served behind a Cloudflare managed challenge — automated clients receive HTTP 403 on every path.
- [Contact](https://huckberry.com/contact-us): Company contact page.
- [Terms of Service](https://huckberry.com/terms)

## Partner and affiliate

- [Affiliate program](https://huckberry.com/affiliates): Huckberry's affiliate program.
- [Partnerize signup](https://signup.partnerize.com/signup/en_us/huckberry): Affiliate tracking and reporting are operated by the Partnerize network, not by Huckberry. Any programmatic affiliate access is a Partnerize API against a Partnerize account, not a Huckberry API.
- [Advertise with us](https://huckberry.com/advertise-with-us): Media and sponsorship inquiries.

## Support

- [Huckberry Support](https://help.huckberry.com/hc/en-us): Zendesk-hosted help center (43 published articles as of 2026-08-22).
- Zendesk Help Center API (vendor-operated, readable anonymously on Huckberry's tenant host):
  `https://help.huckberry.com/api/v2/help_center/en-us/articles.json` — HTTP 200. This is Zendesk's
  contract running under Huckberry's subdomain, NOT a Huckberry-authored API. It exposes help-center
  content only: no catalog, no cart, no orders, no account data.

## Source code

- [Huckberry Inc on GitHub](https://github.com/Huckberry): Eight public repositories, no first-party API, SDK or specification.

## API Evangelist profile

- [apis.yml](https://raw.githubusercontent.com/api-evangelist/huckberry/refs/heads/main/apis.yml): Machine-readable APIs.json profile of this company.
- [Domain security probe](https://raw.githubusercontent.com/api-evangelist/huckberry/refs/heads/main/security/huckberry-domain-security.yml): TLS/HSTS/DNSSEC/CAA/SPF/DMARC observations.
- [Well-known probe](https://raw.githubusercontent.com/api-evangelist/huckberry/refs/heads/main/well-known/huckberry-well-known.yml): Every `/.well-known/*` path probed, with the status each returned.

## Notes for agents

- Do not assume an integration path. There is no public API, no OAuth surface, no webhooks, no MCP server, no A2A agent card and no `.well-known` discovery document on any Huckberry host.
- Every path on `huckberry.com` returns HTTP 403 with `cf-mitigated: challenge` to non-browser clients, including `/robots.txt`, `/llms.txt`, `/sitemap.xml` and all `/.well-known/*` paths. Absence of a document on that host is therefore unconfirmed, not measured.
- `/products.json`, `/cart.js`, `/api/mcp`, `/.well-known/ucp` and `/api/2026-04/graphql.json` were probed for a Shopify-style agentic commerce surface. All returned the same 403 challenge; nothing indicates Huckberry runs on Shopify.
- The only anonymously readable machine surface on a Huckberry host is the Zendesk Help Center API above, and it belongs to Zendesk.