llms.txt
Compare with other sites' llms.txt files →# What Did My Agent Do?
> Local checker for logs and signed records. Paste logs, traces, JSON payloads, signed records, or plain-English incident descriptions and see what is observable, what another party can independently verify, and what evidence is missing. Signed records (compact JWS) are signature-verified in the browser with native WebCrypto Ed25519. No signup. Pasted input is never uploaded; the only network request is an issuer-key lookup you explicitly trigger, with the URL shown first.
## What this site does
This site helps anyone working with AI agents understand the difference between internal observability and cross-boundary evidence. It provides:
- An analyzer that classifies input and returns an evidence scorecard
- A logs-vs-signed-record comparison for the same sample interaction
- Hard questions for disputes, incidents, and audits that logs alone cannot settle
- Methodology and source links that document scoring rules and limitations
- A collapsible technical background on how signed records work
## PEAC record surfaces you can test
The analyzer offers a realistic sample for each major PEAC record surface, and shows what is observable, what is independently verifiable, what is missing, and the ideal signed-record shape:
- **API call**: did this API return that result?
- **MCP tool run**: did this tool run with this input/output?
- **Agent action**: what did the agent actually do?
- **Gateway decision**: why was this request allowed, denied, or sent to review? (See the Gateway Decision Evidence profile for terminal access decisions within a gateway decision boundary.)
- **Payment event**: what was authorized vs captured/settled?
- **Provisioning event**: who created/changed access, config, or entitlement?
## Key concepts
- **Cross-party evidence**: Evidence that travels across organizational boundaries and can be verified by any party, unlike logs and traces which stay local.
- **Signed records**: Cryptographically signed records (Ed25519, compact JWS) returned by APIs, MCP servers, and tools after processing an agent request.
- **Offline verification**: Records are verified locally with the issuer's public key. No dependency on any central authority. Works offline once public keys are available or bundled.
- **Evidence scorecard**: A breakdown of what is observable, what is independently verifiable, what evidence is missing, and what to collect next. Uses client-side heuristics to classify input and estimate evidence strength.
- **Gateway Decision Evidence**: A formal profile for issuer-controlled gateway observation over the shipped access-decision record type, standardizing terminal access decisions (allow, deny, review) within a gateway decision boundary.
- **Merkle commitment**: RFC 9162 CT-style sorted-set commitment over receipt digests for workflow-level evidence bundles and inclusion proofs.
- **Replay guard**: Optional bounded-dedup replay guard classifying verified records as fresh, replayed, or outside-window.
## Analyzer details
The structural scorecard (logs, traces, JSON) is heuristic: it inspects structure and fields only. For signed records (compact JWS), the page additionally verifies the Ed25519 signature in the browser using native WebCrypto, against a key you paste (JWK/JWKS) or an issuer key you explicitly choose to resolve.
### Input types
- Logs (timestamped lines, status codes, agent/tool references)
- Trace / request (HTTP methods, trace IDs, headers, timing)
- JSON payload (structured data with issuer, timestamp, policy fields)
- Signed record (JWS compact serialization with base64url-encoded header/payload)
- Plain English (natural language incident or event descriptions)
### Scorecard columns
- **Observable**: What is visible inside your system
- **Independently verifiable**: What another party could verify
- **Missing**: What evidence properties are absent
- **Next steps**: What to collect or do next
## The open protocol underneath
This site uses PEAC Protocol (v0.16.4), an open protocol (Apache-2.0) for portable, verifiable interaction records across agent, tool, API, and cross-runtime workflows. 36 published TypeScript packages, 13,149 tests, 290 conformance requirement IDs. Wire format: interaction-record+jwt (compact JWS, Ed25519). I-JSON (RFC 7493) enforced on both issuance and verification. PEAC Ed25519 verification profile with cofactorless verification, small-order denylist, and admissibility checks on both A and R points. kid bounded by UTF-8 bytes (max 256). Browser verifier with local supplied-key verification (zero network, zero persistence).
PEAC does not replace auth, payment rails, observability platforms, or MCP/A2A runtimes. It adds signed records alongside those systems.
## Maintainer
Maintained openly by Originary and community contributors. Verification does not depend on any commercial vendor.
## How signed records work
1. **Publish policy**: Services expose machine-readable terms and policy at the edge.
2. **Return a signed record**: When an agent request is processed, the service returns a signed record of what happened.
3. **Verify anywhere**: The receiver verifies the record locally using the issuer's public key.
4. **Keep or bundle evidence**: Use the record for incident review, disputes, compliance, or cross-party workflows.
## Who benefits from this
- Incident response teams
- Customer and vendor support teams handling disputes
- Payment and authorization reviewers
- Audit, legal, and compliance stakeholders
## FAQ
### How does verification work?
For signed records (compact JWS), the page verifies the Ed25519 signature in your browser with native WebCrypto, against a key you paste (JWK/JWKS) or an issuer key you explicitly choose to resolve. It enforces alg EdDSA (rejecting none, HS*, and RS*) and verifies the exact base64url(header).base64url(payload) signing input. The structural scorecard for logs, traces, and JSON is heuristic. A valid signature proves the issuer and integrity of a record, not that its claims are true.
### Does this replace auth, observability, or payment systems?
No. Signed records work alongside those systems.
### Is the evidence score precise?
The analyzer uses client-side heuristics to classify input and estimate evidence strength. It checks for structural properties like signatures, timestamps, issuer fields, and policy references. The score reflects what evidence properties are detectable in the input, not a formal security audit.
### Is this tied to PEAC or Originary?
This checker is a standalone public utility. It uses PEAC concepts in the background, but you can use the site without adopting PEAC or any commercial product.
### What happens to my pasted data?
Analysis and signature verification run entirely client-side. Your pasted input is never uploaded, stored, or sent to any server. The only network request the page can make is an issuer-key lookup you explicitly trigger, and the exact URL is shown before your browser requests it.
## Links
- Homepage: https://whatdidmyagentdo.com
- Methodology: https://whatdidmyagentdo.com/methodology
- Signed record verifier: https://whatdidmyagentdo.com/signed-record-verifier
- Verify an agent action: https://whatdidmyagentdo.com/verify-agent-action
- MCP tool call audit: https://whatdidmyagentdo.com/mcp-tool-call-audit
- Agent payment dispute: https://whatdidmyagentdo.com/agent-payment-dispute
- API response provenance: https://whatdidmyagentdo.com/api-response-provenance
- Incident review evidence: https://whatdidmyagentdo.com/incident-review-evidence
- PEAC Protocol: https://www.peacprotocol.org
- PEAC Documentation: https://www.peacprotocol.org/docs
- PEAC Specification: https://www.peacprotocol.org/docs/specs/protocol-behavior
- Tool source: https://github.com/jithinraj/wtfdidmyagentjustdo
- PEAC protocol source: https://github.com/peacprotocol/peac
- Originary: https://www.originary.xyz
## Technical details
- Wire format: interaction-record+jwt (compact JWS)
- Protocol version: 0.16.4
- Signature algorithm: Ed25519 (PEAC Ed25519 verification profile, cofactorless, small-order denylist, A and R admissibility)
- I-JSON validation: RFC 7493 enforced on both issuance and verification
- kid: bounded by UTF-8 bytes (max 256)
- Replay guard: optional bounded-dedup (iss, jti, iat) classification (fresh / replayed / outside-window)
- Merkle commitment: RFC 9162 CT-style sorted-set over receipt digests
- Browser verifier: local supplied-key verification with zero network and zero persistence
- Go SDK: Wire 0.2 kid profile on issuance and verification, full media-type acceptance
- License: Apache-2.0
- Language: TypeScript (36 published packages, 13,149 tests, 290 conformance IDs) + Go SDK
- Verification: Offline once issuer's public key is available (JWKS)
- Discovery: /.well-known/peac-issuer.json -> jwks_uri -> JWKS -> verify