Yard

View saved version →

---
name: yard
metadata:
  author: yard.sh
  files:
    - SKILL.md
    - references/cli.md
    - references/projects.md
    - references/project-files.md
    - references/pricing.md
    - references/coupons.md
    - references/products.md
    - references/checkout.md
    - references/license-keys.md
    - references/releases.md
    - references/updates.md
    - references/sandboxes.md
    - references/landing-pages.md
    - references/services.md
    - references/yard-auth.md
    - references/database.md
    - references/rooms.md
    - references/local-dev.md
    - references/webhooks.md
    - references/api.md
    - references/sales.md
    - references/templates.md
    - references/troubleshooting.md
description: >-
  Yard sells, licenses, distributes and hosts software. Use whenever the user mentions Yard or the yard CLI:
  projects, pricing, license keys, releases and updates, sandboxes, hosted services and databases, yard dev,
  landing pages, Yard Auth sign-in, realtime rooms, templates, coupons, users or sales, and products sold on top
  of a tier (add-ons, DLC, consumables, in-app purchases, add-on subscriptions, fulfillment).
---

# Yard

Yard lets developers sell software: checkout with Yard as the merchant of record, for pricing tiers and for products sold on top of a tier, license keys and device activations, release downloads with an update server, custom landing pages, and hosted services with a database, user sign-in (Yard Auth) and realtime rooms. Developers manage it with the `yard` CLI or Yard's MCP server; shipped software integrates through the REST API.

Install: `curl -fsSL https://cli.yard.sh | sh` (Windows: `irm https://cli.yard.sh/install.ps1 | iex`). `yard login` prints a nine-digit code and opens `https://yard.sh/login/device`: show the user the code, they authorize, and the command exits signed in (run it in the background if your shell only returns output on exit). `yard <command> --help` is always current.

## Ground rules

- **Read the docs, not memory.** Every page of https://docs.yard.sh is Markdown at its URL plus `.md`; https://docs.yard.sh/llms.txt lists them all with one-line descriptions and names a search endpoint. Each reference file below names the pages that hold the detail: fetch a page before quoting a shape, limit or endpoint the file does not show. The REST API reference is online only (api.md).
- **Manage with the MCP server or the CLI, integrate with the API.** Projects, pricing, products, releases, pages, services, coupons, users and sales are management work: Yard's MCP tools when connected, otherwise the CLI. The REST API is for shipped software (license validation, updates, subscriptions, products, Yard Auth in external apps). Never create a project over HTTP.
- **Non-interactive only.** `--json` (result on stdout; messages and errors on stderr) and `--spec <file|->` (JSON input). Never pipe answers into a prompt. Commands that delete or overwrite take `--yes`; a run without it previews the question. Bare `yard init` is for humans.
- **Teams own everything.** Projects, coupons, API keys and payouts belong to a team; the CLI acts as the active team (`yard team --json` `.active_team`), shared with the dashboard. Projects live at `https://<team>.yard.sh/<slug>/`.
- **Check entitlements, never assume them.** Read `yard me --json` `.team_permissions` before proposing a feature (`.permissions` is the user's own and gates nothing on a project). Plan-dependent: license keys and activations, custom pages, services, Yard Auth, rooms, coupons, seat pricing, trials, tier and product counts, extra sandboxes and channels, API keys and webhooks (Pro). Never quote a plan's features from memory.
- **Read errors by `error_code`.** `upgrade_required` or `*_limit_reached`: the plan lacks the feature or hit a limit; send a spec it supports or point to https://yard.sh/pricing (tier and product plan refusals are plain `400`s naming the rule). `forbidden`: the member's team role; upgrading does not h

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 23 — file references are metadata, not package contents.