For Agents
Programmatically retrieve access token, retrieve brands. Covers 25 operations with oauth2 authentication.
Use for: I need to access token, I want to brands, Search for a brand, Find all a brand's product catalog
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Weedmaps API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fweedmaps.com%2Fweedmaps" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fweedmaps.com%2Fweedmaps" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Weedmaps API.
Retrieve Access Token
Manage e commerce data programmatically
Integrate Weedmaps API into automated workflows
Query and filter Weedmaps API records by parameters
GET STARTED
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Weedmaps Public API for managing cannabis menus, brands, products, orders, and taxonomy data. The API exposes 25 endpoints secured with oauth2 authentication.
Monitor Weedmaps API operational status and events
Patterns agents use Weedmaps API for, with concrete tasks.
★ E-Commerce Operations
Use the Weedmaps API to perform e commerce operations programmatically. The API provides 25 endpoints covering core functionality including retrieve access token, retrieve brands, retrieve a brand.
Call POST /auth/token to retrieve access token
Automated Auth Management
Automate auth operations by combining multiple Weedmaps API endpoints. Agents can retrieve brands and then retrieve a brand in a single workflow.
Call GET /brands to retrieve brands, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Weedmaps API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.
Search Jentic for 'retrieve access token', load the operation schema, and execute with Jentic-managed credentials
25 endpoints — weedmaps public api for managing cannabis menus, brands, products, orders, and taxonomy data.
METHOD
PATH
DESCRIPTION
/auth/token
Retrieve Access Token
/brands
Retrieve Brands
/brands/{brand_id}
Retrieve a Brand
/brands/{brand_id}/products
Retrieve a Brand's Product Catalog
/products/{id}
Retrieve a Brand Product
/products/{id}/reviews
Retrieve Brand Product Reviews
/menus
Retrieve Menus
/menus/{menu_id}
Retrieve a Menu
/auth/token
Retrieve Access Token
/brands
Retrieve Brands
/brands/{brand_id}
Retrieve a Brand
/brands/{brand_id}/products
Retrieve a Brand's Product Catalog
/products/{id}
Retrieve a Brand Product
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Weedmaps API by hand means running its OAuth2 token flow, keeping the token fresh across the brand and menu endpoints, and handling retries yourself. Through Jentic you install once, import Weedmaps from the API Directory, store the OAuth2 credentials once, and your agent calls it.
Permission scoping
Weedmaps puts the brand id in the URL path (/brands/{brand_id}/...), so a rule can pin your agent to one brand: it can read that brand and its products and nothing else. You choose the operations it may call, so listing every brand or reading arbitrary menus is not included unless you add them.
Credential isolation
Your Weedmaps OAuth2 credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a brand's products' or 'read a menu', and Jentic returns the matching Weedmaps operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Weedmaps API through Jentic.
What authentication does the Weedmaps API use?
The Weedmaps API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I retrieve access token with the Weedmaps API?
Yes. Use the POST /auth/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Weedmaps API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I retrieve access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve access token'. Jentic returns the matching Weedmaps API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Weedmaps API have?
The Weedmaps API exposes 25 endpoints covering auth, brands, menu items operations.
/products/{id}/reviews
Retrieve Brand Product Reviews
/menus
Retrieve Menus
/menus/{menu_id}
Retrieve a Menu