List your AI tool on AI Orion for free. Submit a tool

Antaeus

Semantic policy decisions you can inspect

Pricing
Free plan

About Antaeus

Antaeus is a semantic decision engine that turns human-written policy into versioned artifacts an application can evaluate and inspect. It is meant for bounded questions that need interpretation of language, intent, context or exceptions, while deterministic rules, authentication, authorization and side effects stay in the application's own code. It is aimed at engineers who run meaning-heavy decisions in production and need to know which policy decided a case, what changed, and what happens when evaluation fails.

A policy is written as constrained YAML or JSON against a versioned schema, and Antaeus derives a canonical digest for that exact policy. Named cases bind inputs and expected outcomes to the policy version so wording changes show up as test differences. An evaluator route is chosen separately from the policy meaning; the local quickstart uses a synthetic fixture with no credentials or network calls, and an experimental OpenAI adapter evaluates real conditions with the user's own key.

Every evaluation returns one of four explicit outcomes: allow, review, deny or failure, so an outage is never treated as a denial or a permission. The decision carries the policy, rule results, reason codes and the supporting proof behind it. The hosted API accepts an inline policy or a reference to a published immutable version, uses idempotency keys with a 24-hour replay window, and supports shadow mode. An MCP server lets AI assistants check proposed actions against an approved policy.

The core is open source under the Apache-2.0 license, with Go packages, a command-line workflow, schemas and examples; release v0.6.0 installs with Homebrew, go install or a container image. The hosted beta adds API keys, managed policies, a dashboard and prepaid usage, but runs on shared capacity with no production SLA, and the semantic evaluator is experimental. Request metadata and decisions are kept for 90 days; raw inputs and inline policy text are not stored in that log.

Use cases

  • Checking a product listing against selected marketplace policy rules
  • Screening user submissions for threats before they reach an application decision
  • Turning terms of use into an enforceable content policy
  • Testing a policy wording change against named cases before it ships
  • Letting an AI assistant verify proposed actions against an approved policy through MCP

Key features

  • Policies authored as constrained YAML or JSON with a canonical digest
  • Named test cases bound to a policy version
  • Four explicit outcomes: allow, review, deny or failure
  • Traceable evidence behind each decision
  • Open-source Go core and CLI under Apache-2.0
  • Hosted API with API keys, managed policies and a dashboard
  • Experimental OpenAI evaluator using the user's own key
  • Idempotency keys with a 24-hour replay window
  • MCP server for checking AI assistant actions against a policy
  • Scoped API keys for decisions, policy reads and policy writes

Pros and cons

Pros

Core engine is open source and runs locally without a hosted account
Local quickstart reads no credential and makes no network call
Operational failures and replayed requests are not charged

Cons

Hosted service is an experimental beta with shared capacity and no production SLA
The semantic evaluator is experimental
No browser CORS access; calls must come from a backend
Public demo allows one free completed check per network per day and only selected Amazon rules
No backup evaluator is dispatched on outages
No empirical result on semantic quality has been published

Reviews

Loading reviews…

Frequently asked questions

Which policy decided a given result?
Each decision identifies the exact authored artifact, configuration and evaluator route rather than reconstructing them from a prompt.
What happens when evaluation fails?
Failure is returned as its own outcome, distinct from review and deny, so the application decides how to handle it; it is never relabelled as allow.
How is request data handled?
Request metadata and structured decisions are retained for 90 days; raw evaluation inputs and inline policy text are not persisted in that log, though they pass to the evaluation provider.
How is Antaeus installed?
Release v0.6.0 installs with Homebrew, go install or a container image.

Alternatives to Antaeus

More in AI Agent