# Aurochs > A backend with a human face: workspaces of pages, typed databases, and files, editable by people in a UI and by agents over MCP and REST. Both see the same data. There are three ways in, and which one you want depends on what you're building. If you are an AI assistant acting for a person, use MCP: point your client at https://aurochs.oxen.dev/api/mcp and it will discover the OAuth server, register itself, and prompt the person to connect. No API key. An assistant acts as the person, so it reaches every workspace they belong to. If you are a third-party app, use OAuth 2.1 + PKCE. The person picks ONE workspace when they connect you, and your token carries it — so you call the plain REST endpoints (/api/v1/pages, /api/v1/databases, …) with no workspace in the URL, exactly as an API key does. If you are a script the workspace owner controls, use an API key from the Connect page. Same REST API. In every case your effective permission is the weaker of that person's role in the workspace and the scope they granted you. Scopes are read, write, and admin (admin is not available to OAuth clients). Ask for offline_access if you want a refresh token; without it access ends in 15 minutes and can't be renewed. ## Connect - [Getting started for agents](https://aurochs.oxen.dev/agents): This page as HTML, plus the connect command for each client and the 30-tool surface. Start here if you are an assistant. - [MCP endpoint](https://aurochs.oxen.dev/api/mcp): Streamable HTTP. For assistants. OAuth or an `ak_` API key as a Bearer token. - [OAuth discovery](https://aurochs.oxen.dev/.well-known/oauth-authorization-server): RFC 8414. Most OAuth libraries can configure themselves from this URL alone. - [Developer docs](https://aurochs.oxen.dev/developers): The "Connect with Aurochs" flow for third-party apps, end to end. ## API - [REST base](https://aurochs.oxen.dev/api/v1): Workspace comes from your credential. `GET /api/v1/workspace` tells you which one you're in. - [OpenAPI spec](https://aurochs.oxen.dev/api/v1/openapi.json): Every endpoint and schema. Import it into any tool. - [API reference](https://aurochs.oxen.dev/api-reference): The same surface, interactive. ## Branding If you are putting Aurochs in your own interface — a Connect button, an integration listing, a settings row — take the assets from here rather than screenshotting the site. Two rules cover almost every case. Don't alter the mark: scale it and flatten it to one colour if your icon set needs that, but don't redraw, rotate, or drop it into a shape it didn't ship with. And say "Connect with Aurochs", never "Log in with" or "Sign in with" — the flow reaches a person's existing workspace, it doesn't create them an account. - [Brand manifest](https://aurochs.oxen.dev/brand.json): Machine-readable — every asset URL, the palette, the exact button spec, and the full do/don't list. Fetch this one if you are generating markup. - [The Connect button](https://aurochs.oxen.dev/developers): Copy-paste HTML in both themes, rendered from the same source as the real thing. - [Mark, SVG black](https://aurochs.oxen.dev/brand/aurochs-icon-svg-black.svg): Default, for light backgrounds. - [Mark, SVG white](https://aurochs.oxen.dev/brand/aurochs-icon-svg-white.svg): For dark backgrounds. - [Mark, SVG currentColor](https://aurochs.oxen.dev/brand/aurochs-icon-svg-current.svg): Inline it to inherit your text colour. Through `` it renders black — use the black or white file there. - [App icon](https://aurochs.oxen.dev/brand/aurochs-icon-colour-liquid-glass-rounded.png): 1024px rounded icon for a directory tile. Large; resize and re-host rather than hot-linking. ## Optional - [Auth reference](https://aurochs.oxen.dev/api/auth/reference): Sign-in, magic link, and device flow. Only relevant if you're building a first-party client. - [Protected resource metadata](https://aurochs.oxen.dev/.well-known/oauth-protected-resource): RFC 9728. MCP clients find this from the 401 on /api/mcp; you rarely fetch it by hand.