NeuroAPI

Changelog

Dated NeuroAPI releases, newest first, with breaking changes, new limits, and billing behavior in the public API.

Current build

  • API version: v1
  • Build: 0.1.19

The same values come back in the X-API-Version and X-Build headers on every API response.

v0.1.19

2026-11-16

  • No API changes - this build only changes how NeuroAPI is operated. Requests, responses, limits and billing behave exactly as in v0.1.18.

v0.1.18

2026-11-14

  • Live token data in more answers - token metrics, technical analysis, trending coins and pools, new and recently added coins, top holders, smart-money flows, buy and sell pressure and token risk checks were unavailable to POST /agent/ask and the MCP ask tool. The agent now uses them in every mode.
  • Coded errors instead of 500 - a non-streaming POST /agent/ask that hits its step limit before it produces your output_schema now returns 422 agent_budget_exceeded, and unusable model output returns 502 agent_model_error. Neither is billed. Errors says when to retry each.
  • Long runs finish with an answer - a POST /agent/ask run close to its step limit now wraps up with the data it already gathered instead of ending in an error.
  • No more false 429 too_many_concurrent_runs - a run stopped part-way, for example during a deploy, could keep counting against your concurrent-run limit. A stopped run now frees its slot within 3 minutes.

v0.1.17

2026-11-12

  • No more intermittent 500 on POST /agent/ask - some calls, mostly smart and max runs that drew extra quota, could return 500 after the answer had already been produced. These calls now return the answer as normal.
  • X-Quota-Remaining is always a whole number - the header now always reports the number of requests left in your quota.
  • You were not billed for the failed calls - every call that hit this 500 was refunded to your quota, so no action is needed on your side.

v0.1.16

2026-11-10

  • Retry the right 429 - Rate limits shows how to tell rate_limited, which clears after Retry-After, from quota_exceeded, which clears at X-Quota-Reset. The retry samples no longer retry a spent quota.
  • Accurate error reference - a malformed request body returns 422, and Errors now says so. It also covers the plain-text 413, the 504 agent_timeout, and which statuses are safe to retry.
  • Failed streams are documented - a stream that fails ends with an error event and no [DONE], and the call isn't billed.
  • Sample timeouts match the server - the code samples now wait 300 seconds, the limit for a non-streaming run, so they no longer give up on answers that are still running.
  • Concurrent runs on Pricing - Pricing now lists how many runs each plan can have at once: Starter 2, Pro 5, Enterprise 10.
  • Clearer API reference - every error response says what to do next, and mode lists its cost and the plans that include it. MCP clients see the same mode details.
  • Fixed code samples - two broken samples now run as written.

v0.1.15

2026-11-03

  • Compare, MCP, and Agents - new public pages compare NeuroAPI with market data and AI search APIs, explain how to connect MCP clients, and describe what the agent can do. All three are linked from the site footer.
  • MCP rate limits - MCP requests follow the same rate-limit and auth rules as the HTTP API. See Rate limits.
  • Pricing on mobile - all plans can be compared on small screens.
  • Security disclosures - report vulnerabilities to [email protected] as described on the Security page.
  • Docs navigation - missing pages show a not-found state.
  • API key creation dialog - Escape dismisses the copy hint before closing the dialog.

v0.1.14

2026-10-30

  • Choose your quota emails - get them at 50%, 80%, 90%, or 100%, or turn them off, under Account → Notifications. You now also get an email when the quota runs out. See Quota emails.
  • Edit API keys - rename a key or change its expiry without rotating the secret.
  • Revoke all keys at once - from Account → Security, after confirming your password. See Revoke every key at once.
  • New home page, About, and FAQ - neuroapi.neurobro.ai shows sample answers, pricing, the AI tools it works with, and common questions before you sign in.
  • Use every unit of your quota - a mode that costs more than you have left now runs on what's left instead of returning 402 quota_exceeded. 402 now only means a payment failed.
  • Dashboard updates - a new Account page, a softer dark theme, and keyboard shortcuts (⌘/ or Ctrl+/ lists them).
  • Expired keys show as Expired in the dashboard. They used to show as Active.
  • The sidebar shortcut no longer blocks the browser's Save - it moved from ⌘S to ⌘B.
  • Terms and Privacy open without signing in.
  • Security patches across the API and the docs.

v0.1.13

2026-10-28

  • Breaking: new streaming event shape - with stream=true, every event is now {"type": ..., "data": {"answer": ..., "usage": ...}}. type is status_update while the agent works and complete at the end. The metadata object, tool-progress events, and internal status details are gone. The answer text is still at data.answer.chunk.content. If you read metadata.message_type, read type instead.

    Usage arrives once near the end with the same fields as a non-streaming response, so it has cost_units and no longer has total_tokens. See Streaming.

  • A limit on runs in flight at once - each account can now have 2 (Starter), 5 (Pro), or 10 (Enterprise) POST /agent/ask runs going at the same time, MCP calls included. One more returns 429 too_many_concurrent_runs with Retry-After and isn't billed. See Rate limits.

  • Long runs stop after 5 minutes - a non-streaming run that takes longer than 300 seconds now returns 504 agent_timeout and isn't billed. Stream long research with stream=true.

  • Request bodies are capped at 8 MiB - larger bodies get 413 with a plain-text body. That is well above the largest valid request.

  • message_history roles - only user and assistant turns reach the agent. system, developer, tool, and function turns are accepted and ignored, so put instructions in system_prompt instead. Any other role now returns 422 instead of 500.

  • Expired API keys stop working - a key whose expires_at has passed now gets 401. Before, it kept working.

  • Streams that fail after the full answer are billed - if the final answer was delivered and something fails afterward, the stream ends with [DONE] and counts as a run. Failures before the answer is complete are still free.

  • MCP answers on /api/v1/mcp directly - the path without a trailing slash no longer redirects, which some MCP clients didn't follow.

  • Agent runs continue after tool-call errors - a malformed tool call or a missing trading symbol no longer ends the run. Separately, mode=max uses a stronger model for long research.

v0.1.12

2026-10-23

  • MCP rejects API keys in the URL - requests to /api/v1/mcp that carry an API key in the query string now return 400 api_key_in_query. Proxies and logging tools often record full URLs, so send the key only in the X-API-Key or Authorization: Bearer header. If a key has ever been sent in a URL, rotate it from the dashboard.

v0.1.11

2026-10-16

  • Structured output is checked against your schema - when you send output_schema, the object you get back is checked for field types, required fields, allowed values, and number limits. If the agent gets something wrong, it corrects it before replying. If it still can't, the request fails and you aren't charged.
  • 422 errors for unsupported schemas - schemas are read as JSON Schema 2020-12. These now return 422 with the exact location of the problem: regular expressions (pattern, patternProperties), dynamic references ($dynamicRef, $recursiveRef), references that don't point to a definition in $defs, and schemas nested deeper than 32 levels or made of more than 500 parts.
  • null instead of made-up values - if a field allows null and the agent can't find the value, you get null instead of a stand-in like 0. Make such fields nullable. See Designing the schema.
  • Backup model on fast and smart - if the AI model cuts a response off halfway, the request now switches to a backup model instead of failing.

v0.1.10

2026-10-15

  • Breaking: a failed payment returns 402, not 403 - when your subscription's latest payment fails, /api/v1 requests return 402 payment_required instead of 403 no_active_subscription. Access returns as soon as a payment succeeds. If you handle 403 no_active_subscription, handle 402 too. See Billing.
  • Idempotency-Key no longer replays 402, 403, or 429 - a retry with the same key now runs again once you've paid, upgraded, or waited out the quota or rate limit, instead of returning the stored rejection. Stored replies now expire after 24 hours, as documented. See Idempotency.
  • mode=fast and mode=smart loop less on long conversations - fewer requests run long and return a repetitive or cut-off answer.
  • Subscriptions from restricted countries are refunded - if a subscription's billing address or card turns out to be from a country NeuroAPI can't serve, it is canceled and the payment refunded. Requests then return 403 no_active_subscription.
  • Checkout open again in Syria - following changes to U.S. sanctions policy. Other listed countries remain restricted at checkout and on billing details.

v0.1.9

2026-10-01

  • Checkout compliance by location - before paid checkout starts, NeuroAPI checks whether your connection appears to be from a restricted country. Local development is unaffected, and checkout still works when your country can't be determined.
  • Billing details verified for compliance - your billing address and card country are also checked when a subscription is created or updated, so a restricted region can't complete checkout by skipping the initial location check alone.

v0.1.8

2026-09-30

  • Bug fixes - minor fixes and stability improvements.

v0.1.7

2026-08-21

  • X-Request-Id on every response - the header was set only on a successful POST /agent/ask, so a 401, 403, 422, 429, or a GET /health call came back without one, even though those are the responses you need to report. Every response now carries an id, and a replayed Idempotency-Key returns the original request's id instead of a new one.
  • Every error response now has a documented schema - error bodies come in three shapes: coded ({"detail": {"code", "message"}}), plain ({"detail": "..."}), and the list-shaped 422. All three are now in the API reference, and the Errors guide lists every code with the status it arrives on and what clears it.
  • New Idempotency guide - covers the 24-hour replay window, the Idempotent-Replayed header, why a replay is never billed twice, and the cases that don't replay.
  • Quota and rate-limit headers documented - X-RateLimit-* are now declared on the success response as well as under 429, so you can read them before you're throttled. The X-Quota-* headers reporting your remaining plan budget are now covered in Billing.
  • mode=fast and mode=smart migrated to a current-generation model - the model previously serving both modes has been retired by its provider. Both now run on its successor and fall back to an independent second provider, so an incident at the first provider no longer surfaces as a 5xx. mode=max runs on a newer primary model with a three-deep chain behind it.
  • mode=max trims long multi-turn history - a large message_history could previously outgrow the model's context window and surface an upstream 400 mid-run. The history you submit is now authoritative and is trimmed locally ahead of each step, so a long conversation no longer hits that 400.
  • On-chain research - POST /agent/ask can now screen a token for scam flags, mint/freeze authority, and top-holder concentration, read buy/sell pressure across 5m-24h windows, rank a token's most profitable traders, and surface newly launched tokens filtered by age and liquidity.

v0.1.6

2026-07-14

  • Call the agent over MCP - NeuroAPI now supports the Model Context Protocol. Point any MCP client at https://api.neurobro.ai/api/v1/mcp (remote, Streamable HTTP) with your X-API-Key, and the ask_neuroapi tool runs the same single-turn research as POST /agent/ask, with the same rate limits, metering, and billing. See the MCP guide to connect.

v0.1.5

2026-06-28

  • Trade-setup confidence is tied to risk/reward - when POST /agent/ask includes a trade setup, its 1-10 confidence is anchored to the setup's own risk/reward and structure instead of being a free-form guess. The same setup now scores consistently, and a high number can't sit on a weak risk/reward, so you can set a threshold on it. The score rates the setup and can't tell you how a trade will end.
  • Tool use on mode=max - changes to how mode=max selects and calls tools mean requests that need live data (market metrics, technical analysis, trade setups) stall less often on tool selection.
  • Searchable docs - the documentation site now has full-text search. Press ⌘K (or Ctrl-K) or use the search bar to jump to any endpoint, guide, or field.

v0.1.4

2026-06-03

  • Structured output with a JSON Schema - POST /agent/ask now accepts an optional output_schema (a JSON Schema with an object root) and returns the validated object on a new output field. answer is then null, so exactly one of the two is ever set and you can consume the result as typed data instead of parsing prose.

    It's non-streaming only: combining it with stream=true returns 400, and a schema that can't drive structured output returns 422 - both before any usage is charged. Conformance is strict on mode=max and best-effort with automatic retries on fast/smart.

  • Steer the agent with a system prompt - a new optional system_prompt shapes the agent's tone, role, or output format (e.g. "answer as a fixed-income analyst, in bullet points"). It layers on top of the built-in instructions and can't override the agent's persona or safety guardrails.

  • International equity coverage - the agent can now pull quotes, fundamentals, financials, and technicals for stocks listed in Indonesia, Brazil, and Vietnam, and resolve a company name to its ticker. The existing US-equity tools remain.

  • Streaming restored on fast and smart - stream=true on these modes again streams the answer chunk-by-chunk instead of returning it as a single block at the end.

  • Lower latency on repeat and social-data requests - multi-turn requests that resend message_history keep more of the response cache warm on fast/smart, and requests that read social-sentiment data no longer stall when that upstream is briefly degraded.

v0.1.3

2026-05-26

  • Failed streaming runs are no longer billed - POST /agent/ask with stream=true previously charged you for runs that errored after the response started, while stream=false was already free on the same failure. Both modes now refund, so you only pay for runs that finish cleanly.
  • mode=max repairs tool-call pairs in long conversations - sending a message_history that contained a tool call without its paired result could trip an upstream 400 and abort the run. The agent now repairs the pairing before each step, so a multi-turn max session no longer fails late on that error.
  • Trade setups with a cost check - when your prompt expresses any directional view on a crypto, stock, or commodity, the response now includes a structured trading setup (entry, stop, take-profits, R:R) alongside the prose. Setups whose allocation-weighted R:R doesn't clear an assumed fee + slippage cost are rejected outright instead of being returned as marginal trades.

v0.1.2

2026-05-23

  • Usage alerts - you now receive an email the first time your request usage reaches 80% of your plan's quota for the billing period. It shows how many requests you've used, how many remain, and when the quota resets, so you can act before requests start returning 429. Manage notifications from your dashboard.

v0.1.1

2026-05-16

  • Request size limits on POST /agent/ask - requests are now validated against published limits: prompt up to 32,000 characters, and message_history up to 50 messages with each message's content up to 32,000 characters. Oversized requests are rejected with 422 before any quota is spent. The limits are published in the OpenAPI schema.

v0.1.0

2026-05-15

  • Initial public surface: GET /health, POST /agent/ask.

On this page