Weight rights
Read the exact checkpoint license, derivative conditions, commercial permissions and possible territorial restrictions.
AGENT USE CASE · SOURCE-FIRST
Open-weight checkpoints can make self-hosted agents possible, but a private system requires local inference, tools, retrieval, logs and secure operations. Model licensing and hardware feasibility must be checked per artifact.
Read the exact checkpoint license, derivative conditions, commercial permissions and possible territorial restrictions.
Start with total-parameter weight-only GB, then budget separately for KV cache, quantization artifacts, runtime overhead and concurrency.
Inspect outbound calls, telemetry, search indexes, image/audio processing, backups, observability and tool providers.
Use scoped credentials, sandboxed execution, approvals, auditing and patch management; on-prem hosting does not remove prompt-injection risk.
These model records are included by catalog modality or category, not by a verified task-success benchmark. Follow their primary sources before testing.
Map where prompts, retrieved documents, tool credentials, embeddings, logs and backups travel. Validate data residency and third-party services before claiming local-only processing. Apply prompt-injection defenses and scoped execution.
COMMON QUESTIONS
No. Self-hosting may improve data control but legal and technical obligations apply across the full processing system.
No. It is only a mathematical weight estimate unless that exact quantized artifact has been verified.
READ THE ORIGINALS
Neither an eligible model category nor an untested runtime implies demonstrated agent task success. For documented source claims, consult the capability evidence ledger and then apply deployment constraints in the selector.
Model metadata is source-linked; agent task success, tool-call reliability and production readiness require separate tests.
Review the methodology → Return to the explorer →