Mythosia.AI.Abstractions 2.4.0

Mythosia.AI.Abstractions

Core contracts and shared models for the Mythosia.AI ecosystem. Defines IAIService, all model types, and streaming primitives. Consumed by Mythosia.AI.Rag and any library that needs the AI service contract without pulling in heavy provider implementations.

Installation

dotnet add package Mythosia.AI.Abstractions

Install this package directly only when writing a library that depends on the AI service contract (e.g., RAG orchestration, custom middleware). Applications normally take a transitive dependency through Mythosia.AI.

Core Interface

IAIService

The central abstraction for AI completion and streaming.

public interface IAIService
{
 string Model { get; }
 string Provider { get; }
 string SystemMessage { get; set; }
 bool StatelessMode { get; set; }
 ChatBlock ActivateChat { get; }

 // Completion
 Task<string> GetCompletionAsync(string prompt);
 Task<string> GetCompletionAsync(Message message);
 Task<string> GetCompletionAsync(Message message, AIRequestContext context);
 // ... additional overloads with AIRequestProfile

 // Streaming
 IAsyncEnumerable<string> StreamAsync(string prompt, CancellationToken ct = default);
 IAsyncEnumerable<StreamingContent> StreamAsync(Message message, StreamOptions options, CancellationToken ct = default);
 // ... additional overloads
}

All concrete providers (OpenAIService, AnthropicService, GoogleAIService, etc.) in Mythosia.AI implement this interface.

Models

Streaming

Functions

Exceptions

Relationship to Microsoft.Extensions.AI

Microsoft.Extensions.AI (IChatClient) and IAIService solve different problems at different layers.

IAIService sits at a higher abstraction level than IChatClient. Implementing IChatClient on top of IAIService would discard stateful session management, typed streaming, and the function-calling loop. The two interfaces are not interchangeable.

If interoperability with the MS ecosystem is required, the recommended direction is to accept an IChatClient as a constructor dependency inside a Mythosia.AI provider — not to replace IAIService with IChatClient.

Why This Package?

Mythosia.AI.Rag → Mythosia.AI.Abstractions (zero heavy dependencies)
 instead of
 Mythosia.AI (Azure.AI.OpenAI, NJsonSchema, TiktokenSharp, ...)

By depending on abstractions rather than the full implementation package, libraries like Mythosia.AI.Rag avoid pulling in provider-specific dependencies. The concrete provider is chosen by the final application.

Links

• Mythosia.AI (implementation)
• GitHub
• Wiki