# Eidos

> Decision market analysis. Eidos analyzes decision markets. Compare the choices being priced, inspect trading activity and follow recorded execution and outcomes. Explore sourced findings in the App or retrieve structured analysis through API and MCP. Coverage spans five engines on Solana, Unichain, Base and Gnosis Chain; available evidence varies by decision. Versioned analytical instruments state their evidence, method and coverage. Sourced interpretations explain what findings support and what remains uncertain. Reviewed corrections preserve prior records; usage alone does not establish improved accuracy.

Eidos provides independent decision market analysis. Each engine supplies its own decision mechanism; Eidos keeps the record around it. It reads publicly cited research and each engine's confirmed onchain state, five engines on Solana, Unichain, Base and Gnosis Chain. Missing wallet-forensics or market inputs never classify LOW. Complete evidence that does not match a monitored vector classifies NO-MATCH, not LOW. Catalog-only and treasury-only rows are not decisions. Draft and pending markets stay on the App's Live decisions.

## Surfaces

- [For Organizations](/organizations/): What market-governed organizations get: window monitoring, decision semantics, adversarial findings, treasury exposure — and the refusals
- [For Funds](/funds/): What funds and market participants get: live market state, scenario-dependent flip-cost lower bounds, evidence completeness, and the historical record
- [For Agents](/agents/): What economic agents get: the decision-context fields, the tools and keyless URLs that answer each, and what no payload will ever carry
- [Add your organization](/register/): Where an organization states what the chain cannot show, in its own words, checked against the documents it cites and dated; coverage never depends on it
- [Start a pilot](/pilot/): The commercial front door — how a design-partnership engagement is scoped, and why engagement prices are quoted rather than published
- [Approach](/approach/): The decision record as built: what is decoded, what the record keeps, independent analytical results, and the surfaces that read them, with every count derived from a registry
- [Methodology](/methodology/): Independent analytical instruments, historical review contracts and the versioned attack-vector library
- [Vector library JSON](/vectors/library.json): Machine-readable vector definitions
- [Review contracts JSON](/vectors/reviews.json): Historical machine-readable review contracts
- [Decisions](/decisions/): Every decoded decision on every engine, one page each, in the record's form: what it was for, what was known, what was done and what followed. Each page is the decision's IRI; the same record resolves by exact key, keyless, at /api/objects
- [Ontology](/ontology/): The record's vocabulary as a page: every class and property the decisions, reviews and series are stated in, each at the anchor its IRI names
- [Decision cases](https://eidos.software/app/cases/): Finalized published cases with their historical findings
- [App](https://eidos.software/app/): The app SPA — tracked organizations with live quotes, the ranked open-window feed, reports, and the Live decisions sheet
- [Docs](https://eidos.software/docs/): Product documentation and the OpenAPI reference, rendered by Scalar from the same registries the product ships
- [Organizations](https://eidos.software/app/organizations/): Tracked organizations, cited treasuries, and live quotes
- [Live decisions](https://eidos.software/app/monitor/): Current MetaDAO decision state, thresholds, and pass/fail TWAPs, decoded from Futarchy v0.6 program accounts
- [Calendar](https://eidos.software/app/calendar/): Every pending recording window ranked by lifecycle stage, with Eidos's dated reports beneath
- [Activity](https://eidos.software/app/activity/): Dated rows of what moved — windows opening, entering their closing stretch, closing, and Eidos's reports — derived from the current snapshot
- [Alerts](https://eidos.software/app/alerts/): Daily digest, notification channels and browser alert rules, separate from saved items on Watchlist
- [Watchlist](https://eidos.software/app/watchlist/): What you starred — organizations, decisions, engines — with each one's latest move, the free Watchlist email when a starred window opens, nears its close or closes, or a starred organization's story ranks; general notification settings are on Alerts
- [Profile](https://eidos.software/app/profile/): Your account: sign-in state, alert rules, plan, and developer access (live API + MCP install line)
- [Research](/research/): Published posts on mechanism, market, method, and provenance
- [FAQ](/faq/): The rulebook as questions — classifications, withhold rules, and what Eidos declines
- [FAQ JSON](/faq/faq.json): Machine-readable FAQ registry
- [Catalog JSON](/data/catalog.json): Rendered catalog snapshot
- [Organization statements JSON](/data/organization-statements.json): What each organization says in its own words, checked against the document it cites; a lapsed statement is not current
- [History JSON](/data/history.json): Append-only sourced history
- [Ontology Turtle](/ontology/eidos.ttl): The product ontology as OWL 2 — the decision record, analytical runs, sourced interpretations, historical review contracts, state partitions and mechanism taxonomy; safety ratings remain outside the model
- [Ontology KG JSON](/ontology/kg.json): The same ontology as a node-link knowledge graph, with which mechanism component each vector exploits and detector coverage of that surface
- [Ontology SHACL shapes](/ontology/shapes.ttl): SHACL shapes that validate data against the ontology — generic review findings admit roster provenance; vector findings require exactly one monitored vector and classification; finding properties are closed, so a payload with a composite field fails validation
- [MCP](https://eidos.software/docs/tag/mcp): The MCP guide — install, tools, resources and the metered handshake for the remote MCP endpoint at /api/mcp (stateless JSON-RPC, 28 read-only tools plus the six registry documents as MCP resources; 27 tools need no key, one is metered per pull over x402. Metering is off until the operator activates it, and until then the packet does not serve (GET /api/review-packet answers 503 X402_DISABLED); once it is on, each caller's first 10 review packets per UTC day are free, and after that a pull costs $0.02 in USDC by default, payable on Base or Solana (whichever the operator has enabled) — the HTTP 402 quotes the live price and networks.)

## Optional

- [Status](https://status.eidos.software/): Live-path health and scheduled clock
- [Privacy](/privacy/)
- [Terms of Service](/terms/)