ResolveMesh

Infrastructure for agent fallbacks

Find the capability your agent is missing.

ResolveMesh ranks manually approved, read-only tools across MCP, A2A, and REST, then learns from the outcome. Your agent executes directly with the provider; ResolveMesh never holds its credentials.

Apply to the public pilotRead the integration guide
POST /v1/resolutionsPOST /mcpGET /openapi.json
resolution · v1live
$ 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
}

Published evidence

86%Precision@1
89.3%Precision@3
823Tools inspected
100Providers studied

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

One narrow job

ResolveMesh is not another agent framework or execution proxy. It is the neutral fallback an agent calls after its installed tools come up short.

01

Submit a sanitized intent

Describe the missing read-only capability and hard constraints.

02

Receive ranked connections

Compare compatible providers using current, observable evidence.

03

Report the outcome

Feed success or failure back without sending provider output.

Public pilot

Put a real fallback path into production

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 month

Start on Free

Validate REST or remote MCP against a bounded read-only use case and confirm up to three weekly compatibility watches.

$49 / month

Move to Builder Pro

Raise the allowance to 25,000 resolutions and manage the subscription on Stripe-hosted surfaces, with up to 100 daily compatibility watches.

Apply to the public pilotContact support

The boundary

Defined by what it refuses to do

Neutrality is an engineering constraint here, not a slogan. Four refusals are load-bearing and versioned in the V0 specification.

never

Execution proxying

ResolveMesh returns ranked connection details. Requests and results flow between your agent and the provider — never through the mesh.

never

Credential custody

No provider keys, no OAuth grants, no pass-through secrets. Authentication stays between you and the provider.

never

Content retention

No prompts, examples, tenant identities, documents, or provider output are retained or published. Outcomes carry status, not content.

never

Thin aggregates

Demand signals publish only past 20 requests from five independent tenants in 30 days. Sparse-but-true is the intended result.

Machine surfaces

Three doors, one resolver

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/resolutions

REST

Authenticated JSON over HTTPS. Report results to /v1/outcomes with exact-replay idempotency.

POST /mcp

Remote MCP

Stateless Streamable HTTP exposing resolve_intent and report_outcome tools.

@resolvemesh/sdk

TypeScript SDK

Typed contracts shared with the server — the same Zod schemas validate on both ends.

Pricing

Validation pricing

Start without a card. Upgrade only when ResolveMesh has become part of your agent's production path.

Free

$0 / month
  • 1,000 resolutions per UTC month
  • REST, MCP, and TypeScript SDK
  • Outcome reporting
  • 3 confirmed weekly compatibility watches
Production paths

Builder Pro

$49 / month
  • 25,000 resolutions per UTC month
  • The same narrow data-retention boundary
  • Stripe-hosted billing management
  • 100 confirmed daily compatibility watches