Octagon API Smoke Test
Use this skill to confirm that the Claude plugin and hosted Octagon connector are configured correctly.
Run this smoke test only against the plugin-managed server octagon-claude-plugin.
If another Octagon server such as octagon-local is available in the client, do not use it as a substitute for the plugin connector. Report the plugin as unhealthy until the plugin server itself is working.
Smoke test sequence
- Check whether Octagon tools for server
octagon-claude-pluginare visible - Run a simple
octagon-agentrequest - Run a simple
octagon-deep-research-agentrequest - If a Kalshi URL is available, run
octagon-prediction-markets-agent - If an event ticker is available, run
prediction_markets_history
MCP calls
General agent:
{
"server": "octagon-claude-plugin",
"toolName": "octagon-agent",
"arguments": {
"prompt": "Give me a one-sentence summary of Apple's latest quarter."
}
}
Deep research:
{
"server": "octagon-claude-plugin",
"toolName": "octagon-deep-research-agent",
"arguments": {
"prompt": "Research the current AI infrastructure spending cycle in one short paragraph."
}
}
Status matrix
Classify failures before suggesting next steps:
- No Octagon tools are visible at all: the Octagon connector is not connected in Claude yet
- Auth flow is requested or connector auth appears missing: route the user to
octagon-setup - 401 or 403 style failures after tools appear: the connector exists but needs reconnect
- Credit, entitlement, or plan restriction failures: report the exact error and stop
- Network, timeout, or service failures: classify as service-side or connectivity issues
- Successful text response from at least one tool: the connector is healthy enough to use
Failure triage
- No tools visible: open Plugins -> Octagon -> Connectors, connect Octagon AI, then rerun the smoke test
- Auth or reconnect needed: use
octagon-setup - Prediction market failures mentioning Kalshi URL: supply a valid Kalshi market URL
- Credit or entitlement failures: report the exact error and stop
- Advanced/manual API-key fallback questions: explain that API-key mode is no longer the default plugin path and should only be used for standalone or local runtime workflows
Success criteria
- At least one Octagon tool returns usable text
- Tool failures, if any, are classified clearly as connection, auth, entitlement, input, or service issues