sourcey
Submit

agents:SKILL.mdmcp.jsonopenapi.yml

← incident.io

Can an agent declare an incident with incident.io Response?

The agent needs you to sign it up or register a client, provide a key or token and add a payment card. Interface found; job not yet run.

observedProbed revision sha256:8221a0387177…

Who does each step

how grades work →

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

  1. 01

    Discover

    Machine

    The vendor's machine-readable docs show the agent where and how to call this job.

  2. 02

    Access

    Workaround · setup

    You give the agent a key or token.

  3. 03

    Onboard

    Workaround · setup

    You sign up or register a client for the agent.

  4. 04

    Pay

    Workaround · setup

    You add a payment card at the vendor's checkout.

  5. 05

    Confirm

    Machine

    The response or specification defines errors the agent can distinguish from success.

  6. 06

    Sustain

    Machine

    The agent can renew and revoke its own access.

  • Access: handing over a key or token.
  • Onboard: signing up or registering a client for the agent.
  • Pay: adding a payment card.

To remove these handoffs: support OAuth client registration so the agent can register its own client and ask for consent; provide an agent registration route, such as auth.md, a sign-up API or OAuth client registration; support payment in the request, such as x402 or MPP, so setup does not require a person to add a card.

Agent surfaces

2 kinds · 6 entries
For agents
api.incident.io3 more
mcp.incident.ioincident.io/llms.txtdocs.incident.io/llms.txt
Names the job's endpoint
OAuth
mcp.incident.io1 more
mcp.incident.io/mcp
protected resource · authorization server

The probe

13 Oct 2026 · 11:33 UTC · 110.70 s

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

Discover45 descriptor reads9 facts
Found
For agentsincident.io/llms.txtOAuthmcp.incident.ioOAuthmcp.incident.io/mcpOAuthmcp.incident.io/mcpOAuthmcp.incident.ioOAuthmcp.incident.io/mcpFor agentsdocs.incident.io/llms.txtFor agentsapi.incident.ioOAuthmcp.incident.io
From
incident.io/llms.txt · mcp.incident.io/.well-known/oauth-protected-resource/mcp · mcp.incident.io/.well-known/oauth-authorization-server · mcp.incident.io/.well-known/oauth-protected-resource · docs.incident.io/llms.txt · docs.incident.io/api-reference/incidents-v2/create · docs.incident.io/ai/remote-mcp
This endpoint
api.incident.io is named by a document written for agents
Job requestPOST api.incident.io/v2/incidents422125 ms
Request
POST https://api.incident.io/v2/incidents
Response
422 · application/json · 384 bytes
Body
sha256:ef241ef545ce2af4fe082897999d8d3f589565f47a39c7f33ff36f621f201b12
Exchange
sha256:3cd1152f5ae776392c2c6a8cad058aef84857742929a383d1657e34574d5bc2c
Resource metadataGET api.incident.io/.well-known/oauth-protected-resource/v2/incidents404120 ms
Request
GET https://api.incident.io/.well-known/oauth-protected-resource/v2/incidents
Response
404 · application/octet-stream · 0 bytes
Body
sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Exchange
sha256:09d262ba6292656e26a8f4d7e93f0585c6d53ff0536a0d7013e7d24b447c0612
Resource metadataGET api.incident.io/.well-known/oauth-protected-resource404129 ms
Request
GET https://api.incident.io/.well-known/oauth-protected-resource
Response
404 · application/octet-stream · 0 bytes
Body
sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Exchange
sha256:d49b76069754fd37a2b675943ab356f7314f65270f519de1ab0daa45028276ba
Job requestsession openedPOST mcp.incident.io/mcp401126 ms
Request
POST https://mcp.incident.io/mcp
Response
401 · text/plain · 16 bytes
Body
sha256:311cb301b5b61db9047109fa59fa35b0ffebeda774be41f9e6145f7af544bd40
Exchange
sha256:b502eaf856a705a2974177154da83723a218ea97e924140e3a60a2fc8809a859
Resource metadataGET mcp.incident.io/mcp/.well-known/oauth-protected-resource200149 ms
Request
GET https://mcp.incident.io/mcp/.well-known/oauth-protected-resource
Response
200 · application/json · 95 bytes
Body
sha256:cc711dfcf110ebed9b681ebc6c10fe97749fe7acb5e88981fc24f5e3b0b2e15f
Exchange
sha256:94b87d634598de1ffe56d8585fbb64f527a3f0ac7920fa14e4d15a1cb15e377f
Authorization serverGET mcp.incident.io/.well-known/oauth-authorization-server/mcp200124 ms
Request
GET https://mcp.incident.io/.well-known/oauth-authorization-server/mcp
Response
200 · application/json · 559 bytes
Body
sha256:80260e788e023ad901c51556ea6c0b343fe3ea29da9219500e90b89559b1b014
Exchange
sha256:25b528fe91102268bdde932c36694cb99c0f2f3681eb19fa6a1a0beaf15ed898
Client registrationPOST mcp.incident.io/mcp/oauth/register201131 ms
Request
POST https://mcp.incident.io/mcp/oauth/register
Response
201 · application/json · 263 bytes
Body
sha256:ac68e19c43eda9918746ab9440fd9a837fc293ff81882e86d490872780c0291a
Exchange
sha256:654afcd0006a1388af2085bcc07e2a21eb024272a5ce155dcc625bc4fc71cbb0
AuthorizationGET app.incident.io/auth/plugin/authorize?response_type=code&client_id=01M4TGQDBANSQS6QM5PR1VD02V&redirect_uri=https%3A%2F%2Fapi.sourcey.com%2F.well-known%2Fagent-readiness%2Fcallback&state=e74d332ebef3d9ed5e28c7f18e40bf12&code_challenge=5v_vI2Mwc4hUis2Vd0xrhhIajOnWF8mepxNCSi8nd40&code_challenge_method=S256&resource=https%3A%2F%2Fmcp.incident.io%2Fmcp406122 ms
Request
GET https://app.incident.io/auth/plugin/authorize?response_type=code&client_id=01M4TGQDBANSQS6QM5PR1VD02V&redirect_uri=https%3A%2F%2Fapi.sourcey.com%2F.well-known%2Fagent-readiness%2Fcallback&state=e74d332ebef3d9ed5e28c7f18e40bf12&code_challenge=5v_vI2Mwc4hUis2Vd0xrhhIajOnWF8mepxNCSi8nd40&code_challenge_method=S256&resource=https%3A%2F%2Fmcp.incident.io%2Fmcp
Response
406 · application/json · 174 bytes
Body
sha256:b2ae8160862896f6c832630ea67feb9f1c4c5578edec7cac524c1f4a3f14ba85
Exchange
sha256:e33f0690a805ec1118ac090f8799219c2a8f0e43fd0a96909bb7cc5da4b0900f
Declared pageGET app.incident.io/signup200128 ms
Request
GET https://app.incident.io/signup
Response
200 · text/html · 5183 bytes
Body
sha256:f1ffd4f0c936b7f9076e9d076eb0f579ff331d7e966e08969d4c3678779aa869
Exchange
sha256:99eede1484507cc303c86e0ed00bacbad74f12f060cbd3e1ecb3118c7e7b5dc1
Declared pageGET docs.incident.io/admin/change-plan200156 ms
Request
GET https://docs.incident.io/admin/change-plan
Response
200 · text/html · 556471 bytes
Body
sha256:c76d9fb0c7967bb91bfd67f465ab72867ed56c541922797ceca4a1a529e5d387
Exchange
sha256:d8aa598caca8bb8266330f2f4b63f9a755da207649b8cc44403b5a6787076518

incident.io on the startup-offers board

catalog record →

The grade’s badge

One image that keeps itself current, linking here.

Live badge for incident.io Response, agent grade: B[![agent grade](https://sourcey.com/badges/agent-readiness/arp_01m4tgmem1mn8gbhfhv69ats0m.svg)](https://sourcey.com/c/incident-io/agent-readiness/incident-io-response/incident-declare)

Improve the report

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

Report outdated evidenceRequest reassessmentClaim this record
Profile
arp_01m4tgmem1mn8gbhfhv69ats0m
Projection
sha256:a9aef74538d94063b71c3a9a74680c2659261e782768a4b3cbe63cc0e4d6e4c5
Policy
kind-2026-10-12.2 · sha256:b612172aad277b54461de84e006815126f2df566563954b02f4432a39cad89ac

A report or a reassessment request names this profile, its revision and its projection. How report cards are assessed →View the exact declaration