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 is listed with 1 API on the APIs.io network. Tagged areas include Cannabis, Consumer Packaged Goods, Direct to Consumer, E-Commerce, and Retail.

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

🌐 Visit website 📡 Profile data on GitHub

22.5/100 emerging ▬ flat Agent 19/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 2 MCP Servers 1 Agent Skills

Cannabis Consumer Packaged Goods Direct to Consumer E-Commerce Retail Shopify Agentic Commerce Universal Commerce Protocol MCP Storefront

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 22.5/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 5.2 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 6.1 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 19/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/binske/"><img src="https://apis.io/badge/binske/card.svg" alt="Binske on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Developer Ergonomics scores 30.4 — up to +13.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/binske/apis.yml: open an issue on github.com/api-evangelist/binske to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Universal Commerce Protocol (UCP)

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

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 Storefront Commerce MCP Server

Anonymous, publicly reachable MCP server on binske's own storefront host (shopbinske.com), exposing the Universal Commerce Protocol (UCP) shopping service. A JSON-RPC 2.0 `tools...

MCP SERVER

Binske MCP Server

MCP SERVER

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

binske-agent-commerce

AGENT SKILL

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

4 scopes

SCOPES

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

MCPServer

LLMsTxt

WellKnown

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

Conformance

Lifecycle

DataModel

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

BlogRSS

BlogRSS

Other 2

Properties that don't map to a standard resource type

Store

Store

SecondaryMarket

SecondaryMarket

Source (apis.yml)

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.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
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.23'
created: '2026-08-07'
modified: '2026-08-07'
tags:
- Cannabis
- Consumer Packaged Goods
- Direct to Consumer
- E-Commerce
- Retail
- Shopify
- Agentic Commerce
- Universal Commerce Protocol
- MCP
- Storefront
tags_raw:
- 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:
  - Agentic Commerce
  - Universal Commerce Protocol
  - MCP
  - E-Commerce
  - Shopify
  - Cannabis
  tags_raw:
  - 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
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
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'

Binske API — frequently asked questions

Does Binske have an API?

Yes. APIs.io lists 1 API from Binske, including binske Storefront Commerce API (UCP / MCP).

How do I authenticate with the Binske API?

Binske documents its authentication (3 schemes). The details are profiled on APIs.io as Binske Authentication.

Does Binske have an MCP server?

Yes. APIs.io lists 2 MCP servers for Binske: Anonymous, publicly reachable MCP server on binske's own storefront host (shopbinske.com), exposing the Universal Commerce Protocol (UCP) shopping service. A JSON-RPC 2.0 `tools/list` call returned 20

Is the Binske API ready for AI agents?

Binske has a Kin Score of 22.5 out of 100 (emerging) and an Agent Readiness score of 19.2 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/binske"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/binske/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/binske/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.