Weedmaps
Weedmaps is a cannabis discovery and ordering marketplace connecting consumers with dispensaries, delivery services, and brands. For its business customers it publishes a partner integration API suite - a Menu API for keeping a retailer's product menu, pricing, and availability in sync with their point-of-sale, a Brand Catalog API for mapping and enriching menu items against the Weedmaps brand and product taxonomy, a Taxonomy API for categories, cannabinoids, strains, terpenes, and discovery tags, and an Orders API for receiving and updating online orders in a partner POS. The developer documentation is public, but production access is partner-gated - integrators apply by email, receive OAuth2 client-credentials credentials and a test listing, and a Listing Owner must grant access. New integrations are noted as not currently being onboarded, so the endpoints below are documented but modeled from the public reference rather than exercised against a live account.
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 Weedmaps the way a machine reads it — 8 machine-readable artifacts across 4 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 — Weedmaps scores 26.3/100 (emerging), with a separate agent-readiness read of 16/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 Weedmaps
Each block below is one kind of artifact we hold for Weedmaps. 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 4
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.
Weedmaps Menu API
Keep a retailer's Weedmaps menu in sync with their point-of-sale. Retrieve menus and menu items, and create, retrieve, update, delete, and upsert-by-external-ID menu items to pu...
Weedmaps Brand Catalog API
Sync or map the Weedmaps catalog of Brands and Brand Products to an internal catalog to improve menu-item search relevance and discoverability. Retrieve all brands, a single bra...
Weedmaps Taxonomy API
Read-only reference taxonomy used to enrich menu items - retrieve cannabinoids, categories (flat and tree), strains, terpenes, and discovery tags. Linking menu items to these ta...
Weedmaps Orders API
Receive and manage online Weedmaps orders directly in a partner POS. Update order status, retrieve applicable discounts, retrieve order schedule time windows, and retrieve docum...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Weedmaps Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Weedmaps Finops
FINOPSSecurity 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 Weedmaps — 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 2
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/weedmaps · machine-readable index on apis.io