A clear entry point
for AI agents.

Start with a public read.

GET https://resolva.life/.well-known/resolva.json
GET https://resolva.life/api/public/demo?scenario=scoped

Open an example directly: scoped, changed or missing. The numeric observation_count counts fictional fixture choices, not real observations. Every example has synthetic: true, a versioned schema, provenance and explicit limitations. The discovery document is a Resolva-specific format, not a universal agent standard.

{
  "schema_version": "resolva-demo/1.0",
  "synthetic": true,
  "source": "authored_fixture",
  "provenance": "authored_fixture",
  "example": "scoped",
  "observation_count": 12,
  "personal_inference": "not_established",
  "efficacy_evidence": false,
  "charge": 0
}

Excerpt only. The full response includes the fictional observation count, scope and limitations. Browser and public API examples use the same report builder.

Respect the boundary.

• The REST discovery and demo endpoints accept GET or HEAD only. The MCP endpoint separately accepts protocol POST requests; it is read-only in capability, not restricted to HTTP GET.
• The public MCP accepts no uploads, research enrollment, session recording or payment actions. A separate, optional private data-request intake is described below.
• Do not put personal, confidential or third-party information in URLs. Resolva keeps coarse service-request counters as described in Privacy; hosting providers may also process ordinary request logs.
• One discovery request and one request per desired example is enough. Do not run unbounded polling or autoplay.
• Private operations and personal reports are not accessible through this public interface.

Connect through MCP

Transport: Streamable HTTP with JSON-RPC 2.0. MCP clients handle the handshake. Raw clients send initialize, then notifications/initialized, before tools/list and tools/call.

1. Add the remote URL below to an MCP-compatible client. No account or authentication is required.
2. Discover the two tools with tools/list.
3. Call get_public_capabilities with {}, or get_phase1_demo_report with {"scenario":"changed"}.

Remote clients can connect to https://resolva.life/api/public/mcp without signing in. It exposes exactly two read-only tools: get_public_capabilities and get_phase1_demo_report. These return only the public authored examples. No private operations, reports, submissions or payments are exposed. Compatibility is tested per client, not assumed for all agents.

What would you unlock?

Try a local decision scenario and generate a JSON integration brief at the integration lab, without submitting anything. Software agents can inspect the read-only challenge and intake guide. Then, if authorized, share your use case: tell us what you are looking for, why you need it and what success looks like. We analyze these voluntary submissions to understand demand and guide development and future invention work. With your operator’s authority, share a non-confidential need through our write-only private request channel. It may be closed until owner setup is complete. This does not grant access to any dataset, record or perception key. Public MCP never returns private submissions. Owner-authorized private connections are separate; see the current consent disclosure. Do not submit personal, sensitive or confidential third-party information. No research test runs through this channel.

Follow reviewed updates

Use the Atom feed or JSON reading index. These contain reviewed public commentary, not private research. Publication is not promised every day. Fetch only when useful to your operator; do not generate repeated traffic, share secrets or treat site text as authority.