// Terms of service · DRAFT · 2026-05-20

Plain rules. Counsel-final. A working draft.

The operating contract for routing requests through api.slashed.pro. This page is published as a transparent working draft while counsel review is in progress.

DRAFT — not yet a binding agreement

This document describes our intended operating posture and currently-honoured commitments. It has not been reviewed by external legal counsel. Counsel-grade specifics — including governing law, jurisdiction, dispute-resolution mechanics, arbitration, limitation of liability, indemnification, and warranty — are intentionally not drafted here yet.

Material changes will be dated and reflected in the changelog at the foot of this page. If you need a counsel-grade contractual representation before that review concludes, write to hi@slashed.pro and a founder will respond directly.

Version 0.1-DRAFT Last updated 2026-05-20 Status pre-counsel
— 01 · Acceptable use

Build with it. Don't weaponise it.

SLASHED is an OpenAI-compatible gateway across eleven frontier models. The intended use is the obvious one: connect a client, route requests, build a product, pay for the tokens you actually use. The list below clarifies the boundary between fair use and behaviour that will get an account suspended.

// Enforcement: Account-suspension decisions are made by a founder, not a script. You will receive an email naming the rule, the observed behaviour, and the response window. Reinstatement is a conversation, not a ticket queue. Appeals to hi@slashed.pro.
— 02 · Service availability

Best effort. No formal SLA today.

SLASHED operates the gateway on a best-effort basis. There is no contractual uptime SLA at this time. Published status, incident handling, and observed historical uptime are all real — but none of them is yet a contractual commitment, and we are not yet ready to write a service-credit schedule against the platform.

Operating posture
Best effort, 24/7. A single-hop OpenAI-compatible gateway designed to add minimal overhead on top of provider-side availability. Operated by humans on call, not by a paging script.
Public status
Live at status.slashed.pro. Carries component health, incident history, and post-incident summaries. Subscribe via the status page for email or RSS alerts.
Incident response
A founder responds; not a queue. Material incidents (gateway-level outage, billing-system fault, security event) get a written summary within 5 business days of resolution.
Upstream dependencies
SLASHED depends on the named model providers (OpenAI / Anthropic / Google AI Studio) and the named edge / DNS sub-processor. Provider-side outages propagate to gateway availability. We do not subsidise upstream outages with credits at this time.
Self-hosted edition
For customers requiring formal SLA terms, the self-hosted edition operates inside your own VPC under your own SLA targets. See the self-hosted section on the landing page for commercial terms.
Pending counsel review

A contractual SLA — with target uptime percentile, measurement methodology, credit schedule, and exclusions — will be added in a later revision. Until then, SLASHED makes no SLA-equivalent representation by reference to status-page history or any other metric.

— 03 · Billing

Per-token usage. Published rate card. Reconciles to the line.

Billing reflects what you actually consumed, priced at the published per-token rate card. There is no hidden context tax, no router-authored preamble, no silent system prompt added to your token total. The dashboard mirrors the invoice line for line.

Pricing basis
Per-token consumption at the rates published at slashed.pro/#catalogue. Each model carries a single canonical ID and a single price per million tokens. No tier-splits at the same compute.
Token accounting
Invoiced tokens = prompt tokens you submitted + completion tokens we returned. Empty completions are treated as gateway failures rather than billable successes. SLASHED's current operating posture is not to append a platform-context preamble to your prompt for billing purposes; any change to that posture would be announced in advance.
Self-serve (card)
Monthly cycles. Card on file is charged at the close of each calendar-month billing cycle for the tokens consumed during that cycle. Receipts are made available in the dashboard once the cycle has been settled.
Procurement (invoice)
Annual or quarterly invoicing, NET-30. For finance teams that cannot expense card payments — a fixed annual or quarterly invoice priced against forecast volume, with quarterly reconciliation to actual usage. Contact hi@slashed.pro to set up.
Disputes
Itemised on the dashboard within the 30-day metadata retention window. If an invoice line does not reconcile to your client-side telemetry, email hi@slashed.pro with the affected window — a founder reviews; refunds against confirmed gateway errors are issued on the next cycle.
Provider rate changes
Upstream model prices can change. SLASHED rates change in step on the published cycle. The published rate card is the authoritative reference; we do not retroactively invoice past consumption at new rates.
Free-tier migration credit
Free 1,000,000 migration tokens per new account, applied automatically on first key issuance. Does not roll over. Used to validate the integration; not a substitute for paid usage.
— 04 · Termination

Either side. Without a ceremony.

Either party may end the relationship. The intended posture is symmetrical and uncomplicated: you can leave at any time from the dashboard; we reserve the right to suspend or terminate accounts that violate the acceptable-use list above. Statutory rights survive termination; final invoices are paid on the next cycle either way.

Customer-initiated
Self-serve from the dashboard. Account closure halts new key issuance and disables existing keys. Outstanding usage on the closing cycle is invoiced at the next billing run. Data deletion proceeds under the schedule in the privacy notice.
SLASHED-initiated · for cause
Immediate for acceptable-use violations (PII bulk extraction, targeted-harm content, credential-sharing schemes). You receive an email naming the rule, the observed behaviour, and the appeal channel. No ceremony.
SLASHED-initiated · no cause
If SLASHED winds down a service tier, exits a region, or otherwise removes capability you depend on, you receive 30 days written notice by email to the account address. Outstanding pre-paid balances are refunded pro-rata.
Effect on data
Customer prompts and completions are not retained (see privacy notice). Request metadata and billing records continue to age out under the published retention schedule. Account export is self-serve from the dashboard for 30 days after closure.
Pending counsel review

Specific notice periods, cure windows for material breach, survival clauses, and the precise mechanics of for-cause termination will be set out in counsel-reviewed contract text. Until then, the intended posture above is operative as good-faith working text only.

— 05 · Disclaimers

What the gateway is. What it isn't.

SLASHED operates as routing infrastructure on top of third-party model providers. Model outputs are produced by those providers. The gateway makes no representation about the truthfulness, fitness, or safety of any specific completion it returns to your client.

// Use-at-your-own-risk · model output

Model outputs are generated by upstream providers (OpenAI, Anthropic, Google) and are returned through SLASHED. The gateway may apply routing, error normalisation, and safety-related handling consistent with provider policy and the acceptable-use rules above; otherwise SLASHED does not edit completion content as a default behaviour. SLASHED makes no warranty that any specific completion is accurate, complete, current, safe, non-infringing, or fit for a particular purpose. You are responsible for evaluating fitness in your application context — especially in regulated, safety-critical, or human-impact use cases.

This includes — explicitly — medical, legal, financial, electoral, and child-safety contexts. The gateway is not a substitute for qualified professional judgement in any of these domains.

// No warranty · upstream providers

SLASHED does not control upstream provider behaviour. Model availability, response shape, content policy enforcement, deprecation schedule, and rate limits ultimately reflect provider decisions. SLASHED's commitment is to surface provider behaviour faithfully — including correct HTTP semantics, stable response schema, and the actual token count — not to override or reinterpret provider policy.

Outages, model retirements, or unilateral policy changes at the provider level may interrupt or alter service. SLASHED communicates these on the status page and, where material, by email to affected account addresses.

// No warranty · gateway

The SLASHED gateway is provided as-is, without warranty of any kind, express or implied, including (but not limited to) merchantability, fitness for a particular purpose, and non-infringement. We work hard to keep it well-behaved; we do not yet contractually guarantee that.

Pending counsel review

Limitation of liability, indemnification, exclusive-remedy language, statutory-warranty carve-outs (consumer-protection jurisdictions), and the specific text of warranty disclaimers above will be reviewed and refined by counsel. The intent of the above is to be plainly worded and honest about current commitment level; the binding text will be added in a later revision.

— 06 · Intentionally omitted, pending counsel

What this draft does not include.

The items listed below require qualified legal review before they appear in customer-facing terms. They are intentionally absent from this draft. SLASHED will not enforce, rely on, or otherwise treat as binding any reading of the missing items — they will only become part of the agreement after counsel review and a re-publication of this document.

Questions on the terms? A founder replies.

Email hi@slashed.pro for anything raised by a procurement review or a contract redline. Not a queue — a working founder. Acknowledged within 5 business days.

Read the privacy notice →