.NET Clients

Typed HttpClient SDKs for modern .NET (net10.0). Hosts and Core stay out of NuGet — Client + Contracts only. Flow has no client package (orchestrator ships as app zips).

Package	Surface	Product docs
OxyKit.Render.Client	Render transforms	Render › Client
OxyKit.Mail.Client	SendAsync only	Mail › Client

dotnet add package OxyKit.Render.Client
dotnet add package OxyKit.Mail.Client

Contracts packages (OxyKit.*.Contracts) hold shared wire types and are referenced by the Clients. Integrators normally take the Client package only. Do not consume OxyKit.Render.Core from other apps — it is not published.

Runnable hosts

Prefer GitHub Releases when you want binaries without building from source (framework-dependent; needs .NET 10):

Product	Releases
Render	app zips
Mail	app zips
Flow	app zips

Each tag publishes *-{linux-x64|win-x64|osx-arm64}.zip. Render and Mail release assets also include the Client/Contracts .nupkg files (same packages as nuget.org).

Local references (optional)

From a suite checkout you can project-reference instead of NuGet:

<ProjectReference Include="..\OxyKit.Render\src\OxyKit.Render.Client\OxyKit.Render.Client.csproj" />
<ProjectReference Include="..\OxyKit.Mail\src\OxyKit.Mail.Client\OxyKit.Mail.Client.csproj" />

Auth reminders

Client	Typical header
Render	X-OxyKit-Render-Key
Mail	X-Api-Key (or Bearer)

Legacy .NET Framework

Do not consume these packages from Framework 2.0–4.8. Use raw HTTP:

→ .NET Framework 2.0 / 4.5+