Agentfleet.Client.Http 1.0.1

Agentfleet.Client.Http

The HttpClient-based implementation of the Agentfleet .NET client. Register it with one call and run workflows against the Agentfleet API. Contract types live in Agentfleet.Client.Core, which this package depends on.

Install

dotnet add package Agentfleet.Client.Http

Targets net8.0 and net10.0, so it can be consumed from any .NET 8+ application.

Authentication

The client attaches a bearer token to every request. The Agentfleet API expects an Authlink-issued JWT with the Agentfleet API as its audience (for example https://api.agentfleet.co.za in production). Obtain a client and credentials from your Authlink administrator, then supply the token via a static token, a token factory, or your own IAgentfleetTokenProvider registration — see below.

Getting started

using Agentfleet.Client.Core.Abstractions;
using Agentfleet.Client.Core.Requests;
using Agentfleet.Client.Http.DependencyInjection;

// Register with a static token…
services.AddAgentfleetWorkflowClient(
    accessToken: "<bearer-token>",
    configure: o => o.BaseAddress = new Uri("https://api.agentfleet.co.za"));

// …or a token factory that mints/refreshes on demand (for example an Authlink client-credentials token):
services.AddAgentfleetWorkflowClient(
    tokenFactory: ct => MintTokenAsync(ct),
    configure: o => o.BaseAddress = new Uri("https://api.agentfleet.co.za"));

Then inject IAgentfleetWorkflowClient and run a workflow, awaiting completion:

var result = await client.RunWorkflowAndWaitAsync(
    new RunWorkflowInstanceRequest { WorkflowId = workflowId, AgentId = agentId },
    cancellationToken: ct);

if (result.IsError)
{
    // inspect result.Errors
}
else
{
    var instance = result.Value; // final WorkflowInstanceDto — check instance.State
}

What the registration wires

• A typed HttpClient for IAgentfleetWorkflowClient bound to your configured BaseAddress.
• A BearerTokenHandler that attaches the token from your IAgentfleetTokenProvider per request.
• The standard resilience handler (Microsoft.Extensions.Http.Resilience) — retry, circuit breaker, and timeouts with sensible defaults for transient failures.

Options are validated at startup: a missing/relative base address or a missing token provider fails fast.