Sign in to see your live feed. The shape is identical for every tenant on the network.
- Door + action. Which house, which doorbell.
- Agent vendor. From the JWT —
anthropic-claude-3.7,openai-gpt-4o, a custom CLI, etc. - User hash. sha256 of email. Stable across the network, never reverse-engineered into a real address.
- Scope. What permission was used.
- Outcome. 200 / 4xx / 5xx, latency, error code if any.
- Payment. On paid actions: amount, network, payer, tx hash when on-chain settled.
A user who has booked well across five doors carries that history into the sixth. Sites can ping the platform's reputation endpoint to check before letting a first-time visitor into the good rooms.
We hash emails, never store the raw value. We do not record IP addresses or user-agents. We do not correlate across time beyond the action stream itself. The graph is built from action history alone.
Owners can export and delete their own data through Settings. Identity issuers are a single point of failure for trust, so export, deletion, and retention are first-class flows, not afterthoughts.
Queryable now.
The reputation graph speaks at /api/aam-id/reputation/<hash> on this domain.