# Product API

Use Product API to manage workspace-scoped product resources. Each task page documents the HTTP interface; use Product SDK when application code needs typed wrappers.

| Task | Start here |
| --- | --- |
| Make the first authenticated request | [Get started](getting-started.md) |
| Find workspaces and members | [Workspaces and members](workspaces-members.md) |
| Manage data, files, and transfers | [Data, files, and connectors](data-files-connectors/index.md) |
| Create or run workflows | [Workflows, WorkItems, and lineage](workflows-workitems-lineage/index.md) |
| Invoke published agents | [Agent invocation](agents-a2a/index.md) |
| Run SQL | [SQL](sql.md) |
| Manage compute instances | [Compute instances](compute-resources.md) |

Product resources normally belong to one workspace. Obtain a `workspace_id`, send the same workspace header on later requests, save IDs returned by create or run operations, and use status or detail endpoints to continue. Genesis model inference uses separate service addresses and credentials.

```{toctree}
:hidden:
:maxdepth: 1

Get started <getting-started>
Workspaces and members <workspaces-members>
Data, files, and connectors <data-files-connectors/index>
Workflows, WorkItems, and lineage <workflows-workitems-lineage/index>
Semantic models <semantic-models>
Agent invocation <agents-a2a/index>
Provider, Backend, and Router <provider-backend-router/index>
SQL <sql>
Compute instances <compute-resources>
Data sharing <data-sharing>
```