canonical: https://jentic.com/apis/weedmaps.com/weedmaps

# Weedmaps API

Weedmaps Public API for managing cannabis menus, brands, products, orders, and taxonomy data. The API exposes 25 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically retrieve access token, retrieve brands. Covers 25 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Retrieve Access Token
- Manage e commerce data programmatically
- Integrate Weedmaps API into automated workflows
- Query and filter Weedmaps API records by parameters
- Monitor Weedmaps API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'retrieve access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth/token` | Retrieve Access Token |
| GET | `/brands` | Retrieve Brands |
| GET | `/brands/{brand_id}` | Retrieve a Brand |
| GET | `/brands/{brand_id}/products` | Retrieve a Brand's Product Catalog |
| GET | `/products/{id}` | Retrieve a Brand Product |
| GET | `/products/{id}/reviews` | Retrieve Brand Product Reviews |
| GET | `/menus` | Retrieve Menus |
| GET | `/menus/{menu_id}` | Retrieve a Menu |

## Key resources

- **Auth** — Operations related to Auth
- **Brands** — Operations related to Brands
- **Menu Items** — Operations related to Menu Items
- **Menus** — Operations related to Menus
- **Orders** — Operations related to Orders

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 85 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/weedmaps.com/weedmaps/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the Weedmaps API?

Yes. Because you run Jentic One yourself, you decide which Weedmaps operations your agent may call and which OAuth2 credentials it uses, and your own rules enforce that at execution time. Weedmaps puts the brand id in the URL path, so you can pin an agent to a single brand, letting it read that brand and its products through GET `/brands/{brand_id}` and GET `/brands/{brand_id}/products` while leaving out operations you did not grant. Listing every brand with GET /brands or reading arbitrary menus stays off limits unless you explicitly add those operations to what the agent is allowed to do.