Community nodes: privacy and quality

Common Sapience brings together community-operated computing resources. We work to protect your data and maintain reliable service through privacy safeguards, node checks and ongoing quality monitoring.

Protecting your data

Common Sapience does not save request or response bodies or include them in logs. Your API key authenticates requests to the platform and is not sent to community nodes.

To generate a response, a node processes your request in plain text. Its operator can read the request and response on that machine. Platform data protection measures do not prevent this access within the node.

An authorized API proxy node forwards your request to its upstream provider, such as OpenAI. That provider processes the request and response under its own policies.

Managing node quality

Nodes must register and authenticate before connecting. We check local model weight hashes, verify response signatures and validate reported usage. API proxy nodes require administrator authorization.

We monitor success rates, latency and errors. The platform reduces traffic to or removes endpoints that fall below quality thresholds, and can block nodes for integrity violations.

What these checks establish

These controls help detect service problems and invalid node reports. They do not provide remote attestation: the platform cannot verify the exact model or quantization actually executed on a node. For API proxies, signatures identify the reporting node but do not independently verify the upstream model or token counts.

How requests are routed

Community nodes participate in routing by default for every account. Routing considers endpoint availability, quality and platform configuration. There is currently no account or API key setting to exclude them.