LIVE / SYNTHETIC AGENT SURFACE

Use Qelly from the agent you already work in.

Connect one public MCP endpoint from a compatible agent client. Qelly validates a bounded scenario, runs the deterministic synthetic portfolio kernel, and returns a signed run reference under the same reproducible evidence contract.

Connect a provider Try the browser-local demo

CAPABILITY MAP

One interface. Four explicit maturity states.

The public endpoint proves the interaction contract. Private portfolio work and learned world models remain behind the controls and evidence they require.

LIVE / SYNTHETIC

Public Portfolio MCP

A bounded, unauthenticated product proof with one synthetic portfolio, deterministic calculations, signed run references that expire within 60 minutes, text results, and a read-only embedded view.

No holdings upload. No Qelly Event Markets key. No portfolio-specific model training.

NEXT / PRIVATE

Governed portfolio workspace

OAuth, tenant-scoped access, encrypted uploads, immutable portfolio snapshots, approvals, and audit records come before real holdings or continuous workflows.

RESEARCH

Event-conditioned world models

Event-conditioned financial world models remain a research program for separating branch probability, financial consequence, and decision robustness.

Portfolio-specific training begins only after OAuth, tenant isolation, and approved private-holdings ingestion. It is not part of the public endpoint.

OUT OF SCOPE

Consequential authority

Qelly does not provide investment advice, trade execution, custody, or a self-approved recommendation. Every decision artifact remains analysis for human review.

PROVIDER-NEUTRAL FLOW

The conversation changes. The calculation does not.

The agent interprets and explains. Qelly validates, calculates, signs, and returns the evidence.

  1. YOUR AGENT State premise · ask · explain
  2. QELLY PORTFOLIO MCP Validate · calculate · evidence
  3. HUMAN REVIEW Compare · decide · resolve
  1. 01 / ListDiscover the bounded synthetic portfolio.
  2. 02 / CompileTurn a quantified premise into explicit factors.
  3. 03 / ReviewInspect units, ranges, warnings, and assumptions.
  4. 04 / RunEvaluate only the reviewed scenario.
  5. 05 / RetrieveReopen the signed decision artifact.
  6. 06 / CompareInspect bounded actions and residual downside.

TOOL MANIFEST

Five tools, each with one bounded job.

There is no database query, code-execution, upload, account, or trading tool on the public surface.

  1. list_demo_portfolios Return the available synthetic case and its declared coverage.
  2. compile_scenario Compile supported quantified language into a reviewable factor scenario.
  3. run_stress_test Evaluate the reviewed scenario with the deterministic synthetic kernel.
  4. get_run Verify a Qelly-signed reference and reconstruct the same result.
  5. compare_candidate_actions Expose ranking stability, trade-offs, constraints, and residual downside.

STARTER PROMPTS

Make the review step visible in the conversation.

These prompts use the same five bounded tools. Start with compilation, inspect the assumptions, and run only after review.

  1. 01 / Compile and pause “Use Qelly Portfolio Demo. List the synthetic portfolio, compile the higher-for-longer preset, and stop so I can inspect every factor, unit, and warning.”
  2. 02 / Run after review “Run only the reviewed scenario. Explain the loss attribution and distinguish scenario severity from probability.”
  3. 03 / Retrieve and compare “Retrieve the signed run, compare all bounded candidate actions, and explain residual downside without presenting investment advice.”

PUBLIC DATA BOUNDARY

Synthetic inputs only. Private holdings stay outside.

The browser-local demo and remote agent endpoint have different execution boundaries, so Qelly states both explicitly.

SENT TO THE PUBLIC ENDPOINT

Bounded synthetic tool inputs

Only bounded synthetic scenario inputs are sent to Qelly when an agent calls the remote MCP endpoint. The public endpoint is stateless and its analysis is non-persisting.

Its short-lived run reference is signed for integrity, not encrypted. Never place confidential information in a public-demo premise.

NOT ACCEPTED

No private portfolio channel

The public surface does not accept uploads, real holdings, credentials, or Event Markets keys. It cannot connect a brokerage, monitor a live portfolio, or train a portfolio-specific model.

The separate browser-local demo calculates on the visitor's device. Read the complete privacy boundary.

Inspect the pinned evidence case →

NEXT / PRIVATE

Authentication and governance come before personalization.

OAuth, tenant isolation, encrypted uploads, real holdings, governed approvals, continuous monitoring, and subscriptions are the next authenticated layer—not capabilities of this public demo.

CONNECT

Choose a host. Keep the same Qelly boundary.

Provider controls and plan eligibility change. These concise setup notes render the checked-in guides without claiming a capability a host has not documented.

HOST GUIDE

ChatGPT

services/portfolio/docs/agents/chatgpt.md
  1. Open the supported custom-app or developer-mode controls for your workspace.
  2. Add https://www.qelly.ai/demo/mcp with no authentication.
  3. Confirm the five synthetic tools, then ask Qelly to compile and pause for review.

HOST GUIDE

Claude

services/portfolio/docs/agents/claude.md
  1. Open remote custom-connector settings on a supported Claude plan.
  2. Add the public endpoint with no authentication and inspect the discovered tools.
  3. Request scenario review before Qelly runs or compares the synthetic actions.

HOST GUIDE

Kimi-compatible developer clients

services/portfolio/docs/agents/kimi.md

Consumer Kimi custom-connector support is not yet claimed. Wave A targets Kimi Code and verified Kimi-compatible developer clients.

  1. Add a remote Streamable HTTP MCP server in a compatible developer client.
  2. Use the public endpoint without a credential and review tool permissions.
  3. Use text and structured results when the host does not render the embedded app.

PORTABLE CONTRACT

MCP and other agents

services/portfolio/docs/agents/mcp.md
  1. Connect over remote Streamable HTTP and negotiate a supported 2025 MCP version.
  2. Use text-first tools and structured content as the canonical portable result.
  3. Keep Event Markets credentials and private holdings outside this public surface.

PRODUCT BOUNDARY

Portfolio and Event Markets remain deliberately separate.

Qelly Event Markets has a separate product, data, session, and authorization boundary. Its API key is not a Portfolio credential and should never be pasted into this endpoint.

Understand the Event Markets boundary →

TRY THE LIVE BOUNDARY

Start with synthetic evidence. Add private data only after the controls exist.

Connect the public endpoint, inspect every assumption, and keep a human in the decision path. For a governed private pilot, define the portfolio workflow and approval boundary first.

Run the browser-local demo → Inspect the pinned evidence case → Discuss a private pilot ↗