Jane (iHeartJane)
Jane Technologies (iHeartJane) is a cannabis ecommerce and marketplace platform that powers real-time online menus, point-of-sale and kiosk checkout, order and reservation flows, and the Jane Universal Product Catalog for 2,500+ dispensaries and brands across the United States and Canada. Jane exposes a documented HTTP API (the Jane API, published as Swagger at api.iheartjane.com/jane-api-docs) for retrieving live store menu products and generating access tokens, and a partner Digital Merchandising SDK (Jane DM SDK) for embedding MyHigh-powered personalization and sponsored-product widgets into a retailer's own menu. Both surfaces are partner-gated - access requires approval and credentials from a Jane account representative - so the endpoints listed here are modeled from Jane's public documentation rather than exercised against a live, open, unauthenticated API.
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.
API Evangelist profiles Jane (iHeartJane) the way a machine reads it — 3 machine-readable artifacts across 2 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 — Jane (iHeartJane) scores 12.7/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
How we profile Jane (iHeartJane)
Each block below is one kind of artifact we hold for Jane (iHeartJane). 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 2
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.
Jane Menu Products API
Jane's documented HTTP API (published as a Swagger UI at api.iheartjane.com/jane-api-docs) for retrieving live store menu products and for generating the access tokens used to a...
Jane Digital Merchandising SDK (Jane DM SDK)
The Jane DM SDK is a TypeScript/JavaScript library (usable in client-side React/Angular/Vue and server-side Node.js/Express apps) that embeds MyHigh-powered personalization and ...
Security Posture 1
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.
Resources
Every other property we hold for Jane (iHeartJane) — 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
Access & Security 1
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/iheartjane · machine-readable index on apis.io