Developers · API & MCP

Intelligence API & MCP, Documentation

The LyraMind Intelligence API turns market data, filings, and macro signals into grounded, cited, compliance-safe intelligence. 36 endpoints, 13 MCP tools. Every response carries a Trust Layer.

Offline-safe & anonymous-friendly. No key required to integrate and test, unauthenticated calls run on the anonymous tier (60 req/min per IP) against live data where configured and deterministic sample data otherwise. Every response reports its data_mode and never hides sample data.

Quick start

# A grounded read on any symbol, no key needed
curl -X POST https://api.lyramindos.com/v1/company \
  -H "Content-Type: application/json" \
  -d '{"symbol":"NVDA"}'

# The go/no-go gate an agent checks before it acts
curl -X POST https://api.lyramindos.com/v1/readiness \
  -H "x-api-key: $LYRAMIND_KEY" \
  -d '{"symbol":"NVDA","action":"rebalance"}'

API host shown for illustration. The self-describing index lives at GET /v1; every response includes a trust{} envelope (confidence · sources · evidence · reasoning · data_mode · compliance).

Authentication & tiers

TierRate limitHow
anonymous60 / min (per IP)no key, test freely
sandbox120 / minbuilt-in demo key lm_sandbox_demo
standard600 / minx-api-key header
enterpriseunlimitedx-api-key header

Responses set X-RateLimit-* and X-LyraMind-Tier headers. GET /v1/usage reports your own usage.

Endpoints

Market intelligence

POST /v1/companyOne-call company snapshot: read + confluence + risks + graph connections
POST /v1/explainPlain-English "what & why" for a symbol (retail / pro)
POST /v1/committeeAI Investment Committee + LyraMind Score (5 lenses → composite)
GET /v1/pulseInterpreted market-event feed over a universe
POST /v1/summarizeCondense text or a symbol's situation to key points

Trust & verification

POST /v1/readinessAgent Readiness gate, AGENT_READY / REVIEW_REQUIRED / DO_NOT_EXECUTE
POST /v1/verifyMulti-reasoner verification, consensus, agreement, contradictions
GET /v1/memoryInstitution Memory, a name's track record off the ledger
GET /v1/ledger · /verify · /statsTrust Ledger, entries, hash-chain proof, calibration
POST /v1/ledger/outcomeReconcile a past verdict (borne_out / contradicted / unclear)

Graph · twins · agents · execution

GET /v1/graph · /graph/cascadeKnowledge graph + macro→sector→company cascade
GET /v1/twin · POST /v1/twin/askDigital twin profile + conversational ask
GET /v1/marketplace · /runAgent personas (investor / compliance / macro / catalyst)
POST /v1/execution/decideExecution-Readiness, go/no-go before money moves
GET /v1/execution/providersPluggable execution-provider seam

Corporate AI readiness · data

POST /v1/ai-readiness/reportAI Readiness report for a draft filing
POST /v1/ai-readiness/simulateInstitutional AI Simulator
POST /v1/disclosure/scanDisclosure legibility scan
GET /v1/ai-readiness/benchmark · /historyPeer benchmark + continuous monitoring
GET /v1/alpha/feedInstitutional Alpha Feed (gated)
GET /v1/questions/insightsQuestion Intelligence (Q-IQ)

MCP server, 13 tools for agents

Expose the engine to any agent (Claude Desktop, agent frameworks, execution platforms) over Model Context Protocol. One-command install:

python services/mcp/setup.py   # prints the config and verifies the server live

Tools: lyramind_agent_readiness · lyramind_execution_readiness · lyramind_record_outcome · lyramind_ledger_audit · lyramind_ask · lyramind_agent · lyramind_ai_readiness · lyramind_disclosure · lyramind_explain · lyramind_company · lyramind_committee · lyramind_pulse · lyramind_summarize. Every result carries the Trust Layer and a one-line agent-readable summary.

Building on the API or MCP? Request a key for standard/enterprise tiers and the Alpha Feed. The anonymous tier needs no key.