For agents

For agents

What omra exposes to agents

Every public page has a markdown twin, the site indexes itself in two files, and the callable resources are catalogued as data.

Reading a page

Every page listed below serves clean markdown two ways: send Accept: text/markdown to the normal URL, or append .md to it. Both return the same document, with YAML frontmatter carrying the canonical URL and the last-updated date.

Responses set Vary: Accept, so a cache in front of the site never hands the HTML to an agent or the markdown to a browser. An Accept omra cannot satisfy gets a 406 listing what it can — never a generic error.

Index documents
/llms.txt

What omra is, when to reach for it, and a link to every page's markdown.

text/markdown

/llms-full.txt

Every page concatenated, for a single-fetch read.

text/markdown

/openapi.json

The OpenAPI 3.1 document for the REST API, served from this domain.

application/json

/auth.md

How to get an API key, the scope catalog, error codes, idempotency and paging.

text/markdown

/pricing.md

The full price book as a document rather than a table inside a layout.

text/markdown

/sitemap.xml

Every indexable URL, with last-modified dates.

application/xml

/.well-known/ard.json

The callable resources as structured data. Also served at /.well-known/ai-catalog.json.

application/json

/.well-known/api-catalog

RFC 9727 linkset pointing at the OpenAPI document.

application/linkset+json

Callable resources
/api-reference/spec.json

OpenAPI 3.1 for the REST API. Authenticates with an api-key header.

OpenAPI 3.1

/trust/subprocessors

Who processes club data, for what, and where. No authentication.

application/json

/trust/ai-systems

Where omra uses AI, what each system may decide, and the oversight on it. No authentication.

application/json

These are served from omra’s API origin rather than this domain. Full detail is on the developer page.

Every page, as markdown
/index.md

What omra is, the modules it covers, how its agents draft rather than report, and the full price book.

text/markdown

/tour.md

A five-step walkthrough of one collections run. No sign-up.

text/markdown

/how-collections-works.md

The collections mechanism end to end: what the agent reads, how it ranks, what it drafts, and where it stops for a person.

text/markdown

/workflows/sailing.md

Regatta entries, scoring, classes and wristband checks on the member record.

text/markdown

/workflows/golf.md

Tee times, check-in, the pro shop and the dining room on one member account.

text/markdown

/about.md

What the company builds, its position on agents, who it is for, and its status.

text/markdown

/contact.md

How to reach omra: the monitored address, the demo booking link, and DPO routing.

text/markdown

/developers.md

The Omra REST API: base URL, OpenAPI 3.1 document, interactive reference, and how keys authenticate.

text/markdown

/for-agents.md

Omra's machine-readable surface: markdown variants, llms.txt, the sitemap, the resource catalog, and the public API.

text/markdown

/trust.md

The public subprocessor register and the register of where omra uses AI, both readable as JSON without an account.

text/markdown

What omra does not expose

There is no MCP server and no A2A agent card. Omra’s catalog lists only resources that resolve, so neither appears in it — an entry pointing at a URL that returns 404 costs an agent a fetch to discover nothing is there.

Every ledger figure across these pages carries an illustrative label. Each is a worked example showing how the mechanism behaves, not a club’s reported result.

Something missing?

Write to hello@clubomra.com if a document you expected is not here, or one that is here does not parse.