AI agents

End-to-end deploy from one prompt (generate → train → deploy), streaming

post/api/v1/one_shot

Request

  • Base URL: https://api.quantifyme.ai
  • URL: https://api.quantifyme.ai/api/v1/one_shot
  • Auth: API key in header X-API-Key

Request body

api_keystring

Your API key, if you cannot set the X-API-Key header. Agents that mint a key at runtime (e.g. a ChatGPT Action calling POST /api/v1/key/trial) should pass the returned api_key here on every subsequent call. The X-API-Key header wins when both are present.

community_idinteger

Deploy an existing community strategy by id instead of generating. See GET /api/v1/community.json.

deliver_toobject

Channels to wire on deploy. Keys: webhook (bool|url), telegram (chat_id).

entry_tokenstring

Your integration's entry token. ALWAYS send this if you have one, even when you also send api_key. It is what lets this call succeed when the key is not ready yet - agents that issue tool calls in parallel can reach this endpoint before their own createTrialKey call has returned. With a valid entry_token the deploy proceeds under a fresh anonymous identity instead of failing with 401.

presetstring

Deploy a curated template instead of generating. See GET /api/v1/presets.

promptstring required
symbolstring

FX pair or BTCUSD. Defaults to EURUSD.

timeframe'1min' | '5min' | '15min' | '1h'

Example request

{
  "aux_feeds": [
    {
      "symbol": "USDCHF",
      "timeframe": "15min"
    }
  ],
  "deliver_to": {
    "webhook": true
  },
  "prompt": "Buy when RSI hits 30, sell when RSI hits 70",
  "symbol": "EURUSD",
  "timeframe": "15min"
}

Response

SSE stream of token/step/done/error events. Terminal event: done carries {live_url, model, stem, channels}. Requires a client that can hold an open text/event-stream for ~1-2 minutes. Callers that cannot consume SSE (ChatGPT Actions, most HTTP tool-callers) must use POST /api/v1/one_shot/start + GET /api/v1/one_shot/status instead. — Server-Sent Events stream. Each message is event: <type>\ndata: <json>\n\n.

Changes

No recorded changes to this operation across all 1 revision of this API.