supercomputer
Hosted keys and Supercomputer
Use hosted keys for permissioned Supercomputer calls and keep local-first work separate.
Hosted Supercomputer keys are for permissioned hosted execution. They are not required for ordinary local-first use on the Computer.
Key types
Separate identity from hosted compute. A developer identity key can support attribution and local integration. A hosted Supercomputer key controls paid hosted power.
Hosted request
Hosted calls should include an execution policy, privacy tier, project id, and maximum Joules where applicable.
curl https://tarx.com/api/v1/chat/completions \
-H "Authorization: Bearer $TARX_API_KEY" \
-H "x-tarx-execution-policy: supercomputer-fast" \
-H "x-tarx-project-id: launch-app" \
-H "x-tarx-max-joules: 50000"Boundary
A hosted key should not make local-private data available to hosted compute unless the request and policy explicitly allow that route.