// PROTOCOL SURFACES
These paths are routed by Firebase Hosting to Cloud Functions (2nd Gen). They are thin HTTPS wrappers; authoritative verification and policy logic live in the protocol repositories and client libraries.
| Method | Path | Function | Purpose |
|---|---|---|---|
| GET | https://www.trigguardai.com/protocol/capabilities |
protocolCapabilities |
Deterministic capability manifest (machine-readable). |
| GET | https://www.trigguardai.com/protocol/status |
protocolStatus |
Protocol status snapshot. |
| GET | https://www.trigguardai.com/protocol/metadata |
protocolMetadata |
Engine / environment metadata. |
| GET | https://www.trigguardai.com/protocol/test-vectors |
protocolTestVectors |
Deterministic SDK conformance vectors (inputs + expected decisions). |
| GET | https://www.trigguardai.com/protocol/metrics |
protocolMetrics |
In-memory request/decision counters for this instance (resets on cold start). |
| POST | https://www.trigguardai.com/protocol/verify-receipt |
verifyReceipt |
Receipt payload schema validation for integration and conformance checks. |
| POST | https://www.trigguardai.com/protocol/verify-signature |
verifySignature |
Signature verification helper for protocol-level authenticity checks. |
// SITE / CONTACT
| Method | Path | Function | Purpose |
|---|---|---|---|
| POST | https://www.trigguardai.com/api/request-access |
requestAccess |
Request-access / lead flow (Resend). Not the core protocol API. |
Direct Cloud Functions URLs, In the Firebase console you will also see regional URLs
(e.g.
*.cloudfunctions.net or *.run.app) for the same exports. The paths above are the
canonical public entry points on trigguardai.com.