Pre Trade Check
Ask n0brains First — graded pre-trade CONDITIONS ASSESSMENT for a proposed trade. Body: {asset, side (long/short), entry?, stop?, target?, leverage?, horizon_hours? (default 24)}. Returns grade A..F, flags (crowding, event risk inside horizon, liquidation-distance vs realized vol, stop-vs-noise, proven-edge conflicts, TA extension), supporting factors, and falsifiers to watch. Every check is logged and resolved at its horizon; cross-grade performance stays withheld until the weekly truth gate clears. Free tier: FREE_CHECKS_PER_DAY checks/day; Pro unlimited (within rate limits). Analytical, not advice.
Request
- Base URL: https://api.n0brains.com (the document declares no server; this is the origin it was published from)
- URL: https://api.n0brains.com/check
- Auth: none declared
Headers
Printable, at most 128 characters.
Client-minted, one key per user-initiated submission. The same (user, key) always maps to ONE engine run: a completed key replays its original response verbatim — byte-identical to the first, with no replay marker of any kind, so a retry transparently succeeds and never needs recovering from /checks/history. Replay is served even once the daily quota is exhausted, because the original submission already paid for it. Sameness is judged over asset, side, entry, stop, target, leverage and horizon_hours only. Replay TTL 24h; an in-flight key is held under a 120s lease. Omitting the header is fully supported and behaves exactly as before.
Request body
Response
Graded assessment (typed; additive-only — ignore unknown fields). A replay of an earlier submission under the same key is byte-identical to the original response and carries no replay marker.
Changes
No recorded changes to this operation across all 1 revision of this API.