Submit a sanitized intent
Describe the missing read-only capability and hard constraints.
Infrastructure for agent fallbacks
ResolveMesh ranks manually approved, read-only tools across MCP, A2A, and REST, and records structured success or failure reports. Your agent executes directly with the provider; ResolveMesh never holds its credentials.
The free compatibility catalog is available now. Provider resolution is a pilot with no approved live providers yet; the response shown is illustrative, not a live match.
POST /v1/resolutionsPOST /mcpGET /openapi.json$ POST /v1/resolutions { "intentText": "EU case law search with citations", "capabilityTypes": ["DATA_RETRIEVAL"], "allowedProtocols": ["MCP", "REST"], "riskClass": "READ_ONLY" } status: MATCHED { "providerId": "prov_curia_search", "protocol": "MCP", "confidence": 0.94, "evidence": CAPABILITY_VERIFICATION }
From the 150-intent ranking benchmark and the July 2026 stratified remote-discovery study. Every number ships with its methodology. Read it.
How it works
ResolveMesh is not another agent framework or execution proxy. It is the neutral fallback an agent calls after its installed tools come up short.
Describe the missing read-only capability and hard constraints.
Compare compatible providers using current, observable evidence.
Feed success or failure back without sending provider output.
Public pilot
Applications are open for ten manually approved builders while the cohort establishes outcome evidence and support patterns. No card or sensitive data is needed to apply.
1,000 / UTC monthValidate REST or remote MCP against a bounded read-only use case and confirm up to three weekly compatibility watches.
$49 / monthRaise the allowance to 25,000 resolutions and manage the subscription on Stripe-hosted surfaces, with up to 100 daily compatibility watches.
The boundary
Neutrality is an engineering constraint here, not a slogan. Four refusals are load-bearing and versioned in the V0 specification.
ResolveMesh returns ranked connection details. Requests and results flow between your agent and the provider — never through the mesh.
No provider keys, no OAuth grants, no pass-through secrets. Authentication stays between you and the provider.
No raw prompts, examples, documents, or provider output are stored in resolution records. Account and watch data follow the privacy policy. Outcomes carry status, not content.
Demand signals publish only past 20 requests from five independent tenants in 30 days. Sparse-but-true is the intended result.
Machine surfaces
REST, remote MCP, and a typed SDK delegate to the same service with the same tenant quotas and the same narrow data boundary.
POST /v1/resolutionsAuthenticated JSON over HTTPS. Report results to /v1/outcomes with exact-replay idempotency.
POST /mcpStateless Streamable HTTP exposing resolve_intent and report_outcome tools.
@resolvemesh/sdkTyped contracts shared with the server — the same Zod schemas validate on both ends. Install the published SDK
Pricing
Start without a card. Upgrade only when ResolveMesh has become part of your agent's production path.