Skip to main content

KILLBOT / DEVELOPER GUIDE

Research in your workflow.

Connect an assistant or an API client to your private stock and crypto research. The workspace, API and MCP share the same account, queue and limits.

Connect in four steps.

  1. Create an account and sign in with your email and password.
  2. Request analysis-access activation from the team. Registration and token creation do not activate a paid plan; checkout is not live.
  3. Open API & MCP, generate a named token and save it securely. Its full value is shown once.
  4. Configure your client with the HTTPS endpoint and Authorization header below. Use a separate token for each integration; revoke it from your account when finished.
{
  "mcpServers": {
    "killbot-research": {
      "url": "https://api.killbot.cash/research/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_RESEARCH_TOKEN"
      }
    }
  }
}

Client compatibility.

The server uses Streamable HTTP with a custom Authorization: Bearer … header. The JSON example is for clients that accept the mcpServers format with URL and headers. Follow your client’s configuration schema; it is not a universal import format.

Interactive OAuth discovery and one-click assistant installation are not available. A client that only accepts OAuth connectors cannot use this bearer configuration directly. The endpoint was exercised with an authenticated MCP protocol client; individual desktop-assistant integrations are not certified here.

Endpoint: https://api.killbot.cash/research/mcp

Always begin with research_capabilities to discover current coverage and access limitations.

Request your first report.

Analyse AAPL over one month. Present the thesis, counter-case, evidence, source dates, risks and missing information.
  1. Call create_analysis with asset_class: stock, symbol: AAPL, horizon: 1m, language: en, profile: standard and a unique idempotency_key.
  2. Save the returned analysis ID. The job may be queued or running; creation is not a completed report.
  3. Poll get_analysis conservatively, for example every five seconds, until completed, failed or cancelled. Honour rate-limit responses.
  4. Read the completed result, including source timestamps, evidence quality and limitations. It also appears in your client account.

Reuse the same idempotency key and payload after a transport failure. A new key can create a second billable analysis. Cancelling an analysis does not reverse costs already incurred.

Available tools.

research_capabilities
Discover supported symbols, profiles and current limits.
create_analysis
Create an analysis; consumes analysis quota and may incur research costs.
get_analysis
Read the status and result of one of your analyses.
list_analyses
List your recent private analyses.
cancel_analysis
Cancel a queued analysis or request cancellation of a running one.

Coverage and limits.

Current equities: AAPL, MSFT, NVDA, AMZN, GOOGL, META and TSLA. Current crypto: BTC, ETH, SOL and HYPE. Horizons: one or three months. Profiles: standard or technical. Languages: English or Russian. Query capabilities for the authoritative current list.

New accounts start without analysis entitlement. Activated pilot limits are assigned by the team and apply across all interfaces. Starter and Pro are draft plans, not purchasable subscriptions. Research ratings are model views, not calibrated return probabilities. Sources may be incomplete, and historical as-of analysis is not currently offered.

Research tokens do not place orders, access exchange accounts or grant trading permissions. Keep tokens out of URLs, screenshots and public repositories.

If a request fails.

  • 401: missing, expired or revoked credentials.
  • 403: analysis access may be awaiting activation.
  • 404: analysis not found or not owned by this account.
  • 409: idempotency key reused with a different request, or report not ready.
  • 429: rate, quota, queue or budget limit. Inspect the error code before retrying.
  • 5xx: temporary service failure. Retry status reads with backoff. For creation, preserve the original idempotency key.

MCP tool failures may be returned as tool-error content inside a successful HTTP response; inspect isError as well as transport status.