# Access to ocms.tech

> Public project documentation and published REST content can be read anonymously. Administrative operations require a scoped API key supplied by the site owner.

## Read public content

Start with [llms.txt](https://ocms.tech/llms.txt). Fetch supported guide URLs with .md appended, or request an HTML page with Accept: text/markdown. No account, API key or browser session is needed.

The public REST base is https://ocms.tech/api/v2. For example:

```sh
curl -fsS https://ocms.tech/api/v2/pages/slug/docs
curl -fsS -H 'Accept: text/markdown' https://ocms.tech/docs
```

The [live OpenAPI schema](https://ocms.tech/api/v2/openapi.json) defines each operation's authentication and response schemas. Public content access does not grant access to drafts, private media or administrative actions.

The [AI resource catalog](https://ocms.tech/.well-known/ai-catalog.json) lists public documentation and REST discovery resources. In browsers with WebMCP support, search_ocms_docs searches guide titles and summaries, and read_ocms_guide fetches a selected public Markdown guide. These browser tools send anonymous GET requests without cookies or an Authorization header; they do not publish, edit content or navigate the browser. They are separate from the authenticated server MCP endpoint below.

## Use an owner-issued API key

An authorized administrator creates and scopes API keys in the site's admin panel. Ask the owner for only the permissions needed for the requested work, supply the key as Authorization: Bearer <key>, and check GET https://ocms.tech/api/v2/auth before using it. Keep credentials out of URLs, public documents, screenshots and logs.

Follow the [API cookbook](https://ocms.tech/api-cookbook.md) for scoped-key examples and error handling. A key authorizes API access within its scopes; publication and other changes still require the owner's instructions. An uncertain write result should be resolved by reading the target before attempting another create.

## MCP and registration

The discovery card at https://ocms.tech/.well-known/mcp/server-card.json points to the site's authenticated MCP endpoint. Anonymous initialization returns HTTP 401. Public documentation reading does not require MCP, and a discovery card alone is not evidence that anonymous tools are available. Authorized clients must follow the deployed server's contract and the owner's access instructions.

This site has no automatic agent-registration or OAuth token-issuance flow. This file documents existing access; it does not declare the WorkOS agentic-registration protocol or a public write service.

## Access failures

- HTTP 401: the operation requires credentials, or the supplied key is invalid. Ask the owner rather than attempting a sign-in bypass.
- HTTP 403: the request is forbidden; check the key's scope with the owner.
- HTTP 404: check the exact public URL or slug. Private and unpublished content is not part of this public index.
- HTTP 429: respect Retry-After when present and retry with backoff.

Use the canonical https://ocms.tech host for authenticated requests. See [account security](https://ocms.tech/account-security.md), [support](https://ocms.tech/support.md) and [robots.txt](https://ocms.tech/robots.txt) for further guidance.
