← Intercom

Can an agent create a support ticket with Intercom Tickets?

A person steps in at setup: a person hands over a key or token, a person signs up or registers a client for it, a person puts a card on file and a person replaces or revokes its access when it must change. Job reachable, not yet run.

observedProbed revision sha256:8735dc778536…

Who does each step

Whether the agent handles it alone or a person has to step in.

  1. 01

    Discover

    Machine

    The vendor's own machine-readable documents lead an agent to the job's interface.

  2. 02

    Authority

    Workaround · setup

    A person hands the agent a key or token.

  3. 03

    Onboard

    Workaround · setup

    A person signs up, or registers a client, for the agent.

  4. 04

    Pay

    Workaround · setup

    A person puts a card on file once, at the vendor's checkout.

  5. 05

    Confirm

    Machine

    A failure comes back typed, in its answer or as its spec declares, so an agent can tell a failure from a success.

  6. 06

    Sustain

    Workaround · setup

    A person replaces or revokes the agent's access when it must change.

A person once, at Authority: handing over a key or token.

A person once, at Onboard: signing up or registering a client for the agent.

A person once, at Pay: paying for it.

A person once, at Sustain: renewing, replacing or revoking its access.

Not A+ yet: OAuth that lets an agent register its own client would turn handing over a key or token into a one-time consent; a way for agents to register (auth.md, a sign-up API, or OAuth with client registration) would let the agent register itself; payment inside the request (x402 or MPP) would let an agent pay its own way; a key-management API, or OAuth refresh and revocation, would let the agent keep its access alive.

Agent surfaces

4 kinds · 8 entries
APINames the job's endpoint
API catalogapi-catalog
MCPserver card

The probe

13 Oct 2026 · 10:01 UTC · 57.35 s

Each request it sent and what came back; the descriptors it read, counted, with what they named.

Discover31 descriptor reads8 facts
Found
API catalogwww.intercom.comMCPmcp.intercom.com/mcpFor agentswww.intercom.com/llms.txtFor agentsdevelopers.intercom.com/llms.txtAPIapi.intercom.ioAPIapi.intercom.ioAPIapi.eu.intercom.ioAPIapi.au.intercom.io
From
www.intercom.com/.well-known/api-catalog · www.intercom.com/.well-known/mcp/server-card.json · www.intercom.com/llms.txt · developers.intercom.com/llms.txt · developers.intercom.com/docs/guides/tickets/build-a-ticket-form.md · developers.intercom.com/_bundle/docs/references/@2.15/rest-api/api.intercom.io.yaml
This endpoint
api.intercom.io is named by a descriptor it read
Job requestPOST api.intercom.io/tickets40150 ms
Request
POST https://api.intercom.io/tickets
Response
401 · application/json · 143 bytes
Body
sha256:250c52197bd47ed8de9719b1970c095dc12433435560d5b9da23b8041b67cf0a
Exchange
sha256:bf65d8dc1aaf745b4abc5feff0cfc74c5631f645e3c78d32b771ddeeed51ccae
Resource metadataGET api.intercom.io/.well-known/oauth-protected-resource/tickets40443 ms
Request
GET https://api.intercom.io/.well-known/oauth-protected-resource/tickets
Response
404 · application/json · 199 bytes
Body
sha256:918268bde29349519027d36ab972e5b086741a6ffe4542598362c31e332b86e9
Exchange
sha256:a0a13d9ba96a8e10b5e2d06c8602cbf0a7daa9093765a3a5ae85451f3af22ac3
Resource metadataGET api.intercom.io/.well-known/oauth-protected-resource40448 ms
Request
GET https://api.intercom.io/.well-known/oauth-protected-resource
Response
404 · application/json · 199 bytes
Body
sha256:918268bde29349519027d36ab972e5b086741a6ffe4542598362c31e332b86e9
Exchange
sha256:5c2f972b2b825c8b5345abd9d53b7658475d5cf061c2e6da12e2ae2abc48c272
Declared pageGET www.intercom.com/signup307211 ms
Request
GET https://www.intercom.com/signup
Response
307 · text/html · 0 bytes
Body
sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Exchange
sha256:4733337b9f2d1ebc33e297ece71b4a8dad8860c3194401305d81de24ee5f629a
Declared pageGET www.intercom.com/pricing200512 ms
Request
GET https://www.intercom.com/pricing
Response
200 · text/html · 1451157 bytes
Body
sha256:ad9ede05d1a71da21b121b45054d9e0b673428e94e9e7bf5cdc1f60a090046b0
Exchange
sha256:5e8348ab1f800c44ce6f93a7c589827acbf2036c2fde55e1fff1e2659bb7eb5c

Intercom on the startup-offers board

The grade’s badge

One image that keeps itself current, linking here.

Live badge for Intercom Tickets, agent grade: B[![agent grade](https://sourcey.com/badges/agent-readiness/arp_01m4tbbmrrd0vftg22s06bgjkb.svg)](https://sourcey.com/c/intercom/agent-readiness/intercom-tickets/support-ticket-create)

Improve the report

Correct it, probe it again, or improve the path.

Profile
arp_01m4tbbmrrd0vftg22s06bgjkb
Projection
sha256:84a14c7c63be384cc9379993a71808324b6bfbe9083facd69fb5ef3ad3b79d38
Policy
kind-2026-10-12.2 · sha256:b612172aad277b54461de84e006815126f2df566563954b02f4432a39cad89ac