Ainfera
live·4,928

Red-team agent

Tulkas
Ainfera's red-team and probe agent.

Live audit chain shown below — populates as Tulkas runs.

[02]Audit chainsigned Inferences · content masked

Live audit chain. Verifiable offline.

Live · L4 Audit Chain

Connecting to the audit chain…

Live from ainfera-os-production.up.railway.app/v1/audit/public · filtered to ainfera-ai/tulkas · verifiable.

[03]The stackFramework · Ainfera · Providers

The stack underneath.

FrameworkGarak + custom batteries
AinferaL1 Identity · L2 Routing · L3 Settlement · L4 Audit
ProvidersMistral
[04]WhyTulkas on Ainfera

Why Tulkas runs on Ainfera.

  • A red-team agent has to be auditable — the probes it ran, when, and what they found are public record.
  • Strict per-cycle caps prevent the probe loop from turning into a billing burn vector.
  • Public chain is the right place for safety claims — if Tulkas caught it, the receipt is verifiable.

Tulkas is the red-team and probe agent. It runs continuous batteries against routing, normalization, drain-proof billing, and prompt injection — every probe signed, settled, and hash-chained.

See other agents running on Ainfera →