Terms of Service
Version: tos-2026-07-26
Product: Metrecept OpenAI-compatible gateway + optional public-web ingestion
Contact: partners@withohm.dev
By calling the API with terms_ack: true (or accepting these terms at tenant issue), you agree to this version.
1. Service
Metrecept provides: (a) LLM request routing and identical-request cache replay; (b) optional public-web context fetch under the Legal & compliance framework. Upstream model providers process prompts under their terms.
Service availability: Documentation and marketing are served on www.withohm.dev. The production API is https://api.withohm.dev. Supported client contracts also include localhost:8081 and operator-deployed edges. Mid-stream provider handoff is unsupported — see Streaming.
2. Accounts and keys
API keys identify a tenant. You are responsible for key custody. Suspended tenants receive HTTP 403.
Key prefix: Issued keys currently use the legacy prefix sk-at-…. The product brand is Metrecept; a sk-ohm- cutover is deferred and will be announced before rename.
3. Prohibited uses
You must not use the Service to:
- Access login-gated, credentialed, or private account systems
- Harvest leads, build person dossiers, or derive biometrics
- Conduct unsolicited direct marketing without a lawful basis (UK PECR and equivalents)
- Violate copyright, database rights, or site terms through bulk republication of fetched content (Copyright)
- Attempt to extract cache contents for model training or competing model development
- Violate applicable computer-misuse / unauthorized-access laws
4. Cache
Identical chat requests may be stored in Redis for the configured TTL solely for identical-request replay. Cache is not a training corpus. Use cache_control: "no_store" when prompts must not be written to cache. Response headers use the legacy family X-AT-* until a rename cutover.
5. Web ingestion
Requires web_purpose, web_compliance_ack, and (when enforced) terms_ack / dpa_ack. Fetched pages are excerpted and personal identifiers are redacted by default. Public pages only.
6. Customer content
You retain rights in prompts and outputs as between you and Metrecept, subject to upstream provider terms. You grant Metrecept a limited license to process content to provide the Service (routing, caching as configured, metering).
7. Subprocessors
8. Fees and ledgers
Metrecept invoices (Stripe) are separate from upstream provider pay-as-you-go costs. Usage meters and savings figures are estimates for identical-request cache effects, not guaranteed savings. Enterprise SKU availability does not imply a published uptime SLA until a separate SLA schedule is executed.
9. Disclaimer and liability
Service is provided as-available. Caps and exclusions for a specific deploying entity should be set with that entity’s counsel.
10. Acknowledgement
API field terms_ack: true and tenant terms_version at key issue bind this version (tos-2026-07-26).
Amendments (2026-08)
Additive under tos-2026-07-26 (existing acks remain valid):
- Operational metadata. Optional path labels (
X-Ohm-Path/ohm_path) and cost-center bindings are service-operation fields for hit-ratio inventory and FinOps attribution — not content for model training. - Spend caps. Org policy may soft-throttle or hard-refuse cache MISS upstream when monthly pipe-rent caps are exceeded. Cache HIT replay still serves. Caps are not prepaid credits; Metrecept invoice ≠ provider bill.
- Savings and receipts. Dual-ledger and public savings receipts remain estimates (
estimate_only). No guaranteed savings SLA; no semantic cache; provider invoice reconcile is not offered. - Copyright. Posture documented at /docs/copyright (
copyright-2026-08-07) — excerpt caps are controls, not a fair-use opinion.