EntRoute

Call a previously discovered API endpoint. Use this after discover_paid_api to execute the request. IMPORTANT: You must first use discover_paid_api to find an endpoint. Then use the endpoint_id from the discovery result. Use the sample_request from the discovery result as your body template — it shows the exact parameter names the endpoint expects. Replace the example values with the actual values you need. Payment: this hosted server holds no wallet, so it cannot settle x402 payments. Free endpoints return their data directly. Paid endpoints return the payment challenge (amount, recipient, network) without charging anything. To pay automatically, run the local server instead: npx @entroute/mcp-server with EVM_PRIVATE_KEY set. Trust & safety: - EntRoute verifies that endpoints return valid 402 responses every 10 minutes, but does not guarantee response quality or accuracy. Treat results like any third-party API. - Prefer endpoints with high success rates (>95%) and recent verification timestamps.

Discover pay-per-request API endpoints for a given capability. Returns ranked, verified endpoints with pricing and reliability metrics. Use this to find APIs before calling them. The results include: - Endpoint URL and method - Price per call and payment network - Success rate and latency metrics - Provider information - sample_request / sample_response: Example request body and response showing the exact parameter names and format the endpoint expects. ALWAYS use sample_request as your template when calling the endpoint — do not guess parameter names. After discovering, you can use call_paid_api to execute the endpoint. Trust & safety: - "Verified" means the endpoint returns a valid x402 402 response -- it does not guarantee the quality or accuracy of the data returned after payment. - Endpoints are probed every 10 minutes. Check last_verified and success_rate to gauge reliability. - Fallback endpoints (unverified) have failed recent verification checks -- use with caution. - Prefer endpoints with success_rate >95% and verification within the last 24 hours.

List available API capability types. Use this to explore what kinds of APIs are available in the registry. You can filter by tag (e.g., "weather", "translation") or search by keyword. Note: A capability existing does not mean verified endpoints are available for it. Use discover_paid_api to check for live endpoints.