neutron AI
Changelog

Testing

Use a sandbox tenant and test token to validate your Neutron AI integration before enabling it for production users.

API Smoke Test

curl -s "$NEUTRON_API_URL/v1/memory/remember" \
  -H "Authorization: Bearer $NEUTRON_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d @- <<EOF
{
    "tenantId": "$NEUTRON_TENANT_ID",
    "scopeId": "$NEUTRON_SCOPE_ID",
    "type": "preference",
    "text": "Prefers concise integration examples"
}
EOF

Then verify recall:

curl -s "$NEUTRON_API_URL/v1/memory/recall" \
  -H "Authorization: Bearer $NEUTRON_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d @- <<EOF
{
    "tenantId": "$NEUTRON_TENANT_ID",
    "scopeId": "$NEUTRON_SCOPE_ID",
    "query": "integration examples"
}
EOF

SDK Smoke Test

Test these flows in your preferred SDK:

  • health check
  • remember
  • recall
  • agent context
  • reflect
  • forget
  • error handling for invalid token
  • error handling for unauthorized scope

CLI Smoke Test

neutron health
neutron memory remember --scope $NEUTRON_SCOPE_ID --type preference --text "Prefers short examples"
neutron memory recall --scope $NEUTRON_SCOPE_ID --query "short examples"
neutron context create --scope $NEUTRON_SCOPE_ID --agent agent_docs --task "Write onboarding copy"

MCP Smoke Test

Validate that your host can:

  • connect to the Neutron MCP endpoint
  • list allowed tools
  • call memory_agent_context
  • call memory_recall
  • reject write tools when the token is read-only

Production Readiness

Before launch, confirm:

  • tokens are server-side only
  • tenant and scope IDs are authorized by your app
  • logs do not contain raw memory content by default
  • delete controls call forget
  • repeated tasks use an intentional cache policy
  • SDK and CLI versions are pinned in your release workflow

Release notes