Chutes
Serverless inference platform for public model endpoints and user-created compute chutes.
Score calculation
(3 + 8 + 3 + 1 + 7) ÷ 5 = 4.4
5 of six dimensions rated. Unrated dimensions are excluded from the average.
Full scoring method ↗Setup details
Public system-user LLM API inference only; first-party apps and user-created/private chutes have separate data handling.
What fits your needs
Public model API use only; apps and private/user-created chutes require separate review.
Inference access
The platform offers public model inference and standard API requests with usage-based billing metadata.
See the evidence
Tradeoffs to expect
Different chute boundaries
User-created/private chutes can run third-party code and do not inherit the public system-model content guarantees.
See the evidence
How to switch
Select public model
Choose a system-user public model endpoint and configure API credentials; verify the model and pricing first.
See the evidence
Practical questions
Privacy scope
Confirm endpoint type, supported TEE/E2E options, usage logging, and payment metadata for your route.
See the evidence
For the Chutes public system-user LLM API inference; first-party apps and user-created/private Chutes are outside this assessment boundary, public documentation establishes the service or route but not its request-level physical footprint. The API exposes selectable models and request-generation parameters; these configure the workload, but no physical savings are measured. Electricity sourcing is not mapped to this route.
See the evidence
This practices/transparency assessment covers the Chutes public system-user LLM API inference; first-party apps and user-created/private Chutes are outside this assessment boundary. The sources establish how the service or endpoint is exposed and provide the request controls described in the demand component; they do not give a measured per-request energy, emissions or water value. The disclosure point reflects the stated operating boundary, not a product footprint, and company-wide electricity reporting is not attributed to this route.
1 + 1 reporting + 0 electricity + 1 controls = 3/10. This grades documented practices and transparency.
The reviewed sources don’t confirm request-level electricity, emissions or water; the actual serving facility and its power mix are also not mapped to Chutes public system-user LLM API inference; first-party apps and user-created/private Chutes are outside this assessment.
- Reporting1/3
- The reviewed documentation defines the Chutes public system-user LLM API inference; first-party apps and user-created/private Chutes are outside this assessment boundary. It gives an operating-scope description, not a dated quantitative energy, carbon or water report for this route.
- Electricity sourcing0/3
- No reviewed source maps Chutes public system-user LLM API inference; first-party apps and user-created/private Chutes are outside this assessment to a disclosed electricity mix or time-and-location-matched clean-power supply. The route's actual electricity use and emissions therefore remain unestablished.
- Resource controls1/3
- The API exposes selectable models and request-generation parameters; these configure the workload, but no physical savings are measured.
Water disclosure
Water reporting has not been assessed for this choice.
Chutes routes requests to many model families; prompt non-retention doesn’t settle training rights for selected model weights.
See the evidence
The provider documents how request content is handled in public inference, but its multi-model catalog does not have one training-data rights basis. Check the exact model release and license; API privacy is not training-data permission.
Exact model selection, release version, source inventory, permissions, post-training data, and creator-remedy scope remain unresolved.
Chutes says public system-model API prompts and responses are not persistently logged; request metadata remains, while first-party apps and user-created chutes have different guarantees.
See the evidence
The Chutes privacy policy carefully scopes its zero-content-retention statement to public LLM inference using system models. It describes transient in-memory processing, billing/operational metadata, and exceptions for applications or arbitrary third-party code, so the privacy grade does not apply to every chute.
No numerical score assigned because the reviewed evidence doesn’t confirm the route-specific controls needed for one.
Check that the target is a public system-user model endpoint, not a private or user-created chute; account, billing, support, and infrastructure metadata still exist.
Chutes hosts many models and offers inference APIs, but its service platform and request routing are hosted rather than user-operated locally.
See the evidence
Users can choose public model deployments through a hosted API and review individual model releases, but the Chutes inference service itself is not documented as a self-hostable runtime. Model licensing is separate from platform control.
The score reflects service-level inspectability and control, not usefulness or model quality.
Model availability, weight licenses, deployment controls, and exact serving configuration vary by model.
Company-level worker conditions and supply-chain safeguards are not assessed from product terms alone.
See the evidence
The reviewed product material describes access and features but doesn’t show labor conditions for the company’s model-development, data-labeling, moderation, or infrastructure workforce. This is an evidence boundary, not a claim about worker treatment.
1 + 0 + 0 + 0 = 1/10. Documented worker protections; missing disclosure is an evidence gap.
Current worker conditions, voice, grievance outcomes, contractor scope, and independent assurance were not established in these product sources.
- Pay & conditions0/3
- No qualifying worker-conditions disclosure was found in the reviewed product sources; this is a limited evidence gap.
- Worker voice & remedy0/3
- No worker-voice or grievance outcome evidence was found in the reviewed product sources.
- Evidence & follow-through0/3
- No independent worker-safeguard audit was found in the reviewed product sources.
No military or intelligence relationship is established by the reviewed product sources.
See the evidence
The official sources reviewed define product behavior and service terms but do not identify a military contract, deployment, or military-specific restriction for Chutes Global Corp.. This is “not established” within this source set, not evidence that no relationship exists.
7 base + 0 safeguard adjustment = 7/10 (0 of 9 safeguard points; every 3 adds 1). No military relationship was established in the cited sources. This ranks above known defense ties without claiming a verified clean record.
Undisclosed contracts, downstream hosting, customer deployment, end-use, and enforcement are outside the reviewed product sources.
- Use restrictions0/4
- No product-specific military-use restriction was identified in the reviewed materials.
- Enforcement & oversight0/3
- No military-specific enforcement or oversight mechanism was identified in the reviewed materials.
- Relationship disclosure0/2
- The product sources provide no military customer or deployment disclosure.
No company military relationship was established in the reviewed product sources; the source set is not a customer-complete investigation.
Military rubric ↗Chutes Global Corp. was not named in the BNC consumer-target guide or its No Tech target list when. This status covers those named lists only.
See the evidence
I checked the BNC consumer-boycott and pressure guide and the No Tech target list for Chutes Global Corp.. The company was not named in either list on 2026-10-24; this does not assess unrelated suppliers, customers, investors, or every BNC publication.
The result is limited to the two linked BNC target lists as; additions or other BNC publications may change the assessment.