Terms of service

Last updated: 3 September 2026.

These terms govern use of the hosted NeuronPool coordinator operated by Danny Mota (the “service”): the OpenAI-compatible inference API, dashboard, host protocol, and related public pages. They are product rules that match the running code, not a counsel-signed master services agreement. Related: Privacy, Data retention.

By creating an account, calling the API, or running a host agent against this coordinator, you agree to these terms.

The service

Idle machines join a pool. Buyers send OpenAI-compatible chat (and related) requests. The coordinator assigns a host, seals the job, relays ciphertext, decrypts at the buyer edge, and settles the ledger.

Hosts keep 100% of successful public jobs at launch. The platform fee is PLATFORM_FEE_BPS (default 0). Failed jobs are not billed. Pool and self jobs are never billed and never scored.

The service is provided as-is. Capacity, latency, and which host serves a job vary with who is online. Public default trust is software, not operator-blind hardware isolation. See Privacy.

Accounts and keys

You must provide a valid email and keep credentials secret. API keys (sk-neuronpool-…) and host tokens (ht-neuronpool-…) are bearer secrets. You are responsible for traffic sent with your keys. New accounts may add at most $25 in credits during their first 7 days.

We may rate-limit, refuse, or disable keys that abuse the service.

Acceptable use

You may not use the service to:

• Break the law, or to generate or host content you are not allowed to process.
• Attack, scan, or overload systems you do not operate, including this coordinator and other hosts.
• Bypass metering, trust floors, sealing, attestation, or rate limits.
• Probe another tenant’s jobs, keys, or prompts.
• Train a model on traffic that is not yours, or retain another party’s prompts or completions except as needed to return the response to that party.
• Run unblessed or tampered agent builds on public traffic.

Buyers are responsible for the lawfulness of prompts their users send and for choosing a route (self / pool / public) that matches the confidentiality they need.

Host obligations

If you run neuronpool serve against this coordinator:

• For public traffic you must run a currently blessed release binary, keep keys local, answer the 5-minute challenge, and stay in probation until the coordinator marks you public-eligible. Dev / tsx builds stay at trust none and are excluded from public.
• You must not substitute listed weights, bias logits to cheat scoring, or strip logprobs on public completes. Confirmed substitution can forfeit held earnings and quarantine the host.
• You will see prompt plaintext in process at none and software (and edr). You must not log, retain, sell, or train on buyer prompts or completions from jobs that are not yours. We cannot cryptographically prevent a root user from reading memory; this clause is a condition of remaining listed and of receiving payouts.
• Pool and self jobs follow the same sealing path when the agent has a seal key. Legacy agents without a seal key are excluded from public.

Payouts

Host earnings for successful public jobs credit the host account after settlement. Earnings are held for 7 days before they become cashable. Cash-out requires Stripe Connect and a $10 minimum of released earnings. Weekly auto-payouts are opt-in.

We may freeze or forfeit held earnings for confirmed fraud, weight substitution, or acceptable-use breaches. Buyer credits never fund a host cash-out.

Pools

A social / friends pool is a trust relationship among members, not a NeuronPool subprocessor list. Members should assume the serving friend can read the job. Org tenant pools are the customer’s own machines; the customer is responsible for those operators.

No warranty

The service is experimental infrastructure. We do not warrant uninterrupted availability, bit-exact inference across backends, or confidentiality on the host. T102/T103 checks are statistical samples of public jobs, not a proof that every token was honest.

Changes and contact

We may update these terms by posting a new version on this page. Questions: security@neuronpool.dev. Governing-law and entity language is a counsel hand-off and is not stated here as a guess.