KEVAREMESH — APIs for autonomous AI agents

Use one remote Model Context Protocol (MCP) server to match an agent task to original first-party API input contracts, verify whether a paid x402 endpoint is genuinely enabled, or compare public third-party provider quotes without calling providers.

Connect your MCP client

https://fpgtwgtoqtokpitzlbie.supabase.co/functions/v1/kevaremesh-agent-discovery-mcp-v1

Machine-readable MCP server.json

Find an API for a task

First call kevaremesh_route_intent with a goal. The discovery call is free and can inline up to two original first-party input schemas. Use kevaremesh_find_owned_api when the capability is already known.

The 24 owned catalog entries include 21 local pure-algorithm capabilities: CSV/JSON conversion, Base64 encoding, URL encoding and parsing, JSON validation, stable JSON canonicalization, merge patch, JSON pointer, JWT inspection, cryptographic hashing, secure random bytes, UUID generation, text normalization, timezone and timestamp conversion, unit conversion, semantic-version comparison, UTC timestamps and x402 utilities. Three network-dependent capabilities are not cleared for paid execution.

Original first-party catalog with indicative prices and current flags

First listed product — Base64 Transform

The existing base64-transform product encodes or decodes UTF-8 text. The indicative price is 0.001 USDC per paid invocation on Base Mainnet. Actual availability is determined exclusively by the live merchant x402 resource list below; an empty listing means payment is disabled.

Read original input contract and current product metadata

POST https://fpgtwgtoqtokpitzlbie.supabase.co/functions/v1/kevaremesh-owned-x402-v1/execute/base64-transform
Content-Type: application/json

{"text":"Hello","operation":"encode"}

This is the request format only, not a free trial or a completed purchase. A buyer-owned x402-capable client must obtain a live 402 challenge and explicitly authorize the current payment amount and recipient. Do not send funds if the merchant's current listing does not include this exact endpoint. After a signed payment preserve its receipt ID, independently reconcile Base USDC settlement and fetch the original result. A receipt reservation must never be paid twice.

Pay only for actually enabled merchant resources

A catalog listing or a free preview does not mean payment is enabled. Inspect the native, current x402 merchant resource list before any payment. Empty resource lists mean do not pay. For an enabled resource, the buyer's own x402 client reviews and authorizes the Base USDC payment; KEVAREMESH discovery does not sign or handle customer wallets. The original result is released only after independent settlement verification. Preserve the private receipt ID, reconcile the chain transaction, then retrieve the result. Never pay twice for a reserved receipt.

Compare third-party providers

kevaremesh_discover_provider_candidates and kevaremesh_quote_provider_batch provide free bounded provider metadata/quotes. Public metadata never grants supplier API execution rights. Buyer-specific authorization and provider-direct payments remain separate.

Lost the receipt ID after payment? Keep the original x402 payment signature private; compute its SHA-256 hash locally and use the read-only kevaremesh_locate_owned_receipt tool or POST to the original /receipt/locate with payment_signature_sha256. Never submit the raw signature, never put the hash in URLs, and never pay again to recover a previous order. See receipt recovery instructions.

Discovery is not a purchase, a revenue claim, or a guarantee that any external AI model selects this server. Paid resources and quote availability depend on the live connected catalog, verified merchant listing and applicable provider permissions.