Public API discovery
WITNESS is a machine layer, not only a website.
The public discovery surface exposes service metadata, interoperable agent/tool entry points, and governed public Record verification without exposing private workspace data or collapsing transport into truth authority.
OpenAPI
OpenAPI 3.1 discovery document
The OpenAPI document intentionally covers public discovery and interoperability surfaces: health, public configuration, capabilities, MCP discovery and transport, A2A discovery and message transport, and public Record retrieval/verification.
Public service metadata
| Health | GET https://chat.witnessstandard.com/v1/health |
| Public config | GET https://chat.witnessstandard.com/v1/config |
| Capabilities | GET https://chat.witnessstandard.com/v1/capabilities |
MCP
| Discovery | GET https://chat.witnessstandard.com/.well-known/mcp.json |
| Transport | POST https://chat.witnessstandard.com/mcp |
Private MCP interactions require an authenticated WITNESS bearer token. Discovery metadata remains public so compatible clients can identify the service before authentication.
A2A v1
| Agent Card | GET https://chat.witnessstandard.com/.well-known/agent-card.json |
| Evidence extension | GET https://chat.witnessstandard.com/a2a/extensions/witness-evidence/v1 |
| HTTP+JSON transport | POST https://chat.witnessstandard.com/a2a/v1/message:send |
| JSON-RPC transport | POST https://chat.witnessstandard.com/a2a |
The Agent Card advertises WITNESS Standard as the provider, the evidence-backed capability skills, supported transport bindings, and authentication requirements. A2A carries evidence and claims; it does not establish truth.
Public Records
| Record artifact | GET /records/{recordId} |
| Verification | GET /v1/records/{recordId}/verification |
Public Records are governed commitments, not accidental projections of private workspace evidence. Record verification allows a public artifact to preserve a checkable canonical relationship to its governed state.
Other machine sources