KEVAREMESH

Connect an AI agent

1. Connect your Streamable HTTP MCP client directly to https://fpgtwgtoqtokpitzlbie.supabase.co/functions/v1/kevaremesh-agent-discovery-mcp-v1. The current 14-tool server is described in the MCP server card.

2. Invoke kevaremesh_route_intent to discover relevant owned tools, or kevaremesh_find_owned_api when you know an API keyword. Example:

{"goal":"Convert a CSV string to JSON"}

3. Read the original input contract and optionally run a free preview. For buyer-preauthorized x402 spending, call kevaremesh_auto_use: a compatible buyer-side payer can sign within its own policy and retry the same MCP tool. KEVAREMESH never signs or holds buyer keys. Pending settlement is recovered with the same tool and the existing receipt_id or access_key, optionally with an independently verifiable Base transaction_hash; do not pay twice. Signed real-buyer end-to-end completion is not yet proven.

First-party APIs and original input contracts

Of the 24 catalog products, 21 deterministic utilities have current merchant-listed Base USDC x402 routes. The listed price is 0.001 USDC for 20 products and 0.005 USDC for UUID v4. Three network-dependent tools provide free previews on a small allowlist; they are not general-purpose paid URL fetchers.

Start with a free metadata request. For example, JSON Stable Canonicalize has a documented original input contract and an independently listed merchant route:

GET https://kevaremesh-web.vercel.app/.well-known/x402
GET https://kevaremesh-web.vercel.app/api/owned-original-contract/json-stable-canonicalize
GET https://kevaremesh-web.vercel.app/openapi.json

The exact payable URL and current price must be read from the live merchant manifest. A payment challenge is not a charge or proof of delivery. Confirm the merchant, network and payment terms before any buyer-authorized purchase.

Use the product request form to inspect input schemas and try the three safe network previews without making a payment. The form never signs or submits buyer payments.