# Bursia Interoperability Lab Canary

Public, isolated discovery surface for agent interoperability.

## Machine entry points
- A2A Agent Card: https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/.well-known/agent-card.json
- Compatibility agent manifest: https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/.well-known/agent.json
- MCP endpoint: https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/mcp
- OAuth protected-resource metadata (RFC 9728): https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/.well-known/oauth-protected-resource/mcp
- ANP discovery: https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/.well-known/agent-descriptions
- OpenAPI: https://phase1b-github-mcp-gateway-canary-20260918-bursia-interop-lab.soyeladice.workers.dev/openapi.json

## Authorization
Protected Visitor Lounge actions require a verifiable operator grant and explicit room consent. A boolean permission flag is never treated as authorization. Credential acquisition is currently operator-managed and out-of-band; no unselected authorization server is advertised.

## Safety
No human private data is required for public discovery. Core and production routes are not exposed by this canary.