Hoster Policy
Rules, requirements, and enforcement. Read this before registering. Violations can result in reduced traffic, probation, or permanent ban.
TL;DR: Run a real model on real hardware. Keep it up. Don't lie about what you're serving. Don't route traffic through someone else's API. Everything is verified automatically every 10 minutes.
Availability requirements
Your server must maintain consistent uptime to stay in the routing pool.
| Metric | Threshold | Consequence |
|---|---|---|
| Health check failures | 3 consecutive failures | Circuit opens — traffic paused 30s |
| Health score | Below 0.5 | Reduced routing priority |
| Health score | Below 0.3 | Excluded from routing entirely |
| Error rate (30 min window) | Above 20% | Alert sent to admin + you |
| Consistency score | Below 40% | Auto-deactivated immediately |
Scores recover automatically when your server performs well again. Health score uses exponential moving average — one bad period won't destroy your score permanently.
drain mode before planned maintenance: POST /hosters/drain {"drain": true}. This stops traffic without penalizing your circuit breaker or health score.Model authenticity rules
You must serve exactly what you claim to serve. Violations are detected automatically and result in immediate suspension.
What is verified at registration
- Your
/healthendpoint returns HTTP 200 - Your
/v1/chat/completionsreturns a valid OpenAI-format response - Your model does not self-identify as GPT-4, Claude, Gemini, or any commercial model
- Your model produces a response fingerprint (checked for drift over time)
What is verified every 10 minutes
- Consistency probes — 5 factual questions with known correct answers (math, geography, history). Must pass ≥40%.
- Response shape validation — every response must have valid
choices[0].message.content - Identity fingerprint — we track the model's "personality" over time. Sudden changes flag for review.
Prohibited model practices
- Proxying commercial APIs — registering an endpoint that forwards to OpenAI, Anthropic, Google, etc. Instant permanent ban.
- Misrepresenting model size/quality — claiming to serve Llama 3 70B while running a 7B model. Detected via latency profiling and output quality.
- Returning cached/static responses — serving the same response regardless of input. Detected by consistency probes.
- Running a broken model — a model that produces garbled, empty, or nonsensical outputs consistently. Auto-deactivated.
- Rate limiting NeuralGate traffic — throttling the gateway's requests while serving direct customers faster.
Blocked endpoint types
The following cannot be registered regardless of circumstances:
| Type | Examples | Reason |
|---|---|---|
| Commercial API providers | api.openai.com, api.anthropic.com, generativelanguage.googleapis.com | ToS violation, not your compute |
| NeuralGate gateways | api.computeshare.servequake.com, eu.computeshare.servequake.com | Self-dealing, credit fraud |
| Private/localhost IPs | 127.0.0.1, 192.168.x.x, 10.x.x.x | Not publicly reachable |
| Commercial model IDs | gpt-4, claude-*, gemini-* | Cannot legally serve these |
Enforcement tiers
Violations result in graduated enforcement based on severity and history:
| Status | Traffic impact | Trigger |
|---|---|---|
| ⚠️ Warned | Full traffic, flagged for review | First minor violation, policy reminder sent |
| ⏸ Probation | 50% traffic weight | Repeated minor violations or one moderate violation |
| 🚫 Suspended | No traffic, account frozen | Serious violation or failure to respond to warnings |
| ☠️ Banned | Permanent, no appeal | Commercial API proxying, credit fraud, repeated suspension |
Pending earnings are held during suspension. They are released if reinstated, forfeited if banned.
Trust score explained
Your trust score (0–100%) determines your share of traffic. It's a composite of:
| Component | Weight | What affects it |
|---|---|---|
| Health score | 30% | Uptime, health check pass rate. Updated every 60s. |
| Consistency score | 30% | Known-answer probe accuracy. Updated every 10min. |
| Historical reliability | 20% | 30-day rolling error rate from metric rollups. |
| Latency score | 20% | Average response time vs 5s baseline. Updated with each request. |
All scores use exponential moving average (EMA) — recent performance matters more than old performance.
| Score | Formula | Check interval | Half-life | Full recovery time |
|---|---|---|---|---|
| Health | new = old × 0.8 + result × 0.2 |
60s | ~5 minutes | ~10 consecutive successes (~10 min) |
| Consistency | new = old × 0.7 + probe × 0.3 |
10 min | ~20 minutes | ~8 consecutive passes (~80 min) |
Example — health score after failures (starting from 1.0):
| Consecutive failures | Health score | Effect |
|---|---|---|
| 1 | 0.80 | No change |
| 3 | 0.51 | Reduced priority |
| 5 | 0.33 | Excluded from routing (<0.3) |
| 3 consecutive failures within 60s | — | Circuit opens (30s pause, regardless of score) |
After the circuit closes and your server passes the probe, the EMA resumes from where it left off. A bad 10-minute window takes about the same time to recover from. Events older than ~25 minutes have less than 10% influence on the current score.
Acceptable use
- ✅ Open-weight models (Llama, Mistral, Gemma, Qwen, Falcon, etc.)
- ✅ Fine-tuned versions of open-weight models (must disclose in model alias)
- ✅ Quantized models (GGUF, AWQ, GPTQ) — just list the actual base model
- ✅ Multiple models on one server — register each separately
- ✅ Models you trained yourself on your own data
- ❌ Commercial models (GPT, Claude, Gemini, Command, etc.)
- ❌ Models with non-commercial licenses used commercially without permission
- ❌ CSAM, illegal content, or models fine-tuned to produce it
Appeals
If you believe a moderation action was applied incorrectly:
- Email abuse@computeshare.servequake.com with your hoster ID and the reason
- Include evidence: server logs, model card, hardware specs
- We respond within 48 hours
- Permanent bans for commercial API proxying are not appealable
Automated monitoring summary
All checks run automatically — no manual intervention needed to maintain good standing:
| Check | Frequency | Automatic action |
|---|---|---|
Health check (GET /health) | Every 60s | Updates health score (EMA) |
| Consistency probes (5 questions) | Every 10min | Updates consistency score; deactivates if <40% |
| Response shape validation | Every request | Malformed responses → auto-flag + failover |
| Error rate check | Every 10min | Email alert if >20% errors in 30min |
| 5-min metric rollup | Every 5min | Writes to audit log, updates 30-day reliability score |
| Identity fingerprint | Every 10min | Flags significant drift for review |