01 · Naval fleet · space · Sandbox
Satellite
00 ·
Try Satellite in the sandbox.
100 free sealed actions · non-production receipts · no payment
Use a free ps_test_ key to integrate the API and evaluate the evidence path. Sandbox receipts use a non-production signer and are marked dev_key:true.
01 ·
Integration inputs.
What the API needs to identify the evidence action.
- Environment. Name the sandbox or evaluation environment represented by the action.
- Source key. Give the workflow or tool action a stable identifier.
- Proposed action. Send the action that needs a supervision decision and evidence record.
- Context. Include the vertical fields required by the selected API gate.
02 ·
Sandbox and production.
One tenant path; two clearly separated environments.
- Free sandbox. 100 sealed actions with a non-production key and signer.
- Production upgrade. Complete paid checkout with the same email; the key rotates and the tenant history remains.
- Metering. Credits equal gate rate multiplied by request size in estimated 1,000-token blocks, at 1¢ per credit and no more than $25 per action.
03 ·
Compliance controls to include.
The regulator's requirement row — pre-write the answer.
Select the controls and requirements that should land in this evidence record. Common picks:
NIST AI RMF · OMB M-25-21/22 · ISO/IEC 42001 · FIPS 140-3 · HIPAA · FERPA · FRE 702 · ABA Model Rules.
Full control set lives at register 09.
04 ·
Next step.
Create the sandbox key on the hosted signup page.