Read this first — keys, scopes, rate limits, and where the docs live

Everything in this category assumes you have read this topic. It is short.

Where the reference lives

The full endpoint reference is at /reference — request and
response shapes, parameters, and the error catalogue. It is generated from the
live contract, so it does not drift from what the server actually does.

The two credential types

1. An API key — for headless, server-to-server calls. You create it in the
   developer portal, you see the secret exactly once, and you present it in the
   X-PTM-Api-Key header. See How to create, rotate and revoke an API key.
2. An MCP connection — for an AI assistant acting on your behalf. This is a
   separate, explicit authorization, not a side effect of signing in. See
   Connecting an MCP client to Place to Mingle.

They are deliberately not interchangeable. An API key cannot reach the MCP
surface, and an assistant's connection is revocable without touching your keys.

Scopes

A key carries scopes, fixed at creation. A call outside them is refused, not
silently narrowed. Dating data is excluded from both surfaces entirely — there
is no scope that reaches it and no endpoint that serves it.

Rate limits and quotas

Limits are per key. A refusal comes back as a documented status with a
machine-readable body, not as a truncated success. If you are being limited,
the answer is usually batching rather than a higher limit — several endpoints
take a set of identifiers in one call.

Before you post here

Include the endpoint, the HTTP method, the status you got back, and the
response body with any secrets removed. A request id, if you have one, turns a
guess into a lookup.

Never paste a key, a token or an Authorization header. If you do, rotate
it immediately — editing the post does not un-publish it.