Ruzzler Provider Terms

Provider participation

Upstream model providers supply execution capacity to the Ruzzler routing pool. Ruzzler keeps provider credentials server-managed and does not expose supplier terms, discounts, or route-selection logic to customers.

Capacity is admitted to the routing pool only after it passes the same verification pipeline customers see reported.
Provider identities and commercial terms are confidential; customer receipts show Ruzzler rate-card lines, not supplier pricing.
Providers may not inspect, retain, or train on tenant payloads beyond the fulfillment of the routed request.
Ruzzler may remove capacity from the pool at any time when verification, latency, or policy checks regress.

Creator and listing rules

Creators list tools and models on the Ruzzler marketplace. Listings are reviewed before publication, and anything not yet verified is labeled rather than implied.

Listing claims must be demonstrable through the public verification path; unverified listings show a pending state.
Demo or sample listings are explicitly labeled and never mixed into verified results.
Creators may not fabricate benchmarks, reviews, ratings, or usage counts.
Manipulated or misleading listings are removed, and repeat abuse ends marketplace participation.

Settlement and credits

Ruzzler Credits are prepaid and settle against verified execution. The tested pipeline behavior is reserve, settle, and release — including release on unverified abstention.

Credits are reserved when a request is accepted and settle only when the pipeline reports completion.
When Ruzzler abstains without verification, the reservation is released — zero charge is current tested behavior.
Every settled request is accounted against a rate-card-versioned receipt the customer can inspect.
Realized savings are estimates against a disclosed premium reference, not a guarantee.

Marketplace conduct

The marketplace connects customers, creators, and routed execution under one set of conduct rules, enforced through the same verification and review paths.

No unlawful, infringing, or abusive listings or usage.
No attempts to reverse-engineer routing, extract other tenants' data, or circumvent rate and spend limits.
Availability states are honest: a listing that cannot be served shows as unavailable, never as a silent failure.
Ruzzler may suspend listings or accounts pending review, with a written record of the decision.

Stage	Timing	What happens
Reservation	At request acceptance	Credits equal to the rate-card estimate are held against the tenant budget before execution begins.
Settlement	On verified completion	The reservation settles against actual metered usage, and a rate-card-versioned receipt is issued to the tenant.
Release	On unverified abstention	If the pipeline abstains without verification, the full reservation is released back to the tenant balance.
Provider payout	Weekly batch, net 7	Settled execution is aggregated weekly and paid to providers net 7 days, after the dispute window for the batch opens.
Dispute window	14 days from receipt	Tenants may dispute a receipt against its recorded verification status; unresolved disputes pause the related payout line.

Provider, creator, settlement, and marketplace rules.

One rulebook for the whole pool.

Provider participation

Creator and listing rules

Settlement and credits

Marketplace conduct

Reserve, settle, release.

Questions about supply or listings?