DedicatedMac Developer Portal

The public DedicatedMac HTTP API, the OpenAPI specification, and everything an AI agent needs to call the service correctly.

DedicatedMac API documentation

The DedicatedMac API is three plain HTTP endpoints. The full API reference has request and response shapes, status codes and curl examples for each one.

GET /api/sku-availability
Check live stock for every DedicatedMac plan
POST /api/waitlist
Join the waitlist for an out-of-stock configuration
POST /api/checkout
Create a Stripe Checkout session for a rental

DedicatedMac authentication

DedicatedMac issues no API keys and runs no OAuth application. GET /api/sku-availability and POST /api/waitlist are fully public. Only POST /api/checkout understands a credential, and it is optional: a Firebase ID token from a signed-in customer portal session, sent as Authorization: Bearer <token>, binds the checkout to that account.

Machine-readable files

/llms.txtIndex of the site for language models, including when to use DedicatedMac and how to call it.
/llms-full.txtEvery page of the site concatenated as Markdown, for one-shot ingestion.
/agent-instructions.mdStandalone when-to-use guidance and a calling recipe for autonomous agents.
/openapi.jsonOpenAPI 3.1 description of the public DedicatedMac HTTP API.
/sitemap.xmlEvery indexable URL on dedicatedmac.io.
/robots.txtCrawl rules and sitemap pointer.

Markdown content negotiation

Every public DedicatedMac page serves Markdown on request. Send Accept: text/markdown and you get a Markdown body with Content-Type: text/markdown and Vary: Accept; send anything else and you get the normal HTML page. Unknown paths answer 404 with a Markdown error body.

curl -sS -H 'Accept: text/markdown' https://dedicatedmac.io/
curl -sS -H 'Accept: text/markdown' https://dedicatedmac.io/faq
curl -sS -H 'Accept: text/markdown' https://dedicatedmac.io/docs/api

What DedicatedMac does not offer

There is no MCP server for DedicatedMac.
There is no client SDK; the API is three plain HTTP endpoints, so use any HTTP client.
There are no API keys and no OAuth application. The public endpoints are unauthenticated, and the only credential the API understands is a Firebase ID token belonging to an existing portal account.
There is no headless purchase: POST /api/checkout returns a Stripe Checkout URL that a human must open.
There is no API for controlling a rented Mac. Restart and credential actions live in the signed-in customer portal at /dashboard.

Need something the API does not cover?

Questions about the API, or a capability you need that is not listed here: support@dedicatedmac.io.