Information

Aegir package, API host, and platform information

This page is the long-form explanation surface for what Aegir is, how the trust model fits together, how the hosted API surface works, and how teams should think about the NuGet, NPM, and Java distributions.

NuGet

.NET integration path

Install the package
Use the Foxlin.Aegir.Auth package inside your .NET solution to consume Aegir trust services and models.
Register your application
Create your developer account, issue a key, and register the application and environment you are securing.
Wire challenge and token flows
Use the Aegir SDK services to issue challenges, verify responses, and translate trust into OIDC-friendly outputs.

NPM

JavaScript integration path

Install the package
Add the Aegir NPM package to your JavaScript or TypeScript application when the JS distribution is published.
Bind to the same developer account
Use the same application and environment registration model as the .NET package so audits stay aligned.
Route trust outcomes into your UI
Use the package to surface login, provider linking, and device trust moments inside your app flow.

Java

JVM integration path

Publish to Maven Central
Use Maven Central as the primary distribution channel for Java and broader JVM consumers.
Offer a clean JVM wrapper
Package Java-facing APIs as a stable wrapper over the same Aegir trust contracts rather than inventing a different trust story.
Keep docs aligned
Mirror the NuGet and NPM guidance so Java adopters see the same application registration and federation concepts.

API host

`services.foxlinindustries.com/apis` responsibilities

Account lookup
The API host exposes a user account summary endpoint so the dashboard and future mobile app can retrieve identity, provider, and device context.
Federation handoff sessions
The API host creates session records that a desktop or mobile app can pick up, use for provider authentication, and complete back into Aegir.
Protected machine access
Endpoints are gated by a configuration key using the X-Aegir-Config-Key header so hosted clients can be enrolled deliberately.
Package and payment discovery
The API host also exposes distribution and payment-option descriptors to support the dashboard and future developer account flows.

Payments

Commercial surface

Stripe
Primary card and subscription billing path for developer plans.
ACH
Bank-transfer option for larger or recurring business accounts.
Aegir payment
Visible as a Coming Soon stub so the product hints at its future direction without disclosing the full design yet.

What the project includes

Aegir combines device-bound trust, developer-scoped application registration, challenge verification, trust tokens, revocation logic, and an OIDC bridge foundation. The public site explains those layers in plain language while the API host gives the future mobile and desktop clients a stable place to create and complete federation sessions.

What comes next

Production readiness still requires real provider federation, commerce, deployable API hosting, and publication pipelines. This page now makes the hosting, packaging, and payment direction visible so the UX and API contract can evolve together.