Rivalatch Terms of Use (operator draft)

1. Status

These terms are an operator-owned draft so the public Rivalatch listing can point at an HTTPS Terms URL. They are not legal advice and invent no warranty, SLA, or liability cap beyond the as-is language below. Operator: Contravious Battle / ConWan30.

2. The service

Rivalatch provides an agent-facing acceptance gate over HTTPS MCP: gate.run, gate.status, and gate.get_result. Docs vocabulary for outcomes includes Lodged, Recalled, Occupied, and Contested. It is not a public marketplace, not a billing product, and not crowning. Wire identifiers remain VibeGate.

3. Access and acceptable use

• Callers must keep their API key confidential and use X-Api-Key (or the configured VIBEGATE_API_KEY environment) only as authorized.
• Do not abuse the shared door: respect rate and occupancy behavior. A rival knock on the same idempotency key with a different payload may receive HTTP 409 Occupied / Contested — that is expected contract behavior, not a billing dispute.
• Do not attempt to circumvent auth, overload the host, or use the gate for unlawful activity.

4. As-is; no warranty

The service is provided as is and as available for MVP use. The operator makes no warranties of uninterrupted availability, fitness for a particular purpose, or non-infringement. Spec / OpenAPI / GateResult schemas change only via Spec diffs in the monorepo — not via this HTML.

5. Contact

See Support.