# incident.io API > incident.io is an incident response, on-call, alerting and status page service. Agents reach it through a REST API at api.incident.io with an OpenAPI description and seven SDKs, a hosted MCP server and the inc CLI. - Canonical: https://www.anchorterminal.com/tools/incident-io - Markdown: https://www.anchorterminal.com/tools/incident-io.md (~7,600 tokens) - Slim: https://www.anchorterminal.com/tools/incident-io.min.md (~1,930 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/incident-io.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade B · 68.9/100 · rank #204 of 950 · #3 in Observability & incidents · not agent-ready · confidence high** ## Assessment The REST API has a public OpenAPI description with 284 operations, numeric rate limits, `Retry-After` on 429 and required idempotency keys on seven create calls. API and MCP access need the Team plan or higher, so the free Basic plan cannot be used by an agent, and audit logs are Enterprise only. ## Facts | Field | Value | | --- | --- | | Vendor | Pineapple Technology Ltd. (incident.io) (https://incident.io) | | Kind | HTTP API | | Category | Observability & incidents (https://www.anchorterminal.com/categories/observability) | | Transport | HTTP | | Endpoint | `https://mcp.incident.io/mcp` | | Auth | OAuth or key · The REST API takes an API key as a Bearer token. An admin creates an organisation key in Settings and picks its permissions, 13 of which can be limited to named teams. A user key has its owner's current role. Keys are shown once and do not expire. The MCP server takes the same keys, or OAuth with PKCE for a person, which an admin must enable and which lasts 28 days. Access is self-serve on a paid plan, with no app review. | | Pricing | Paid ($19 / seat-mo) · API, webhooks and MCP are not included in the free Basic plan. Team is $19 per user a month for incident response ($15 with the annual discount) plus $10 for on-call. Pro is $25 plus $20 for on-call, billed yearly through sales. Enterprise is quoted. API calls are not metered. The terms define a 14-day trial, which the docs say sales sets up for Pro and Enterprise. No sandbox below Enterprise (checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the API reference, the OpenAPI description or the pricing page (checked 2026-10-09). | | Licence | Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT | | Packages | npm: `@incident-io/sdk`; pypi: `incident-io` | | Source | https://github.com/incident-io/sdk-ts | | Docs | https://docs.incident.io/api-reference/introduction | | llms.txt | https://docs.incident.io/llms.txt | | Last release | 2026-10-08 | | npm downloads / week | 1,318 | | API | REST at https://api.incident.io, OpenAPI 3.0.3 with 284 operations on 162 paths (126 GET, 79 POST, 40 PUT, 38 DELETE, 1 PATCH). Versions are per resource in the path, such as `/v2/incidents` and `/v3/catalog_entries` | | Coverage | Incidents, updates, timeline items, alerts, alert sources and routes, escalations and escalation paths, schedules and overrides, catalogue, status pages, workflows, post-mortem documents, follow-ups, users, teams, API keys and telemetry data sources | | MCP server | Hosted at https://mcp.incident.io/mcp with 91 tools in the docs table. OAuth with PKCE for people (the grant lasts 28 days) or an API key for automation. An admin enables it in settings. Team, Pro and Enterprise only | | Credentials | Organisation API keys with chosen permissions, 13 of which can be limited to named teams, and user API keys that take the owner's current role. Bearer header. Keys do not expire. A user key pushed to a public GitHub repository is deleted automatically | | Rate limits | 1,200 requests a minute per key. List incidents 60 a minute, update catalogue entry 300 a minute, bulk catalogue update 60 a minute. Incident creation 10 an hour with a chat channel, 300 an hour without | | Errors | JSON with `type`, `status`, `request_id` and an `errors` list of `code`, `message` and `source.field`. 429 carries `Retry-After` in seconds and a `rate_limit` object | | Pagination | Cursor, `page_size` (default 25, maximum set per endpoint, 250 for incidents) and `after`, on 41 list operations. Configuration lists return everything in one response | | Idempotency | `idempotency_key` is a required body field on create calls for incidents, incident updates, timeline items, escalations, status page incidents, maintenances and retrospective incidents | | SDKs | Go, TypeScript (`@incident-io/sdk` 2.15.0), Python (`incident-io` 2.14.0, Python 3.11 or later), Rust, Ruby, PHP and .NET, generated from the OpenAPI description, MIT. Terraform and Pulumi providers | | CLI | `inc`, MIT, v0.4.25 on 9 October 2026. JSON output, `inc describe` for a schema of every command, `--dry-run`, and `inc api` for any endpoint | | Compatibility | The docs promise no breaking changes to existing endpoints, a new path version when one is needed, and three months for integrators to move off a deprecated endpoint | | Audit | Audit logs on Enterprise only, kept one year, by CSV export or log stream to a SIEM. API actions are attributed to the key, or to the person for a user key | | Hosting | Google Cloud, europe-west1 (Belgium) with a standby in europe-west4 (Netherlands), per the security FAQ. 20 sub-processors listed on 27 July 2026, 17 in the United States | | Certifications | SOC 2 Type I and II and GDPR compliance claimed on incident.io/security, with yearly third-party penetration tests. The trust centre was not read | | Status | status.incident.io with 43 components, among them API and MCP, with uptime from July to October 2026 and Atom and RSS feeds | | Capabilities | observability.incidents, work.oncall | | Tags | hosted, rest, openapi, llms-txt, mcp, api-key, oauth, incidents, on-call, status-pages, cli, typescript, python, go, status-page, sla, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/incident-io.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: high. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 90 | 18.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 88 | 14.3 | | Agent ergonomics | 13% | 16.2 | 75 | 12.2 | | Security & auth | 14% | 17.5 | 64 | 11.2 | | Payments & pricing | 10% | 12.5 | 10 | 1.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 83 | 7.3 | | Transparency & trust (editorial 72, provenance 79) | 7% | 8.8 | 76 | 6.7 | | Negative events | up to −15 | up to −15 | 2026-04-09, 2026-06-26 and 2026-09-30: the API changelog records the request property `time_to_ack_seconds` removed from `POST /v2/escalation_paths`, the request property `version` removed from `POST /v2/alert_routes`, and the response property `layer_id` removed from `GET /v2/schedules`, each with no earlier deprecation entry in a changelog that starts on 5 January 2026. The docs say existing endpoints get no breaking changes. Whether customers were told another way was not established, so the deduction is 2 (https://docs.incident.io/api-reference/changelog). | -2 | | **Total** | | | | **68.9 → B** | ### Why each score - Reliability 90: Scored as a hosted API. status.incident.io lists 43 components, API and MCP among them, with uptime from July to October 2026 (20). The API component shows 100 per cent. The feed lists six incidents since 16 July 2026, one of which broke listing alerts in the public API on 18 August until a rollback, with no duration given, and none marked as an outage of the API (20). Limits are published with numbers, 1,200 requests a minute per key and lower figures for eight endpoints (15). 429 carries `Retry-After`, the body recommends exponential backoff, and seven create calls require an `idempotency_key` (15). The SLA commits to 99.9 per cent a month on Pro and Enterprise (10). The API carries no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 88: OpenAPI 3.0.3 description, public at api.incident.io/v1/openapiV3.json per the docs and read from docs.incident.io/openapi/latest.json, 284 operations and 777 schemas (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a description, but the median is 65 characters and few say when not to use a call. List incidents is the exception, with worked filter examples (12). 262 enums, required fields marked and two free-form objects in the whole file (13). 4,014 example values and thirteen error statuses on every operation, though the shared error example pairs an unrelated code and message (13). Versions sit in the path per resource and the changelog is generated from the description file (15). - Agent ergonomics 75: Scored for the REST API. `page_size` sets response size, but no field selection was found and incident objects are large. The description file is 5.4 MB, with per-resource files as the smaller route (12). Cursor pagination on 41 list operations and operator filters such as `status_category[one_of]` (18). Errors carry a code, a message, the field at fault and a `request_id` (18). `idempotency_key` is required on seven create calls, and updates by PUT have no key (14). Seven official SDKs and a CLI with JSON output, with `idempotency_key` and `visibility` required to create an incident (13). - Security & auth 64: Organisation keys carry chosen permissions, 13 of 36 scopable to teams, can be rotated and are shown once. User keys take the owner's role and die with the account. 30 for that, less the checklist's 10 because alert event and heartbeat endpoints accept the alert source token in a `token` query parameter. The API key itself travels only in the header (20). A `viewer` permission gives read-only keys and the MCP status page tool only drafts, but no confirmation step guards destructive API calls (15). Alert payloads and incident text are untrusted content. The docs cover redaction of sensitive data, and no injection guidance for API consumers was found (4). Audit logs are Enterprise only, kept one year, exported or streamed, and API actions are attributed to the key (10). security.txt valid to July 2027, a disclosure policy with a five-working-day reply, SOC 2 Type I and II claimed, yearly penetration tests, no paid bounty (15). - Payments & pricing 10: No x402, MPP or L402 (0). Plan prices per seat are public, Team at $19 and Pro at $25 a user a month, with no per-call price (10). The Basic plan is free, but the pricing page marks API, webhooks and MCP as not included, and the docs route trials through sales (0). A person signs up, pays and creates a key in the dashboard (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 83: The API changelog's newest entry is 8 October 2026 (30). 60 dated entries between 2 July and 8 October 2026 (20). A public changelog, support by email and a Slack community, with reply times not checked (10). Seven official SDKs generated from the description file, TypeScript 2.15.0 and Python 2.14.0 both tagged 8 October 2026 (15). The SDK and CLI repositories have test workflows, and the two SDKs read were first tagged in September 2026 and reached a second major version within two weeks (8). - Transparency & trust 76: Closed service under published Terms and Conditions effective 1 August 2026, with the SDKs, CLI and skills plugin under MIT (17). Privacy policy, DPA, sub-processor list and an AI data handling page are public. The terms limit training on customer content to the customer's own benefit. The security FAQ's statement that no data leaves Europe disagrees with a sub-processor list naming 17 processors in the United States, and retention is stated in general terms (20). Deprecated endpoints carry a removal date in their descriptions and the docs give integrators three months, but the changelog shows removals with no earlier entry (17). 20 sub-processors with locations and purposes, hosting regions named, 15 days' notice of changes in the DPA (18). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/incident-io.md (JSON https://www.anchorterminal.com/fixes/incident-io.json) ### What we couldn't check - The lead said incident.io has no MCP server. The docs describe a hosted one at https://mcp.incident.io/mcp with 91 tools. This listing grades the REST API and records the MCP server as a second surface. - unchecked: the MCP tool schemas and annotations, which are only available through tools/list with an account - unchecked: trust.incident.io, which is drawn by script, so the SOC 2 claim rests on the security page and the security FAQ - unchecked: the domain registration date, because rdap.org answered 404 for incident.io - unchecked: PyPI download figures, because PyPI's robots.txt disallows `/pypi/` - unchecked: whether a Team trial exists without a card. The terms define a 14-day trial and the docs mention trials only for Pro and Enterprise through sales - The Team price shows as $19 with a second figure of $15 beside an annual discount switch. We read $15 as the yearly-billed price - Whether the three removals in the changelog were announced to customers by another route was not established - The Go, Rust, Ruby, PHP and .NET SDK repositories were not read ### Sources - API introduction with authentication, rate limits, pagination, errors and compatibility: (seen 2026-10-09) - OpenAPI description file, read in place of the rendered reference pages: (seen 2026-10-09) - deprecated endpoints description file: (seen 2026-10-09) - API changelog: (seen 2026-10-09) - docs index for agents: (seen 2026-10-09) - API key permissions: (seen 2026-10-09) - user API keys: (seen 2026-10-09) - remote MCP server, tool table and plans: (seen 2026-10-09) - SDK overview and versioning: (seen 2026-10-09) - CLI docs: (seen 2026-10-09) - audit logs: (seen 2026-10-09) - security FAQ with hosting regions: (seen 2026-10-09) - AI data handling: (seen 2026-10-09) - billing and plan changes: (seen 2026-10-09) - pricing and plan comparison: (seen 2026-10-09) - Terms and Conditions, effective 1 August 2026: (seen 2026-10-09) - Service Level Agreement: (seen 2026-10-09) - sub-processors, effective 27 July 2026: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - Data Processing Addendum: (seen 2026-10-09) - vulnerability disclosure policy: (seen 2026-10-09) - security page: (seen 2026-10-09) - security.txt: (seen 2026-10-09) - status page components and uptime: (seen 2026-10-09) - status incident feed: (seen 2026-10-09) - TypeScript SDK repository, tags and README (shallow clone): (seen 2026-10-09) - Python SDK repository, tags (shallow clone): (seen 2026-10-09) - CLI repository, tags (shallow clone): (seen 2026-10-09) - npm weekly downloads for @incident-io/sdk: (seen 2026-10-09) ## Who's behind it (provenance 79/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Pineapple Technology Ltd. | 20/20 | | Domain age | incident.io, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | mcp.incident.io | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points | 5.1/10 | | Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 | | Status page | status.incident.io | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The site footer and the legal pages carry the copyright of Pineapple Technology Ltd. The terms are governed by the laws of England and Wales. No company number was found on the pages read. The Terms and Conditions are effective 1 August 2026 and are served at incident.io/legal and incident.io/legal/terms. Orders before that date fall under legacy terms. The API answers at api.incident.io and the MCP server at mcp.incident.io. incident.io/.well-known/security.txt names security@incident.io and the vulnerability disclosure policy, and expires on 15 July 2027. rdap.org answered 404 for incident.io, so the registration date is not recorded. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://incident.io/legal/terms), read 2026-10-09, dated 2026-08-01, states 6 of the 7 things a reader expects. - To know. Says it may use customer content to train or improve models, and no opt-out was found (costs points). "incident.io may use User Content to train, tune, and improve the AI Services solely for the exclusive benefit of Customer, in order to solely make the AI Services more accurate and tailored for Customer, without requiring Customer’s separate consent." - To know. Restricts benchmarking or competitive use (costs points). "(f) access, use or view the Services for the purpose of creating a product or service that is competitive with the Services;" - Gives the date it was last updated. Last updated 2026-08-01. - Names the governing law or courts. The law of England and Wales. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Not found in the text. Says how changes to the terms are announced. - Also in the text (2026-10-08). Customers may connect agents and MCP clients through the API, and the vendor's obligations over user content stop once data is sent to such a connected system. "incident.io gives no warranty or indemnity in respect of Connected Systems, and incident.io’s obligations regarding User Content (including under the Data Processing Addendum) do not extend to data once transmitted to a Connected System at Customer’s direction." - Also in the text (2026-10-08). The subscription renews automatically for the same length, and fees for a renewal term may rise on at least 60 days' written notice. "The Subscription Fees to be charged for any Renewal Subscription Term may be increased upon at least sixty (60) days prior written notice to Customer and will only take effect at the start of such Renewal Subscription Term." - Also in the text (2026-10-08). Unless the order form says otherwise, incident.io may name the customer and use its logo on its websites, customer lists and marketing materials. "Customer agrees that incident.io is permitted to identify Customer as an incident.io customer, and to use Customer’s name and/or logo on incident.io’s websites, and in its customer lists and marketing materials" **Privacy policy** (https://incident.io/legal/privacy), read 2026-10-09, dated 2024-02-15, states 6 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2024-02-15. - Says how long data is kept. For as long as needed, with no period named. - Not found in the text. Says whether personal data is sold or shared for advertising. - Not found in the text. Gives a privacy contact. ## Live (updated 2026-10-10 02:07 UTC) - Right now: up, HTTP 401, 55 ms, checked 2026-10-10 02:07 UTC (get on `https://mcp.incident.io/mcp`, asks for auth) - Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 41 ms · p95 127 ms - Vendor status page: none, All Systems Operational - github `incident-io/sdk-ts` v2.16.0, released 2026-10-09 - npm `@incident-io/sdk` 2.16.0 - pypi `incident-io` 2.15.0, released 2026-10-09 - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/incident-io.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Team plan, incident response | $19 | per seat per month | $15 with the annual discount. On-call adds $10 | | Pro plan, incident response | $25 | per seat per month | billed yearly through sales. On-call adds $20 | | On-call only | $20 | per seat per month | sold through sales | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - OpenAPI 3.0.3 description with 284 operations, per-resource description files, llms.txt and Markdown twins of every docs page - API keys carry chosen permissions, 13 of the 36 scopable to named teams, and user keys take the owner's role - Default limit of 1,200 requests a minute per key, `X-RateLimit-*` headers on every response and `Retry-After` on 429 - `idempotency_key` is required on seven create calls, among them incidents, escalations and status page incidents - API changelog generated from the description file, with 60 dated entries between 2 July and 8 October 2026 ## Weaknesses - The pricing page marks API, webhooks and MCP as not included in the free Basic plan. Team starts at $19 per user a month - Audit logs are Enterprise only and reach the customer by CSV export or log stream, with no API to read them - Alert event and heartbeat endpoints accept the alert source token in a `token` query parameter - The changelog records three removals from live endpoints in 2026 with no earlier deprecation entry - The security FAQ says no data leaves Europe, while the sub-processor list of 27 July 2026 names 17 processors in the United States ## Before you call it (notes for agents) 1. Send `Authorization: Bearer ` to https://api.incident.io and call `GET /v1/identity` first to read the key's roles 2. Send a fresh `idempotency_key` with every create call for incidents, incident updates, timeline items, escalations and status page incidents. A repeated key returns the first result 3. Page with `page_size` and `after` until no cursor comes back. Do not stop at a short or empty page 4. Keep `GET /v2/incidents` under 60 requests a minute and wait the seconds in `Retry-After` on 429 5. Incident creation is limited to 10 an hour per key when a Slack or Teams channel is created, 300 an hour otherwise ## Connect Install: ```bash npm install @incident-io/sdk ``` First request: ```bash curl --request GET https://api.incident.io/v1/identity --header 'Authorization: Bearer ' ``` Claude Code: ```bash claude mcp add incident-io --transport http https://mcp.incident.io/mcp ``` Through letme (picks today, calling later): https://letme.dev/incident-io. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Grafana MCP Server | BB | 74.5 | 70 | observability.incidents, work.oncall | no | https://www.anchorterminal.com/tools/grafana-mcp-server.md | | Rootly MCP Server | C | 59.7 | 541 | observability.incidents, work.oncall | no | https://www.anchorterminal.com/tools/rootly-mcp.md | | PagerDuty MCP Server | D | 48.4 | 815 | observability.incidents, work.oncall | no | https://www.anchorterminal.com/tools/pagerduty-mcp.md | | Datadog MCP Server | C | 56.6 | 628 | observability.incidents | no | https://www.anchorterminal.com/tools/datadog-mcp.md | | Sentry MCP | BB | 70.2 | 160 | same category (Observability & incidents) | no | https://www.anchorterminal.com/tools/sentry-mcp.md | | Honeycomb MCP | C | 58.3 | 584 | same category (Observability & incidents) | no | https://www.anchorterminal.com/tools/honeycomb-mcp.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The API reference lists 284 operations on 162 paths in OpenAPI 3.0.3, with 82 smaller files by resource and version, plus files for webhooks, audit log events and deprecated endpoints (source: ) - A hosted MCP server at https://mcp.incident.io/mcp lists 91 tools, takes OAuth with PKCE or an API key, and is included in Team, Pro and Enterprise plans but not Basic (source: ) - The MCP tool `status_page_update` only drafts. The docs say a person publishes every status page update (source: ) - Deprecated `/v2/actions` and `/v2/follow_ups` endpoints carry a removal date of 31 December 2026 in their descriptions (source: ) - Section 2.10 of the terms of 1 August 2026 permits connecting agents and MCP clients through the APIs and makes the customer responsible for what they do (source: ) - The SLA commits to 99.9 per cent platform availability a month on Pro and Enterprise, and 99.99 per cent for notification triggering on Enterprise (source: ) - status.incident.io shows the API component at 100 per cent from July to October 2026, and the feed lists six incidents since 16 July (source: ) - #3 of 7 in Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md - All 15 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md ## Compare - [Datadog MCP Server vs incident.io API](https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.md): C 56.6 vs B 68.9 - [Grafana MCP Server vs incident.io API](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.md): BB 74.5 vs B 68.9 - [incident.io API vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp.md): B 68.9 vs D 48.4 - [incident.io API vs Rootly MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.md): B 68.9 vs C 59.7 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on incident.io or one of its subdomains, or the README of github.com/incident-io/sdk-ts. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "incident-io", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html incident.io API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![incident.io API on Anchor Terminal](https://www.anchorterminal.com/badges/incident-io.svg)](https://www.anchorterminal.com/tools/incident-io) ``` Plain link: ```html incident.io API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say incident.io API is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/incident-io-dark.png - Light: https://www.anchorterminal.com/assets/share/incident-io-light.png