Docs
On this page
Last updated 2026-07-07

Capabilities & Limits

The InvesTeam API produces structured investment analysis: a Master Investment Brief, an AI committee's deliberation, and a red-teamed final synthesis. It is honest about its boundary — the output is decision-support analysis, not investment advice, and there is no trade execution anywhere in the platform. Knowing exactly what it returns and what it will not do is the difference between a sound integration and a legal exposure.

What does the InvesTeam API return?

The API returns the four artifacts of the analysis pipeline, each fetched by polling its stage:

  • A Master Investment Brief — the structured mandate distilled from your question, or a respectful rejected if the question is off-mandate.
  • A committee plan — the roster of AI members assembled for that brief and their research tasks.
  • An execution — the committee's progress and per-task findings as they land.
  • A live transcript — the deliberation, streamed turn by turn via a cursor.
  • A final analysis — the synthesized, red-teamed findings.

Every one of those responses that carries AI-generated output also carries a disclosure object (below). None of them is a directive to act.

Is the InvesTeam API investment advice?

No. The InvesTeam API returns decision-support analysis, not investment advice. The output is AI-generated and may contain errors. It is not a recommendation, solicitation, or offer, it is not tailored to anyone's circumstances, and it creates no advisory or fiduciary relationship. Your application and its users own every decision.

This is not a soft framing — it is a contractual condition of using the API. You must surface the not-advice + AI-generated disclosure to your end users, and you may not present the output as investment advice, investment marketing, or portfolio management without holding the licences that activity requires.

Can InvesTeam execute trades?

No. There is no execution surface and no brokerage connection anywhere in the platform. The API produces analysis and stops there; placing an order, moving money, or connecting to a broker is entirely outside its scope and always your own system's responsibility. This is a deliberate boundary, not a missing feature.

What is the disclosure object, and why must I keep it?

Because API consumers never see the InvesTeam product UI, the not-advice notice is delivered in the payload. Every successful response on an AI-output-carrying path — brief, orchestration, execution, transcript, and analysis — carries a top-level disclosure object with a bilingual (English + Hebrew) notice and four flags. It is additive: it never changes the rest of the body and never appears on errors.

Output is AI-generated and may contain errors and is not investment advice; you must show this not-advice + AI-generated disclosure to your end users and must not strip the response disclosure field (see https://investeam.io/api-terms).

The disclosure object is a contractual obligation. You must surface the not-advice + AI-generated notice to your end users in their language, and you must not remove or alter the disclosure field. See the Briefs reference and the platform Terms.

What are the API's other operational limits?

A few limits shape a real integration:

  • Programmatic keys are throttled. Submit routes are rate-limited and draw from a daily kickoff quota per key. See Rate Limits & Quotas.
  • Statuses are an open set. New states can appear within v1; treat any value you do not recognize as non-terminal. See Versioning & Deprecation.
  • hfk_ keys cannot manage keys. Issuing, rotating, and revoking keys is done by an interactively signed-in user, never with a programmatic key. See Authentication & API Keys.

Ready to build? Continue to the Quickstart, or read API or MCP to pick your surface.