Trading Console

Public agent access

Agent-ready discovery, without private workspace access

Trading Console publishes machine-readable metadata for agents and crawlers while keeping operator workflows, account state, broker state, and authenticated market surfaces inside the protected app.

Read llms.txtView MCP card

Readiness posture

Public metadata, narrow capabilities, clear boundaries

Discoverable

Canonical documents expose robots policy, sitemap, markdown guidance, API catalog, OpenAPI, and MCP discovery.

Read-only

Public tools are marked read-only and return only overview, links, and boundary metadata.

Bounded

Operator workspace routes stay behind authenticated sessions under /app/*.

Discovery links

Canonical documents for agents

Agent access

Human-readable agent guide with the safe public boundary.

llms.txt

Markdown guide for crawlers and agent runtimes.

API catalog

Linkset catalog for API, OAuth, MCP, and skill metadata.

OpenAPI

OpenAPI document for the public-read agent endpoints.

MCP server card

MCP server card for read-only public tools.

OAuth resource

OAuth metadata for the public.read resource scope.

MCP tools

Read-only public tool surface

get_public_overview

Return the public overview, discovery links, and protected-route boundaries for PoisAr Trading Console.

get_agent_readiness_links

Return canonical public agent-readiness discovery links for PoisAr Trading Console.

JSON-RPC
POST /api/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Protected boundary

What public agents should not assume

/app/* is the private operator workspace.
/api/* is private unless listed in /openapi.json.
Public MCP tools cannot submit trades, approve workflow actions, or read account data.
Missing authenticated access should be treated as unavailable, not inferred.

Machine-readable first

Agents should start with the API catalog and llms.txt, then use the MCP server card only for read-only public overview and discovery metadata.

Open catalog

Full index

Published discovery endpoints