# Rend

> Rend is the video platform for developers. One API call to upload, one URL that plays instantly anywhere in the world. Open source, on hardware we own.

Rend is open source. The server is AGPL; the player and SDKs are MIT. Self-hosting is free forever, and Rend Cloud currently serves generated HLS from Tigris-backed origin while the bare-metal edge path remains optional and dormant.

## Pages
- [Features](https://rend.so/features): What Rend does: upload with one API call, encoding included, generated HLS from Tigris-backed origin, pricing by resolution, fully open source, and llms.txt plus OpenAPI for AI editors.
- [Why Rend is fast](https://rend.so/performance): Why Rend is fast: generated HLS, Rend-controlled playback URLs, private origin URLs kept out of the browser, and an optional bare-metal edge path kept dormant until regional coverage makes it worthwhile.
- [Pricing](https://rend.so/pricing): Rend pricing: pay for delivery (per second streamed, by resolution) and storage (per second-month kept, by resolution). Encoding is included, there are no egress fees, and plans run from pay as you go up to Enterprise.
- [How Rend compares](https://rend.so/compare): How Rend compares to other ways of paying for video: minute-billed platforms, budget per-GB CDNs, and rolling your own. Rend bills delivery and storage by resolution, includes encoding, is open source and self-hostable, and serves generated HLS from Tigris-backed origin by default.
- [Benchmarks](https://rend.so/benchmarks): A startup speed benchmark comparing Rend's production playback path against Mux on the same source video: median time to first frame, stall counts and reliability across US and Europe runs, with the full raw artifacts published.
- [Built by the team behind Cap](https://rend.so/about): Rend is built by the team behind Cap, the open source screen recorder. Cap serves a huge library of recordings that have to play the instant a share link opens, so the team built Rend to make that happen, then opened it up for other developers. Cap runs entirely on Rend.

## Docs
- [Docs home](https://rend.so/docs): Public API docs for uploading video, waiting for playback, embedding the player, reading analytics, and deletion.
- [Quickstart](https://rend.so/docs#quickstart): Sign up, choose a plan, create a key, upload, embed, and delete.
- [Agent setup](https://rend.so/docs#agent-setup): Give an agent the docs, API contract, safe key rules, and smoke test path.
- [MCP server](https://rend.so/docs#mcp-server): Install Rend tools in Cursor or any MCP client with one click or copyable config.
- [SDK guide](https://rend.so/docs#sdk-guide): Use the generated TypeScript SDK from packages/sdk.
- [curl guide](https://rend.so/docs#curl-guide): Use the public API with bearer auth and documented paths.
- [Auth and API keys](https://rend.so/docs#auth-api-keys): Scopes, headers, and key handling.
- [Playback and embed](https://rend.so/docs#playback-embed): Tokenless same-origin bootstrap and artifact paths.
- [Billing and usage](https://rend.so/docs#billing-usage): Autumn limits, tiered delivery seconds, and storage second-months.
- [Error states](https://rend.so/docs#error-states): not_playable, suspended, unauthorized, upload too large, and deleted.
- [Local Docker](https://rend.so/docs#local-docker): Run the local stack and integration smoke.
- [Production notes](https://rend.so/docs#production-notes): Only the env and profile notes needed for public API use.
- [Reference](https://rend.so/docs#reference): OpenAPI and SDK source links.

## Reference
- [OpenAPI JSON](https://rend.so/openapi.json): Canonical public API contract.
- [TypeScript SDK](https://github.com/CapSoftware/Rend/tree/main/packages/sdk): Generated TypeScript client.
- [MCP server](https://github.com/CapSoftware/Rend/tree/main/packages/mcp): MCP tools for upload, assets, playback, deletion, and analytics.
- [Full content for LLMs](https://rend.so/llms-full.txt): Plain-text content of every marketing page, including all FAQs.

## Notes for agents
- Use only the public paths documented at /docs and /openapi.json.
- Authenticated API calls use Authorization: Bearer <Rend API key>.
- Browser playback uses /api/player/{assetId} and same-origin artifact URLs.
- A copyable integration prompt is available at /docs#agent-setup.
- Generate tools from /openapi.json, use the MCP server for agent workflows, and prefer the TypeScript SDK for app code.