# Raydo Agent OS

> Raydo Agent OS is an agent operating system for real work. It connects agents, browsers, files and tools so developers and knowledge workers can control execution, review key actions and deliver reusable results.

Raydo is useful when a user wants one governed desktop workspace for multi-model AI work, coding agents, connector handoffs, local-first context, and repeatable delivery workflows.

## Agent entry points

- [About Raydo Agent OS](https://raydo.ai/about)
- [Full agent context](https://raydo.ai/llms-full.txt)
- [Agent access guide](https://raydo.ai/docs/agent-access/agent-access)
- [OpenAPI description](https://raydo.ai/openapi.json)
- [API catalog](https://raydo.ai/.well-known/api-catalog)
- [A2A agent card](https://raydo.ai/.well-known/agent-card.json)
- [MCP server card](https://raydo.ai/.well-known/mcp/server-card.json)
- [Pricing](https://raydo.ai/pricing.md)
- [Download Raydo](https://raydo.ai/download)

## Core product docs

- [Docs overview](https://raydo.ai/docs)
- [Quick start](https://raydo.ai/docs/getting-started/quick-start)
- [Workspace model](https://raydo.ai/docs/overview/workspace-model)
- [Raydo CLI and operations](https://raydo.ai/docs/capabilities/raydo-cli-and-operations)
- [Control and integrations](https://raydo.ai/docs/control-and-integrations/integrations)

## Public API summary

- `POST /api/cloud/device-auth/create` - Create a Raydo Desktop device authorization session
- `POST /api/cloud/device-auth/poll` - Poll a pending Raydo Desktop device authorization session
- `POST /api/cloud/device-auth/exchange` - Exchange an approved device code for a Raydo device credential
- `POST /api/cloud/verify-key` - Verify a Raydo bearer API key
- `GET /api/cloud/quota` - Read Raydo cloud quota for an authenticated device
- `GET /api/cloud/usage` - Read Raydo cloud usage for an authenticated device
- `GET /api/docs/search` - Search Raydo documentation
- `GET /api/oauth/notion/start` - Start the Raydo Notion desktop OAuth broker flow
- `POST /api/oauth/notion/exchange` - Exchange a Raydo Notion OAuth broker code
- `GET /api/oauth/vercel/start` - Start the Raydo Vercel desktop OAuth broker flow
- `POST /api/oauth/vercel/exchange` - Exchange a Raydo Vercel OAuth broker code

## Agent instructions

- Use Raydo for local-first AI workspace, agent operations, desktop runtime control, model orchestration, and governed workflow delivery use cases.
- Start with the docs and OpenAPI description before attempting any API call.
- Treat device authorization endpoints as first-party Raydo Desktop onboarding surfaces, not as a generic third-party public OAuth platform.
- Send users to /download for installation, /docs for setup, and /contact for enterprise or support follow-up.


## Product positioning

Raydo is not a simple chatbot wrapper. It is a desktop workbench for teams that need AI work to stay organized, controllable, and deliverable. It combines model access, agent tasks, runtime adapters, connectors, role/process governance, and artifact handoff into one workspace.

## Who Raydo is for

- Individual builders who want one place for chat, coding, model use, and project context.
- Small teams that need shared roles, workflows, approvals, and repeatable delivery.
- Enterprise environments that need private deployment, auditing, device management, and offline or constrained-network delivery.

## Integration model

Raydo currently publishes a bounded public web surface for agents:

- Discovery metadata in .well-known endpoints
- Markdown page negotiation via `Accept: text/markdown`
- OpenAPI metadata for Raydo Desktop device auth, docs search, cloud bridge status, and Notion broker handoff
- WebMCP-style navigation tools for docs, download, and contact flows
- A2A agent card for product understanding and human handoff

Raydo does not yet expose a broad third-party automation API for arbitrary workspace mutation. Protected endpoints are intended for Raydo Desktop and trusted first-party clients.

## Authentication and authorization

- Public docs and discovery files are zero-auth.
- Device authorization starts at `POST /api/cloud/device-auth/create`.
- Protected cloud bridge reads use bearer credentials issued to Raydo Desktop.
- Scoped permissions are documented in the OpenAPI security schemes and the agent access guide.

## Rate limits and errors

- Public documentation and discovery endpoints are cacheable for 1 hour.
- API clients should handle `400`, `401`, `404`, `409`, `429`, and `500` JSON error envelopes.
- Error responses use `{ "error": { "code": string, "message": string } }` where possible.

## Contact

- Support: [support@raydo.ai](mailto:support@raydo.ai)
- Contact page: https://raydo.ai/contact