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 AgDR (AI Decision Record) with a BLAKE3 content hash and an Ed25519 signature, chained to the previous step. The air CLI replays that chain, verifies every signature, and reports OWASP Top 10 for Agentic Applications (ASI01 to ASI10) violations.

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 AgDR 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

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], ...)

Every step the agent takes (llm_start, llm_end, tool_start, tool_end, agent_finish) is appended to my-agent.log as a signed AgDR record.

Run the forensic trace

air trace my-agent.log

You get console output like this:

[AIR v0.1.3] Loaded 247 agent steps across 3 conversations.
[Chain verified] 247 signatures valid.

  ASI01 Agent Goal Hijack detected at step 47
    Tool `admin_delete_records` called with token overlap 0.03 against the user's stated intent.

  ASI02 Tool Misuse detected at step 51
    Tool `shell_exec` invoked with arguments matching pattern: shell metacharacters.

  ASI03 Prompt Injection detected at step 53
    Prompt matches the `ignore-previous-instructions` pattern.

Detector coverage:
  ASI01 Agent Goal Hijack          implemented
  ASI02 Tool Misuse                implemented
  ASI03 Prompt Injection           implemented
  ASI04 Memory Poisoning           not yet implemented
  ...

[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 AgDR chain implemented
Chain verification (tamper detection) implemented
LangChain callback handler implemented
ASI01 Agent Goal Hijack detector implemented (heuristic)
ASI02 Tool Misuse detector implemented (regex)
ASI03 Prompt Injection detector implemented (heuristic)
ASI04 through ASI10 detectors not yet implemented
JSON forensic export implemented
PDF forensic export implemented
SIEM forensic export (ArcSight CEF v0) implemented
Framework integrations beyond LangChain 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, mapped to a public taxonomy (OWASP ASI01 to ASI10), 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.1.3.tar.gz (25.2 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.1.3-py3-none-any.whl (22.1 kB view details)

Uploaded Python 3

File details

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

File metadata

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

File hashes

Hashes for projectair-0.1.3.tar.gz
Algorithm Hash digest
SHA256 ca14c8bcc0aa62dfeff04a41d22f8e34ec650ae844d6b194c7fd1968c9157f9a
MD5 bcdf0a2e58431a94a55a57f528874e05
BLAKE2b-256 61f5b41eb293f9bcba07181f5ca381505d1e49be868faa4cd144ae33d5feada0

See more details on using hashes here.

File details

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

File metadata

  • Download URL: projectair-0.1.3-py3-none-any.whl
  • Upload date:
  • Size: 22.1 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.1.3-py3-none-any.whl
Algorithm Hash digest
SHA256 213af7353f237f2526f8ec469140fc8ae8b23a19a98a8f0af52aaa48671de6a7
MD5 7f9d82e4d4cd66e55d01f9f08878cabe
BLAKE2b-256 19de1ae0c875cae26b3e5eac34bcfaf3479d0d12a33a3868a52ce0e9da05f6ae

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