Is Firebender agent-ready? — Known-Good report

What we tested

Probed live on 23 Aug 2026 against rubric v1. 4 of 5 checks passed.

PROBE-VERIFIEDtier 2 of 3

✓Markdown negotiationAccept: text/markdown

✓Markdown twin at a predictable URL/page.md

✓llms.txt/llms.txt

—API catalogRFC 9727

✓MCP server answers/.well-known/mcp/server-card.json → tools/list

What its MCP server offers

We connected, ran tools/list, and recorded what came back on 23 Aug 2026. 3 tools, served from firebendercorp.main-kill-isr.mintlify.me — the standard set for sites on mintlify.

search_firebenderquery_docs_filesystem_firebendersubmit_feedback

What an agent could do here

Read from the page’s own content, with the wording each was drawn from. Inference is kept separate from tested facts — an agent completing the action is tier 3.

UNVERIFIED

read“Fetch the complete documentation index at: https://docs.firebender.com/llms.txt”

https://docs.firebender.com/llms.txt

download“Get Firebender for your JetBrains IDE”

https://plugins.jetbrains.com/plugin/25224-firebender

Context

15 sites in the index share the category software development documentation, of which 4 are transactional.

How we grade

Three tiers. Every listing shows which one it has reached, and when. The rubric.

tier 1

Declared

The site says agents are welcome in its robots.txt. A permission, not a capability.

✓

tier 2

Probe-verified

We fetched the site and tested each signal ourselves. Dated, repeatable, re-checked on a schedule.

this site · 23 Aug 2026

tier 3

Behaviourally verified

An agent completed the action end to end — booked, bought, submitted — and it worked.

coming

Own this site?

1 check did not pass when we last looked: API catalog. Each is a small, specific fix; the rubric says exactly what we look for.

Behavioural verification — an agent completing your booking, purchase or contact flow end to end, with the date published here — opens to a small founding cohort first. Leave an email to be in it.