--- name: studiomeyer-services description: Read StudioMeyer services, website packages and fictional demos, prepare Memory or CRM subscription purchases, or submit a consultation inquiry with the user's approval. --- # Use StudioMeyer services Use this skill when the user asks about StudioMeyer's offer, website packages, demo examples or Memory and CRM purchase options. For unrelated companies, use their own sources. ## Agent checkout for Memory and CRM The [agent checkout contract](https://studiomeyer.io/api/stripe/agent-openapi) implements an ACP 2026-04-17 hosted-checkout profile at https://studiomeyer.io/checkout_sessions. Offers: `memory-pro`, `memory-team`, `crm-pro`, `crm-team`, one monthly EUR subscription per checkout. Read the live catalog in the contract for current amounts. Free remains free. Existing paid subscribers should manage their subscription first, rather than create another subscription. After the user's explicit approval, generate 32 cryptographically random bytes as 64 lowercase hexadecimal characters. Prefix with `sm_checkout_`; send only as `Authorization: Bearer `. Also send `API-Version: 2026-04-17`, a random UUID v4 `Idempotency-Key`, and `Content-Type: application/json`. POST the selected item, EUR currency, capabilities and `metadata: {"userConfirmed": true}` according to the contract. Keep the same capability, idempotency key and body on retries; a changed request conflicts. Never work around an uncertain result by changing keys. Do not send MCP credentials, website cookies, card details or payment tokens. The user opens `continue_url` and confirms the recurring payment in Stripe's hosted checkout. This profile requires that handoff; it does not accept autonomous card or Shared Payment Token charges. GET the owned session to observe payment and fulfillment; POST /complete reports completed only after both are confirmed. POST /cancel expires an unpaid open checkout; it never cancels an existing subscription. Payment does not grant data access: authorize separately with the selected product's OAuth flow. Never log the capability or put it in a URL. ## Read before acting 1. Read the [public OpenAPI contract](https://studiomeyer.io/api/v1/openapi) for current request and response schemas. 2. Read [authentication](https://studiomeyer.io/auth.md) before connecting an account. The public website API and authenticated MCP products have different authorization boundaries. 3. Read [prices](https://studiomeyer.io/pricing.md) for current published offers. Use the [Markdown sitemap](https://studiomeyer.io/sitemap.md) for page content; every listed page has a Markdown twin. ## Choose the operation - Read GET /api/v1/services for the published offer. - Read GET /api/v1/portfolio for fictional demos. Do not describe them as client results. - Use POST /api/v1/quote to read website package information, according to its OpenAPI schema. It does not create a binding order. - Read GET /api/v1/memory/purchase?plan=pro&locale=en for a new Memory Pro subscription or plan=team for Team. Read new Memory Pro or Team subscription purchase information: current price, localized purchase link and account-management link. Account status is unknown; existing paid subscribers should use account management first. This request starts no checkout session or payment. The user starts checkout and confirms payment themselves. - Send POST /api/v1/consultation only after the user asks for contact and approves sharing the supplied details. A person arranges the call; no appointment is booked automatically. Reuse the same Idempotency-Key and JSON body for retries. Follow the documented 409 and Retry-After handling; never change keys to bypass an incomplete request. ## Handle results Use only capabilities and amounts returned by the current contracts. Treat an MCP 401 as an authentication requirement. Do not reveal credentials, claim a payment completed from a purchase link, or infer access to another user's data. Follow the [public agent guide](https://studiomeyer.io/AGENTS.md) for further connection instructions.