AI News·14 Nov 2026·via Dev Community

    Bots Visit Your Site Every Day. We Gave Them a Mailbox.

    Agentbadge.xyz has introduced an 'Agent Request Inbox,' a new asynchronous channel designed to let bots and AI agents submit questions and receive responses via API. This system addresses significant machine traffic, which the company reports constitutes a third of its identified clients, by providing a structured way for automated visitors to express their intent rather than being filtered or blocked.

    Websites frequently encounter substantial traffic from automated bots and AI agents, often treating these interactions as issues to be filtered. Agentbadge.xyz reports that machines already represent a third of its identified client requests, yet traditional website interfaces like HTML forms, CAPTCHAs, and email fields are fundamentally designed for human users. This mismatch meant that a significant portion of traffic had no effective way to communicate its purpose, often resulting in server errors.

    The Agent Request Inbox offers an alternative by providing a keyless, asynchronous channel where agents can submit questions via a POST request and receive a `request_id` to poll for an answer. This design bypasses human-centric elements like email replies or sessions, which agents cannot maintain. The system integrates a QA corpus that automatically resolves previously asked questions, while human operators use a pull-based console to address new queries, feeding these solutions back into the corpus.

    This approach reframes bot traffic from a nuisance to a potential source of insights, transforming what was previously blocked into a "queue of questions you never heard." By engaging machine visitors, agentbadge.xyz aims to understand their objectives, run surveys on their tool stacks, and efficiently route answers. The system also incorporates privacy measures, such as rate-limiting via hashed fingerprints and time-to-live for payloads, to manage anonymity and data retention.

    Share this article

    Go deeper
    Original reporting by Dev CommunityWe don't republish, read the full story →

    Related reading

    6 stories