# Meadow

**Canonical:** https://apis.io/providers/getmeadow-com/  
**Website:** https://getmeadow.com  
**APIs profiled:** 1

Meadow provides a comprehensive cannabis point‑of‑sale (POS) and e‑commerce platform for dispensaries across the United States. Founded in 2014, Meadow offers integrated inventory management, compliance reporting, delivery logistics, and retail analytics, helping cannabis retailers streamline operations and scale across multiple states. The platform supports integrations with major partners and delivers a unified dashboard for sales, compliance, and customer engagement.

## Kin Score — 26.6 / 100 (thin)

Scored 2026-10-31 under rubric 0.25.0.

| Facet | Score |
|---|---|
| Discoverability | 66.1 |
| Contract Quality | 0.0 |
| Contract Governance | 4.5 |
| Operational Transparency | 42.1 |
| Developer Ergonomics | 31.0 |
| Access Clarity | 31.6 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 24.5 (matched via fallback).

## Agent readiness — 33.0 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | documented |
| Auth Clarity | served |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | documented |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | yes |
| Consent Identity | no |
| Agent Card | conformant |
| Dry Run Mode | no |
| Delegated Identity | served |
| Protected Resource Metadata | verified |
| Dynamic Client Registration | yes |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |

## APIs (1)

- **Meadow API** — API to connect to the Meadow platform

## Security (2)

- **Getmeadow Com Authentication** — 2 schemes
- **Getmeadow Com Domain Security** — TLSv1.3 · HSTS · DMARC

## Tags

Company, Cannabis, POS, E-commerce, SaaS

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/getmeadow-com/). Scores are computed from the provider's own public artifacts under a published rubric.