Hosting

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.

MetricThresholdConsequence
Health check failures3 consecutive failuresCircuit opens — traffic paused 30s
Health scoreBelow 0.5Reduced routing priority
Health scoreBelow 0.3Excluded from routing entirely
Error rate (30 min window)Above 20%Alert sent to admin + you
Consistency scoreBelow 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.

💡 Use 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

  1. Your /health endpoint returns HTTP 200
  2. Your /v1/chat/completions returns a valid OpenAI-format response
  3. Your model does not self-identify as GPT-4, Claude, Gemini, or any commercial model
  4. Your model produces a response fingerprint (checked for drift over time)

What is verified every 10 minutes

  1. Consistency probes — 5 factual questions with known correct answers (math, geography, history). Must pass ≥40%.
  2. Response shape validation — every response must have valid choices[0].message.content
  3. Identity fingerprint — we track the model's "personality" over time. Sudden changes flag for review.

Prohibited model practices

Blocked endpoint types

The following cannot be registered regardless of circumstances:

TypeExamplesReason
Commercial API providersapi.openai.com, api.anthropic.com, generativelanguage.googleapis.comToS violation, not your compute
NeuralGate gatewaysapi.computeshare.servequake.com, eu.computeshare.servequake.comSelf-dealing, credit fraud
Private/localhost IPs127.0.0.1, 192.168.x.x, 10.x.x.xNot publicly reachable
Commercial model IDsgpt-4, claude-*, gemini-*Cannot legally serve these

Enforcement tiers

Violations result in graduated enforcement based on severity and history:

StatusTraffic impactTrigger
⚠️ WarnedFull traffic, flagged for reviewFirst minor violation, policy reminder sent
⏸ Probation50% traffic weightRepeated minor violations or one moderate violation
🚫 SuspendedNo traffic, account frozenSerious violation or failure to respond to warnings
☠️ BannedPermanent, no appealCommercial 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:

ComponentWeightWhat affects it
Health score30%Uptime, health check pass rate. Updated every 60s.
Consistency score30%Known-answer probe accuracy. Updated every 10min.
Historical reliability20%30-day rolling error rate from metric rollups.
Latency score20%Average response time vs 5s baseline. Updated with each request.

All scores use exponential moving average (EMA) — recent performance matters more than old performance.

ScoreFormulaCheck intervalHalf-lifeFull 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 failuresHealth scoreEffect
10.80No change
30.51Reduced priority
50.33Excluded from routing (<0.3)
3 consecutive failures within 60sCircuit 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.

⚠️ Trust score below 30% → excluded from all routing. Below 80% → lower priority vs higher-trust hosters. Scores recover automatically as your server improves.

Acceptable use

Appeals

If you believe a moderation action was applied incorrectly:

Automated monitoring summary

All checks run automatically — no manual intervention needed to maintain good standing:

CheckFrequencyAutomatic action
Health check (GET /health)Every 60sUpdates health score (EMA)
Consistency probes (5 questions)Every 10minUpdates consistency score; deactivates if <40%
Response shape validationEvery requestMalformed responses → auto-flag + failover
Error rate checkEvery 10minEmail alert if >20% errors in 30min
5-min metric rollupEvery 5minWrites to audit log, updates 30-day reliability score
Identity fingerprintEvery 10minFlags significant drift for review