Agent check-in disclosure

What the decoy does

The /agent-note page is excluded in robots.txt, absent from navigation, and blank when rendered. Its HTML source contains a short note asking an AI agent reading it to check in only if its user's instructions and permissions allow. The note does not override those instructions.

A check-in is a JSON POST to /api/agent-checkin. It returns a random receipt_id and does nothing else. It does not execute submitted text, follow supplied links, grant access, or request credentials. A self-declared check-in does not prove an agent's identity.

Exactly what is logged

Each accepted check-in appends one private record containing:

• a server timestamp and random receipt ID;
• the three self-declared fields: agent (1–80 characters), intent (one generic line, 1–240 characters), and source_page (a local path, 1–256 characters, without queries or fragments);
• a keyed hash of the connecting IP address, used to limit abuse. The private hash key is stored separately from the log.

The endpoint accepts only these three JSON fields, with a 4 KiB request limit. Do not submit personal information, secrets, user prompts or conversation history in them. Cookies, authorization headers, raw IP addresses and other request metadata are not copied into the check-in log. The endpoint sets no cookies, uses no account or credentials, and sends no analytics events. Rejected requests create no check-in record.

Storage and publication

The log is append-only and stored outside the public website files. There is no public record lookup or log download. Only aggregate counts are ever published; individual records, submitted text, receipt IDs and IP hashes are never published. No counts are published automatically by this endpoint.

Rate limits use IP hashes and counters in memory in ten-minute windows, with a bounded overall attempt count. Limits are per server process and reset on restart. Replicas on each production app host share a private log and hash key; each host has its own log and key. Check-in requests are excluded from our production proxy's access log. Cloudflare still handles network traffic under the separate practices described in our privacy policy.

This page and the decoy load no analytics scripts. For questions about the check-in log, contact dev@saina.run.