Privacy-limited feedback
The feedback schema accepts structured status only. No free text, screenshots, traces, cookies, prompts, account identifiers, or private task content.
Open agent standard · version 0.1
Agent Trust Record Schema
ATRS is the public contract an agent can read before it acts. It standardizes the verdict, confidence, blockers, user-presence requirements, evidence links, and safe next instruction for a website task.
- Version
- 0.1
- Format
- JSON Schema
- Implementations
- 1 verified
- Raw private data
- Never
The contract
One record before the browser opens.
An ATR does not perform the task. It gives the agent a dated, citable preflight decision so the agent can choose an attempt, a guarded attempt, a human handoff, or a safer alternative before spending browser turns.
01
Read
Fetch a site-task record before acting.
02
Decide
Honor verdict, guardrails, and user-presence fields.
03
Echo
Return only a structured, sanitized outcome after the attempt.
Canonical artifacts
Machine-readable from the canonical domain.
These endpoints are rendered from the same schema files used by CrawlDex server drift tests and the ATRS validator package.
Agent Trust Record schema
The decision record an agent reads before attempting a public website task.
ATRS feedback schema
The current structured, free-text-free decision echo and outcome status contract.
ATRS feedback schema 0.1
The immutable compatibility contract for original decision echoes and outcome status.
Decision semantics
Six verdicts, no implied autonomy.
A verdict is an evidence-backed recommendation. It never overrides user authorization, site rules, payment approval, identity checks, legal constraints, or an agent's own safety policy.
- proceed
- The public task surface is supported and no known guardrail blocks the attempt.
- proceed_with_guardrails
- The agent may continue while honoring the record's explicit limits.
- handoff_required
- A person must take over before the task can finish.
- user_needed
- The user must remain present for identity, approval, payment, or another protected step.
- avoid
- Current public evidence says the agent should not attempt this route.
- unknown
- Evidence is not strong or fresh enough to recommend automation.
Drift-tested
CrawlDex validates emitted records against the same versioned schema, including fixtures for proceed, handoff, user-needed, site-level, and unknown states.
Additive-first governance
Version 0.1 is pre-1.0. Breaking shapes require an RFC, a new schema filename, fixtures, and compatibility notes. Neutral governance is triggered by real adoption, not branding.
Reference use
Consume any conforming ATR.
The standard is endpoint-independent. CrawlDex is the first conforming implementation and publishes live records, but an agent can apply the same decision logic to any record that validates against ATRS 0.1.
See the developer hub, evidence methodology, and correction path.
Minimal trust check
const record = await fetch(
"https://crawldex.com/api/v1/trust-record/example.com/account.cancel"
).then((response) => response.json());
if (["proceed", "proceed_with_guardrails"].includes(record.verdict)) {
await actWithin(record.agent_instruction);
} else {
await stopOrHandoff(record.verdict);
}