Binske website screenshot

Binske

binske is a Colorado-born premium cannabis brand founded in 2015, producing flower and pre-rolls, live resin and live hash rosin concentrates, vape carts and all-in-ones, and edibles including chocolate bars and fruit gummies, sold through licensed dispensaries as a multi-state brand across Colorado, Florida, Michigan, New Jersey, New York and Washington. The company develops proprietary genetics with ONI Seed Co. and built its chocolate line around rare white cacao sourced in Peru, with packaging art by UK artist Martin O'Neill. binske operates no developer program and publishes no API of its own; its only machine-callable surface is the Shopify-native Universal Commerce Protocol MCP endpoint served from its direct-to-consumer storefront at shopbinske.com, which exposes catalog search, cart and checkout to agents and requires explicit human approval before payment.

Binske publishes 1 API on the APIs.io network. Tagged areas include cannabis, consumer-packaged-goods, direct-to-consumer, ecommerce, and retail.

Binske’s developer surface includes documentation, authentication, engineering blog, support, and 17 more developer resources.

21.7/100 emerging ▬ flat Agent 25/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs 2 MCP Servers
cannabisconsumer-packaged-goodsdirect-to-consumerecommerceretailshopifyagent-commerceucpmcpstorefront

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 21.7/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 7.3 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 1.5 / 12
Discoverability 8.7 / 10
Agent readiness — 25/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 0 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/binske: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

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

binske Storefront Commerce API (UCP / MCP)

Anonymous, publicly callable MCP server on binske's direct-to-consumer storefront host implementing the Universal Commerce Protocol shopping service. A live JSON-RPC 2.0 tools/l...

MCP Servers 2

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

binske-mcp.yml

MCP SERVER

Security Posture 2

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

Binske Authentication

3 schemes

SECURITY

Binske Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Binske Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

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

Company 3

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: binske
name: Binske
description: binske is a Colorado-born premium cannabis brand founded in 2015, producing flower and pre-rolls, live resin
  and live hash rosin concentrates, vape carts and all-in-ones, and edibles including chocolate bars and fruit gummies, sold
  through licensed dispensaries as a multi-state brand across Colorado, Florida, Michigan, New Jersey, New York and Washington.
  The company develops proprietary genetics with ONI Seed Co. and built its chocolate line around rare white cacao sourced
  in Peru, with packaging art by UK artist Martin O'Neill. binske operates no developer program and publishes no API of its
  own; its only machine-callable surface is the Shopify-native Universal Commerce Protocol MCP endpoint served from its direct-to-consumer
  storefront at shopbinske.com, which exposes catalog search, cart and checkout to agents and requires explicit human approval
  before payment.
image: https://binske.com/wp-content/uploads/2026/01/favicon-300x300.png
url: https://raw.githubusercontent.com/api-evangelist/binske/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-07'
modified: '2026-08-07'
tags:
- cannabis
- consumer-packaged-goods
- direct-to-consumer
- ecommerce
- retail
- shopify
- agent-commerce
- ucp
- mcp
- storefront
apis:
- name: binske Storefront Commerce API (UCP / MCP)
  description: Anonymous, publicly callable MCP server on binske's direct-to-consumer storefront host implementing the Universal
    Commerce Protocol shopping service. A live JSON-RPC 2.0 tools/list returned 13 tools with full JSON Schema draft 2020-12
    input schemas covering catalog search and lookup, product detail, cart lifecycle, checkout lifecycle and order retrieval.
    complete_checkout carries an idempotency key and requires contemporaneous buyer approval. The surface is emitted by the
    Shopify platform on binske's behalf, not authored by binske.
  humanURL: https://shopbinske.com/agents.md
  baseURL: https://shopbinske.com/api/ucp/mcp
  tags:
  - agent-commerce
  - ucp
  - mcp
  - ecommerce
  - shopify
  - cannabis
  properties:
  - type: MCPServer
    url: mcp/binske-mcp.yml
  - type: MCPServer
    url: mcp/binske-mcp-tools.json
  - type: Documentation
    url: https://shopbinske.com/agents.md
  - type: LLMsTxt
    url: llms/binske-llms.txt
  - type: Authentication
    url: authentication/binske-authentication.yml
  - type: OAuthScopes
    url: scopes/binske-scopes.yml
  - type: Conventions
    url: conventions/binske-conventions.yml
  - type: Idempotency
    url: conventions/binske-conventions.yml
  - type: DataModel
    url: data-model/binske-data-model.yml
  - type: AgentSkill
    url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/binske-domain-security.yml
- type: Website
  url: https://binske.com/
- type: Documentation
  url: https://shopbinske.com/agents.md
- type: MCPServer
  url: mcp/binske-mcp.yml
- type: LLMsTxt
  url: llms/binske-llms.txt
- type: WellKnown
  url: well-known/binske-well-known.yml
- type: Authentication
  url: authentication/binske-authentication.yml
- type: OAuthScopes
  url: scopes/binske-scopes.yml
- type: Conventions
  url: conventions/binske-conventions.yml
- type: Idempotency
  url: conventions/binske-conventions.yml
- type: Conformance
  url: conformance/binske-conformance.yml
- type: Lifecycle
  url: lifecycle/binske-lifecycle.yml
- type: DataModel
  url: data-model/binske-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Blog
  url: https://binske.com/explore/
- type: BlogRSS
  url: https://binske.com/feed/
- type: Support
  url: https://binske.com/contact/
- type: TermsOfService
  url: https://binske.com/terms-of-service/
- type: PrivacyPolicy
  url: https://binske.com/privacy-policy/
- type: Store
  url: https://shopbinske.com/
- type: SecondaryMarket
  url: https://forgeglobal.com/binske_stock/
x-enrichment:
  date: '2026-08-07'
  status: enriched
  artifacts_added: 18
  pass: local-v1
x-notes:
  api_surface_origin: binske runs no developer program of its own. The one machine-callable surface profiled here — the UCP/MCP
    endpoint, the /.well-known/ucp discovery document, llms.txt and agents.md — is emitted by the Shopify commerce platform
    on behalf of the store. It is recorded because it is genuinely served from a binske-controlled host and genuinely callable,
    not because binske publishes an API product. No OpenAPI, SDK, CLI, sandbox, webhook, changelog, status page, security.txt
    or A2A agent card exists on any binske host.
  probed: '2026-08-07'