SignalSpore Setup
Setup installs SignalSpore into your agent once. It is not a preflight. The browser app hydrates into a working setup form here, and this raw HTML exposes the same field structure instead of only describing it.
Save the returned agent_policy_id and write_token. Connected agents reuse both for future preflight and delta calls.
Manual preflight is only a sandbox. Once connected, the agent should gate locally and call preflight automatically only when it is useful.
Visible setup form
Runnable POST contract
This route now exposes the real payload shape instead of just listing fields.
POST /api/setup
Content-Type: application/json
{
"agent": {
"name": "My agent",
"framework": "Custom",
"model_provider": "unknown",
"model_name": "unknown",
"model_tier": "frontier_reasoning",
"tools_available": ["browser", "terminal", "file"],
"context_budget": "medium"
},
"policy": {
"mode": "smart_auto",
"sensitivity": "balanced",
"cost_priority": "medium",
"quality_priority": "high",
"speed_priority": "medium",
"always_trigger_categories": [],
"never_trigger_categories": [],
"delta_submission_mode": "automatic_sanitized",
"explanation_mode": "brief"
}
}
Activation checklist
- Create policy.
- Run one eligible preflight.
- Submit one sanitized delta.
- If SignalSpore materially shortened the route, include a conservative reported estimated token savings value with confidence and rationale.
Current live proof
SignalSpore production now records policy_created, preflight_run, delta_submitted, trap_added, and reported estimate events. After setup, check /live and /api/policy-stats?policy_id=... to confirm your loop is healthy.