LLM Gateway Terms of Service

Scope

These terms govern access to the LiquidPad LLM Gateway, an OpenAI-compatible inference proxy reachable at api.liquidpad.site/v1. The Gateway forwards chat completion requests to upstream model providers using operator-held credentials. Access is gated by a LiquidPad API key issued by @liquidpadbot on Telegram and bound to a wallet on Base.

Acceptable Use

You may use the Gateway to power applications, agents, and interactive tools that you own or operate. You may not use the Gateway to generate content in any of the following categories:

Child sexual abuse material.
Synthesis or weaponization instructions for chemical, biological, radiological, or nuclear materials.
Targeted violence, threats, or planning of attacks.
Malware, spyware, ransomware, or credential stealers.
Doxxing or exposing private information of individuals.
Live financial fraud, including phishing pages, impersonation of financial institutions, or fake government notices.

Requests in these categories are blocked before reaching upstream providers and recorded in the abuse audit. Repeated violations suspend the API key.

Tier Allocation

Token quotas, rate limits, and model access scale with your $LPAD tier on Base. Tiers are evaluated live on each request, with a 24-hour fallback if the live read is unavailable. A small anonymous trial is available at Tier 0; full access requires holding $LPAD.

Audit and Retention

Each request emits an audit record containing timestamp, hashed API key, wallet, tier, model, provider, token counts, request hash, latency, status code, and abuse-filter verdict. Audit records do not contain plaintext prompts, completions, system prompts, or tool arguments. Records are retained for 90 days and deleted on a daily sweep.

Suspension Grounds

The Gateway suspends an API key when it triggers five or more abuse-filter blocks within one hour, when an operator review identifies misuse, or when the bound wallet is associated with activity inconsistent with these terms. Suspension blocks new requests but does not delete existing audit records.

Caller Responsibility

You are responsible for the prompts and completions produced under your API key, for compliance with applicable law in your jurisdiction, and for your end users. You must not pass through third-party content that you do not have rights to submit.

Provider Compliance

The Gateway only routes traffic to upstream providers whose Terms of Service permit re-exposure of inference. The current upstream provider list is reviewed on a recurring basis and is available on request.

Changes

We may update these terms. When the version bumps, existing API keys must re-acknowledge the new version on Telegram before the next chat completion request. The current version is shown above and surfaced in the ToS-Url response header.

Contact

Questions, abuse reports, and review requests: hello@liquidpad.site or DM @_proxystudio on X.