Agent integration

Integrate a fallback, not another framework.

Call ResolveMesh only after an agent's installed tools cannot satisfy a read-only intent. Receive ranked connection details, execute directly with the selected provider, then report a compact outcome.

Read the OpenAPI contract Review the evidence model

Interfaces

One service, five integration surfaces

REST is canonical. Public compatibility MCP delegates to the same bounded catalog functions as the public REST routes; authenticated MCP remains tenant scoped. OpenAPI gives agents and builders a machine-readable map of the current REST surface.

POST /v1/resolutions

REST

Authenticated JSON resolution and idempotent outcome reporting over HTTPS.

POST /mcp

Remote MCP

Streamable HTTP tools for resolution, outcomes, and public gap listing.

POST /mcp/public

Public compatibility MCP

Unauthenticated, stateless Streamable HTTP with exactly two read-only tools: compatibility lookup and approved changes.

GET /openapi.json

OpenAPI 3.1

The exact documented REST surface with schemas derived from the canonical Zod contracts. Open it.

@resolvemesh/sdk

TypeScript pilot client

The publication-ready package used in pilot integrations. Its first public npm release remains a founder-operated step.

REST quickstart

One request, no execution proxy

ResolveMesh does not proxy provider execution. Send a sanitized capability requirement, not a prompt, document, credential, personal profile, or provider payload.

production · resolution request

$ curl --fail-with-body https://resolvemesh.com/v1/resolutions \
  -H "Authorization: Bearer $RESOLVE_API_KEY" \
  -H "Content-Type: application/json" \
  --data '{"intentText":"Retrieve the latest SEC 10-K for a public company","capabilityTypes":["DATA_RETRIEVAL"],"allowedProtocols":["MCP","REST"],"riskClass":"READ_ONLY"}'

Data boundary

Keep content and credentials out of the mesh

The V0 contract is deliberately narrower than a tool execution platform. The caller owns provider selection, authentication, invocation, and result handling.

never

Raw prompts and documents

Submit a narrow sanitized intent. Do not send source content or personal profiles.

never

Provider credential custody

Provider keys and OAuth grants stay between the caller and the provider.

never

Provider execution

ResolveMesh returns connection details; the caller invokes the provider directly.

never

Provider output retention

Outcome reports carry status, duration, and a bounded failure code—not provider output.

Limits and retries

Bounded by plan and resolution

Quota reservation and the outcome ceiling are atomic. Exact idempotent replays remain available after a ceiling is reached.

1,000 / UTC month

Free

Schema-valid authenticated resolution attempts. Outcome reports do not consume resolution quota.

25,000 / UTC month

Builder Pro — $49/month

The same V0 execution and retention boundary with a higher resolution allowance.

20 distinct reports

Outcome ceiling

Per resolution across all returned capabilities. Reuse the exact idempotency key when retrying the same report.

Current access

Public applications, manually approved

Public pilot applications are open, but self-service API-key issuance is not enabled. Access remains intentionally bounded while the first provider and builder cohorts produce real outcome evidence.

What is ready

REST, remote MCP, OpenAPI, tenant quotas, outcome reporting, Stripe-hosted billing, and privacy-thresholded demand intelligence.

What is still gated

Self-service keys, public SDK distribution, and capability promotion remain closed until their operational evidence and support paths are ready.

Apply to the public pilot.