Inference marketplace

The inference pool where GPUs earn and builders save.

Providers register OpenAI-compatible capacity and earn per token. Developers get drop-in, quality-scored inference from $0.30–$1.80 / 1M tokens — no cloud contracts, no lock-in.

Active providers
Models online
$0.30
From / 1M tokens
bash — drop-in
$
pool router
routing live
Request
Route + score
Escrow
qwen2.5-coder-32b
EU-07·EU·93 trust
$0.74
llama-3.1-70b
US-12·US·89 trust
$0.92
deepseek-coder-v2
EU-03·EU·86 trust
$0.61
awaiting request…
$0.00Price floor / 1M tokens
0×Below cloud list price
0.0%Pool commission
0%OpenAI-compatible
How it works

Two products, one marketplace loop.

Providers supply capacity. Developers buy reliable, lower-cost inference. Policate manages trust, escrow, routing, and observability between both sides.

Supply side

Provider loop

Bring capacity, earn per token

  1. 1
    Connect capacity
    Ollama, vLLM, or any OpenAI-compatible /v1 endpoint.
  2. 2
    Set your terms
    Pick model, price floor, region, and concurrency.
  3. 3
    Serve traffic
    The pool routes, health-checks, and scores quality.
  4. 4
    Get paid
    Escrow, dispute windows, and Stripe payouts.
Read the provider guide
Demand side

Developer loop

Cheaper inference, drop-in API

  1. 1
    Add credits
    Stripe top-up with budget-safe metered usage.
  2. 2
    Point your client
    Drop-in OpenAI base URL and pool_live key.
  3. 3
    Route by quality
    Trust scores, retries, fallback, and health.
  4. 4
    Spend less
    Transparent token pricing, no cloud contracts.
Read the developer guide

Any OpenAI-compatible engine can join the pool

Ollama
vLLM
LM Studio
llama.cpp
TGI
LocalAI
LiteLLM
Any /v1 endpoint

Capacity-aware routing

Every request matched to the best provider by trust, price, latency, and region — with retries and fallback.

Trust & escrow

Continuous quality spot-checks and fraud detection. Credits held in escrow with dispute windows before payout.

Health & scoring

Live health checks and quality scoring keep slow or degraded providers out of the routing pool automatically.

Metered accounting

Transparent per-token pricing, budget-safe metering, and Stripe payout accounting for both sides of the market.

Drop-in

One base URL. Every OpenAI-compatible client.

Add credits, create a pool_live key, and point your client at the pool. Provider health, retries, fallback, and marketplace accounting stay behind the API.

  • No AWS account, no IAM, no cloud contracts
  • Capacity-aware routing with automatic fallback
  • Budget-safe metered billing via Stripe
bash
export OPENAI_BASE_URL="https://api.providers.policate.marcllort.com/v1"
export OPENAI_API_KEY="pool_live_xxxxx"

curl "$OPENAI_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen2.5-coder-32b",
    "messages": [{"role": "user", "content": "Refactor this function"}]
  }'
For providers

Turn idle GPU hours into revenue.

Register any OpenAI-compatible endpoint — Ollama, vLLM, TGI. Set a price floor, serve pool traffic, and get paid per token after quality checks clear escrow.

Estimated monthly earningsafter 16.7% commission
$0/ mo

1× A100 · qwen2.5-coder-32b · ~62% utilization · $0.74/1M floor

Tokens served
2.1B
Trust score
93
Payout cadence
daily
Why the pool

A marketplace, not a contract.

Transparent per-token pricing and quality-scored routing — versus opaque enterprise agreements, committed spend, and single-vendor lock-in.

Policate Pool
Marketplace inference
recommended
Pricing
Transparent $0.30–$1.80 / 1M tokens
Commitment
None — pay per token used
Routing
Quality-scored across providers
Onboarding
One base URL + a pool_live key
Reliability
Retries, fallback, health-aware
Idle cost
None — you never pay for idle
Cloud contracts
Enterprise agreements
Pricing
Opaque, negotiated per contract
Commitment
Annual committed spend / minimums
Routing
Single region, single vendor
Onboarding
Cloud account, IAM, procurement
Reliability
Best-effort within one provider
Idle cost
Reserved capacity billed 24/7
FAQ

Questions, answered.

How trust, routing, payouts, and pricing actually work on the pool.

Every provider gets a trust score from 0–100. The pool continuously replays known-answer prompts as quality spot-checks, grades the responses, and folds in uptime and p95 latency. Clean spot-checks and low latency raise the score; degraded providers lose routing priority. Trust reflects measured behavior, not vendor claims.

Get started

Start with the side of the market you need.

Register capacity as a provider, or use the pool as a developer with a standard OpenAI-compatible API key.