Expose code as a Graftcode Receiver

Turn an existing library or module into a Receiver without adding HTTP route handlers, controllers, or transport types on the public surface.

1. Choose the public surface

Expose only intentional public classes and methods. Keep database clients, HTTP objects, streams, framework models, and implementation helpers internal.

Use a plain module with a small, intentional public API. Prefer primitives, plain models, and language arrays. Async return types (Task, Promise, async def, …) are allowed on many Receivers when you need them—results complete on the Receiver; see Invocation lifecycle. Avoid CancellationToken, framework collection interfaces, and non-parsable BCL types on the public surface.

namespace Pricing;

public static class PriceService
{
    public static double Calculate(double amount, double discountPercent) =>
        amount * (1 - discountPercent / 100);
}

dotnet build ./Pricing/Pricing.csproj

gg ./Pricing/bin/Debug/net9.0/Pricing.dll