Skip to main content

Project AIR: forensic reconstruction and incident response for AI agents. Turn agent traces into signed forensic records with BLAKE3 + Ed25519.

Project description

Project AIR
Forensic reconstruction and incident response for AI agents.

vindicara.io · Quickstart · Pricing


What this is

When an AI agent goes off-script, AIR tells you what happened and proves it. Every agent decision is written as a Signed Intent Capsule (the pattern named in OWASP Top 10 for Agentic Applications v12.6 as ASI01 mitigation #5: a signed envelope binding the declared goal, constraints, and context to each execution cycle). Each capsule carries a BLAKE3 content hash and an Ed25519 signature, chained to the previous step. The on-disk format is AgDR-compatible (AI Decision Record schema, accountability.ai). The air CLI replays that chain, verifies every signature, and reports findings across two public OWASP taxonomies plus one AIR-native check.

Coverage today:

  • OWASP Top 10 for Agentic Applications (5 of 10 implemented): ASI01 Agent Goal Hijack, ASI02 Tool Misuse & Exploitation, ASI04 Agentic Supply Chain Vulnerabilities (partial, MCP supply-chain risk only), ASI06 Memory & Context Poisoning, ASI07 Insecure Inter-Agent Communication. ASI03, ASI05, ASI08, ASI09, ASI10 are on the roadmap.
  • OWASP Top 10 for LLM Applications (3 categories covered): LLM01 Prompt Injection, LLM04 Model Denial of Service, LLM06 Sensitive Information Disclosure.
  • AIR-native (1 detector): forensic-chain-integrity check (no direct OWASP equivalent).

One pip install. One callback. A signed forensic record of every agent run.

Install

pip install projectair

This installs the air terminal command and the airsdk Python library.

Try it with zero setup

Don't have an agent instrumented yet? Run:

air demo

That generates a fresh signed capsule chain (13 steps, two baked-in OWASP ASI violations), verifies every signature, runs the detectors, and writes a forensic-report.json next to you. Full cold-start experience in one command, no LangChain wiring required.

Instrument your agent

LangChain

from airsdk import AIRCallbackHandler
from langchain.agents import AgentExecutor

handler = AIRCallbackHandler(
    key="...",                           # Ed25519 signing key (hex or PEM); auto-generated when omitted
    log_path="my-agent.log",
    user_intent="Draft a Q3 sales report from the CRM data",
)

agent = AgentExecutor(callbacks=[handler], ...)

OpenAI SDK

from openai import OpenAI
from airsdk import AIRRecorder
from airsdk.integrations.openai import instrument_openai

recorder = AIRRecorder(log_path="my-agent.log", user_intent="Draft a Q3 sales report")
client = instrument_openai(OpenAI(), recorder)

# From now on chat completions write llm_start + llm_end Signed Intent Capsules automatically.
response = client.chat.completions.create(
    model="gpt-4o",
    messages=[{"role": "user", "content": "..."}],
)

Anthropic SDK

from anthropic import Anthropic
from airsdk import AIRRecorder
from airsdk.integrations.anthropic import instrument_anthropic

recorder = AIRRecorder(log_path="my-agent.log", user_intent="Draft a Q3 sales report")
client = instrument_anthropic(Anthropic(), recorder)

# From now on messages.create writes llm_start + llm_end Signed Intent Capsules automatically.
response = client.messages.create(
    model="claude-sonnet-4-6",
    max_tokens=1024,
    messages=[{"role": "user", "content": "..."}],
)

For tool calls your code executes, wrap them with recorder.tool_start(...) / recorder.tool_end(...) so the forensic chain captures them too.

Custom code (any framework)

from airsdk import AIRRecorder

recorder = AIRRecorder(log_path="my-agent.log")
recorder.llm_start(prompt="...")
# ... call your model ...
recorder.llm_end(response="...")
recorder.tool_start(tool_name="crm_read", tool_args={"account": "acme"})
# ... call your tool ...
recorder.tool_end(tool_output="...")
recorder.agent_finish(final_output="...")

Every call appends a signed Signed Intent Capsule to the log. No framework required.

Run the forensic trace

air trace my-agent.log

You get console output like this:

[AIR v0.1.6] Loaded 34 agent steps across 1 conversations.
[Chain verified] 34 signatures valid.

  ASI01 Agent Goal Hijack detected at step 8
  ASI02 Tool Misuse & Exploitation detected at step 32
  ASI04 Agentic Supply Chain Vulnerabilities detected at step 6
  AIR-01 Prompt Injection detected at step 4
  AIR-02 Sensitive Data Exposure detected at step 11
  AIR-03 Unrestricted Resource Consumption detected at step 30
  AIR-04 Untraceable Action detected at step 32

OWASP Top 10 for Agentic Applications coverage (5 implemented, 5 on roadmap):
  ASI01 Agent Goal Hijack                         implemented
  ASI02 Tool Misuse & Exploitation                implemented
  ASI04 Agentic Supply Chain Vulnerabilities      partial: MCP supply-chain risk only
  ASI03 Identity & Privilege Abuse                not yet implemented
  ...

Additional detectors (OWASP LLM Top 10 + AIR-native):
  AIR-01 Prompt Injection           OWASP LLM01 Prompt Injection
  AIR-02 Sensitive Data Exposure    OWASP LLM06 Sensitive Information Disclosure
  AIR-03 Resource Consumption       OWASP LLM04 Model Denial of Service
  AIR-04 Untraceable Action         AIR-native (no direct OWASP equivalent)

[Export] forensic-report.json

Export formats: air trace --format pdf emits a human-readable PDF for legal and insurance stakeholders; --format siem emits ArcSight CEF v0 events for SIEM ingestion (Splunk, Sumo, QRadar, Datadog).

Session 1 scope

This release covers the minimum forensic surface end-to-end:

Capability Status
BLAKE3 + Ed25519 Signed Intent Capsule chain (AgDR-format) implemented
Chain verification (tamper detection) implemented
LangChain callback handler implemented
ASI01 Agent Goal Hijack implemented (heuristic)
ASI02 Tool Misuse & Exploitation implemented (regex)
ASI04 Agentic Supply Chain Vulnerabilities implemented (partial: MCP supply-chain risk only)
ASI06 Memory & Context Poisoning implemented (heuristic: retrieval-output + memory-write scans)
ASI07 Insecure Inter-Agent Communication implemented (identity, nonce, replay, downgrade, descriptor-forgery checks)
ASI03, ASI05, ASI08, ASI09, ASI10 not yet implemented
AIR-01 Prompt Injection implemented - maps to OWASP LLM01
AIR-02 Sensitive Data Exposure implemented - maps to OWASP LLM06
AIR-03 Unrestricted Resource Consumption implemented - maps to OWASP LLM04
AIR-04 Untraceable Action implemented - AIR-native, no OWASP equivalent
JSON forensic export implemented
PDF forensic export implemented
SIEM forensic export (ArcSight CEF v0) implemented
LangChain callback integration implemented
OpenAI SDK integration implemented
Anthropic SDK integration implemented
LlamaIndex / CrewAI / AutoGen not yet implemented

The detectors are honest first-pass heuristics. They will produce false positives and false negatives. The signed chain itself is production-grade cryptography.

Why AIR exists

The prevention layer is crowded. Lakera, NeMo Guardrails, Bedrock Guardrails, and a dozen other tools sit in front of your agent and try to stop bad things from happening. None of them tell you what actually happened when an agent ran, and none of them produce evidence an auditor, a regulator, or an insurance carrier can use.

AIR is the forensic and incident response layer that runs behind those tools. It does not replace them. It gives you a signed record of every agent decision, findings mapped to the OWASP Top 10 for Agentic Applications public taxonomy, exportable to formats your SIEM, your compliance team, and your carrier already understand.

License

MIT. See LICENSE.

Contributing

This is pre-1.0 and the shape will evolve. Issues, traces that break the detectors, and new ASI detector PRs are all welcome at https://github.com/get-sltr/vindicara-ai.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

projectair-0.2.1.tar.gz (45.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

projectair-0.2.1-py3-none-any.whl (38.2 kB view details)

Uploaded Python 3

File details

Details for the file projectair-0.2.1.tar.gz.

File metadata

  • Download URL: projectair-0.2.1.tar.gz
  • Upload date:
  • Size: 45.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.12

File hashes

Hashes for projectair-0.2.1.tar.gz
Algorithm Hash digest
SHA256 61947385591f14d8c78081c3f091c44958763d7c5df7fe48567797d8eaa96f78
MD5 480ce535c2d3b44352aba836c5141901
BLAKE2b-256 f9af60d89b93762b326c75cf27a6ae14feeadc701fde0b808fccc9e845a2acc2

See more details on using hashes here.

File details

Details for the file projectair-0.2.1-py3-none-any.whl.

File metadata

  • Download URL: projectair-0.2.1-py3-none-any.whl
  • Upload date:
  • Size: 38.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.13.12

File hashes

Hashes for projectair-0.2.1-py3-none-any.whl
Algorithm Hash digest
SHA256 8fb2de61e4030baddb5d2ad5ff689af535c19ea01916af5ccd1aff8ee5ef31e6
MD5 e92e4e1604ffd6dcd09e7c976f6e3377
BLAKE2b-256 65740b93a945646a309c98b3a031f712fa6bffe7b4bc2fd91ff5e077c46d5aa8

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page