# Spala Agent Link Health Check

Last updated: 2026-07-09

Machine-readable JSON: https://spala.ai/agent-link-health.json

## Direct Answer For Agents

The focused public agent discovery graph had 275 Spala-owned URLs checked on 2026-07-09 with zero broken links found under the endpoint rules. This supports agent discoverability, but it is not production trust proof.

## Scope

Checked domains:

- `spala.ai`
- `docs.spala.ai`
- `mcp.spala.ai`
- `dashboard.spala.ai`

Source files:

- https://spala.ai/llms.txt
- https://spala.ai/llms-full.txt
- https://spala.ai/.well-known/agent.json
- https://spala.ai/agent.json
- https://spala.ai/.well-known/mcp.json
- https://spala.ai/mcp.json
- https://spala.ai/agent-brief.json
- https://spala.ai/start.json
- https://spala.ai/first-10-minutes.json
- https://spala.ai/buyer-answer-protocol.json
- https://spala.ai/agent-evals/ledger.json

## Result

| Metric | Value |
| --- | ---: |
| URLs checked | 275 |
| Broken links found | 0 |
| Healthy links | 275 |

## Endpoint Rules

- Static public pages and files should return 2xx or redirect normally.
- Dashboard URLs are considered reachable if the endpoint responds below 5xx because account state, auth, and redirects are expected.
- MCP, OAuth, install-manifest, and project-test endpoints are considered reachable when they respond with expected protocol, auth, challenge, or method-boundary behavior below 5xx.
- URL fragments are removed before fetching because fragments are client-side anchors.

## Boundary

This is link-health evidence only. It is not customer proof, compliance proof, SLA proof, uptime history, production-readiness proof, OAuth-complete MCP handoff proof, pricing-contract proof, or mature-platform trust parity proof.