ptrace

A dead-simple API where AI agents log what they do, owners define what's allowed, and anyone can cryptographically verify the integrity of what was logged.

How it works

01Register0.002 ETH or $5
02DeclareSign a policy
03LogHash-chained entries
04ReportExternal observations
05VerifyAnyone, anytime

Why ptrace

Tamper-evident logging

Every entry is signed by the agent and hash-chained to the previous one. Deletion or modification is cryptographically detectable by anyone.

Reports catch what logs miss

Agents can omit actions. That's why anyone can file signed reports for behavior they observed. The unlogged_action category flags gaps between what was logged and what actually happened.

Externally verifiable

Signatures and hash chains are self-proving. Anyone can verify integrity without trusting ptrace. We store the data, but the cryptographic proofs stand on their own.

Privacy by design

Only content hashes are stored, never the raw content. The agent retains the original and can produce it for verification. Same model as git commits.

Explore

Live Demo →

Try the real API in your browser. Generates an ephemeral wallet, signs real EIP-191 payloads, and makes actual HTTP requests.

Agent Dashboard →

See what an agent's public profile looks like: logs, policy, chain integrity, reports. Look up any registered agent by address.

Use Cases →

Concrete scenarios with implementation details: forum agents, trading bots, multi-agent pipelines, regulatory audits.

Integration Example →

Working Python script that runs the full ptrace flow: declare policy, log 3 actions, verify chain. ~80 lines of code.

What ptrace is (and isn't)

It's an audit trail

ptrace proves what was logged wasn't tampered with and who signed it. It records signed claims from both agents and external observers.

It's not a firewall

ptrace doesn't sit between the agent and the world. It can't stop an agent from acting. Policies are declared, not enforced — violations are flagged after the fact.

Agents can lie or omit

Self-reporting has limits. External Reports are the mitigation: platforms and other agents file signed observations. The gap between logs and reports is the core signal.

Writes are centralized

Logging goes through our API. Verification is decentralized — the cryptographic proofs stand on their own. Data export and self-hosting are on the roadmap.

SDKs

Python

pip install ptrace-sdk
from ptrace import PtraceClient

client = PtraceClient(KEY)
client.log_action(
  "post_reply",
  "forum.example.com",
  client.content_hash(content)
)

TypeScript

npm install ptrace
import { PtraceClient } from "ptrace";

const client = new PtraceClient(KEY);
await client.logAction(
  "post_reply",
  "forum.example.com",
  PtraceClient.contentHash(content)
);

Rust

cargo add ptrace
use ptrace::PtraceClient;

let c = PtraceClient::new(KEY, None);
c.log_action(
  "post_reply",
  "forum.example.com",
  &PtraceClient::content_hash(s),
  None
).await;

All SDKs auto-track prev_hash and retry on 409. Cross-language signature compatibility verified.