generated: '2026-08-29' method: probed source: live GET probes of /.well-known/* on every Splio host in apis.yml and OpenAPI servers[] note: >- One real document was served: an RFC 9727 API catalog linkset at https://dev-scp.splio.com/.well-known/api-catalog, published by the ReadMe-hosted developer hub and enumerating all six of Splio's OpenAPI definitions with service-desc + service-doc links. Saved verbatim as splio-api-catalog.json. Everything else missed. splio.com answers 403 to every /.well-known/* path (edge policy, not a document). developer.splio.com is a single-page-app catch-all that answers 200 with the same 1,053-byte HTML shell for every path, so its 200s are recorded here as misses, not documents. No security.txt is served anywhere on the estate. hosts: - host: dev-scp.splio.com documents: - path: /.well-known/api-catalog status: 200 content_type: application/linkset+json file: splio-api-catalog.json - path: /.well-known/security.txt status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/oauth-authorization-server status: 404 - path: /.well-known/oauth-protected-resource status: 404 - path: /.well-known/ai-plugin.json status: 404 - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - host: api.splio.com documents: - path: /.well-known/security.txt status: 404 - path: /.well-known/openid-configuration status: 404 - path: /.well-known/oauth-authorization-server status: 404 - path: /.well-known/oauth-protected-resource status: 404 - path: /.well-known/api-catalog status: 404 - path: /.well-known/ai-plugin.json status: 404 - path: /.well-known/agent-card.json status: 404 - path: /.well-known/agent.json status: 404 - host: splio.com documents: - path: /.well-known/security.txt status: 403 - path: /.well-known/openid-configuration status: 403 - path: /.well-known/oauth-authorization-server status: 403 - path: /.well-known/oauth-protected-resource status: 403 - path: /.well-known/api-catalog status: 403 - path: /.well-known/ai-plugin.json status: 403 - path: /.well-known/agent-card.json status: 403 - path: /.well-known/agent.json status: 403 - host: developer.splio.com documents: - path: /.well-known/security.txt status: 404 - path: /.well-known/openid-configuration status: 200 note: SPA catch-all HTML shell, not a document — treated as a miss. - path: /.well-known/oauth-authorization-server status: 200 note: SPA catch-all HTML shell, not a document — treated as a miss. - path: /.well-known/oauth-protected-resource status: 200 note: SPA catch-all HTML shell, not a document — treated as a miss. - path: /.well-known/api-catalog status: 200 note: SPA catch-all HTML shell, not a document — treated as a miss. - path: /.well-known/ai-plugin.json status: 200 note: SPA catch-all HTML shell, not a document — treated as a miss. - path: /.well-known/agent-card.json status: 200 note: SPA catch-all HTML shell, not a document — treated as a miss. - path: /.well-known/agent.json status: 200 note: SPA catch-all HTML shell, not a document — treated as a miss. other_agent_surfaces: - path: /llms.txt host: dev-scp.splio.com status: 200 file: ../llms/splio-llms.txt note: Real documentation index, 253 lines, guides + full API reference + recipes. - path: /llms.txt host: splio.com status: 200 note: >- A second, separate llms.txt generated by the WordPress marketing site (60KB, mostly French marketing pages). Not saved — the docs-host llms.txt is the API-relevant one. - path: /llms.txt host: api.splio.com status: 404