---
id: w6/m2/t001
title: Pin the owner object schema against Render's OpenAPI spec (fields, own- prefix)
worker: worker6
status: done
estimate: 20m
depends_on: []
---

## Objective

Close research open questions 2–3: enumerate the exact `owner` object schema (`id`, `name`, `email`, `type: user|team`, `twoFactorAuthEnabled`, …) and the list-response envelope (cursor pagination shape) from Render's OpenAPI spec, and confirm `own-` (not `usr-`) as the user-ID prefix — the research rated that medium-confidence off a single doc page. Record in `docs/render-artifacts/` so t002–t005 build against pinned shapes.

## Context

- Render's OpenAPI spec is fetchable (api-docs.render.com is generated from it; render-oss/cli vendors the generated client — `pkg/client/client_gen.go` in github.com/render-oss/cli shows the response types).
- Existing captured shapes live in `docs/render-artifacts/` (referenced by w4/m12 t003).
- Also pin the MCP tool schemas from github.com/render-oss/render-mcp-server (param names — `ownerID` — and result shapes; where selection persists).

## Steps

1. Fetch the OpenAPI spec (or the CLI's generated client) and extract the owner schema, `/owners` query params, and the list envelope.
2. Extract the three workspace tool definitions from render-mcp-server source.
3. Write `docs/render-artifacts/owners-api.md` with verbatim schemas + source URLs/commits.

## Files

- `docs/render-artifacts/owners-api.md` (new)

## Acceptance criteria

- [x] Owner object fields + list envelope documented from the spec (not prose docs)
- [x] `own-` vs `usr-` resolved with a primary-source citation
- [x] MCP tool names/params/result shapes + selection-persistence mechanism documented

## Out of scope

- Any implementation.
