intercom.io

Publishes a poppy.json with 1 problem to fix. Organization: Intercom.

Publishes poppy.json, with problems

1problem

HTTP 200 Version 0.1 Routes web Checked 1 hour ago First seen 16 Oct 2026

Open poppy.json ↗

Findings1 problem · 3 passed · 3 notes

Discovery

poppy.json published

Served over HTTPS at /.well-known/poppy.json.

§3

Note

Served after 1 redirect

Allowed: every hop is HTTPS, and the document still speaks for the domain requested. Final URL: https://www.intercom.com/.well-known/poppy.json

§3

Protocol version 0.1

A major.minor version this checker reads.

§3.1

Problem

organization.domain does not match the domain checked

The document says intercom.com; it was requested from intercom.io. After a redirect, the host it is served from does not count.

How to fix →

§3.1

Sign-in

Note

Signed-out browsing only

With no auth, personal agents can only browse the website as ordinary signed-out visitors.

§3.1, §5

Routes

Offers: website

At least one of agent, apis or web is listed.

§3.1

Note

Website: signed-out browsing

No browser_session_endpoint, so personal agents browse the site as ordinary signed-out visitors.

§5

poppy.json as served

0.1 KB

{
    "protocol_version": "0.1",
    "organization": {
        "name": "Intercom",
        "domain": "intercom.com"
    },
    "web": {}
}

Rules from Personal Agent Protocol draft 0.1 (updated 12 Oct 2026). Section numbers refer to the specification. The draft can change before a stable version; see the path to 1.0.