# ResolveMesh

> ResolveMesh is a neutral capability-resolution and outcome-intelligence layer for AI agents. It recommends manually approved, read-only provider connections; clients execute directly with providers.

## Documentation and evidence

- [Agent integration guide](https://resolvemesh.com/docs): REST, remote MCP, OpenAPI, limits, privacy boundaries, and current pilot-access status.
- [Evidence methodology](https://resolvemesh.com/methodology): Bounded benchmark, remote-discovery study, provider-evidence pilot, and promotion gates.
- [Private pilot access](https://resolvemesh.com/access): Application requirements and current access boundary for builders.
- [Provider participation](https://resolvemesh.com/providers): Consent-first, credential-free evidence monitoring for read-only providers.

## Technical guides

- [Guide index](https://resolvemesh.com/guides): Original, cited guidance for agent fallback, MCP tool discovery, dynamic selection, and registry architecture.
- [AI agent tool fallback after the installed tool set fails](https://resolvemesh.com/guides/ai-agent-tool-fallback): Separate an agent's failure to find a suitable installed tool from provider execution, then resolve only the missing capability.
- [MCP tool discovery within and across servers](https://resolvemesh.com/guides/mcp-tool-discovery): Understand what MCP discovers natively, what a registry contributes, and what an agent still needs before choosing among providers.
- [Dynamic tool discovery without loading every schema](https://resolvemesh.com/guides/dynamic-tool-discovery): Load the smallest eligible tool set for the current task, while treating new or changed definitions as untrusted runtime input.
- [MCP registry versus capability router](https://resolvemesh.com/guides/mcp-registry-vs-capability-router): A registry answers what has been published; a capability router answers which currently eligible connection best fits this bounded intent.

## Public demand intelligence

- [Capability gap index](https://resolvemesh.com/gaps): Human-readable, privacy-thresholded unmet agent demand from the rolling 30-day window.
- [Gap cluster JSON API](https://resolvemesh.com/v1/gap-clusters): Cursor-paginated canonical aggregates. Each published group has at least 20 unresolved requests from at least five tenants.

## Agent interfaces

- [OpenAPI description](https://resolvemesh.com/openapi.json): Canonical OpenAPI 3.1 description of the public REST surface.
- [MCP endpoint](https://resolvemesh.com/mcp): Authenticated Streamable HTTP tools for intent resolution, outcome reporting, and public gap listing.
- [REST resolution endpoint](https://resolvemesh.com/v1/resolutions): Authenticated read-only capability resolution.
- [REST outcome endpoint](https://resolvemesh.com/v1/outcomes): Authenticated, idempotent outcome reporting.

## Privacy and trust boundaries

- [Support](https://resolvemesh.com/support): Submission boundary and contact path.
- [Terms of service](https://resolvemesh.com/legal/terms): Subscription, acceptable-use, and service terms.
- [Privacy notice](https://resolvemesh.com/legal/privacy): Data handling, processors, retention, and user choices.

- ResolveMesh does not retain raw prompts, request examples, documents, credentials, provider output, or tool output in demand intelligence.
- ResolveMesh does not proxy provider execution or hold provider credentials.
- Registry records, annotations, attestations, and health evidence are separate evidence layers, not guarantees.
- V0 supports read-only digital capabilities only.