Find and evaluate public API endpoints and MCPs that match your query. Set `q` to a natural language query, keywords, an API name, or a question — results are matched by meaning and keyword; each result includes `id`, `resourceType` (`endpoint` or `mcp`), `name`, `description`, `method` (for an `endpoint`) or `transport` (for an `mcp`), `url`, and `evaluateGuide` — an evaluation of what the endpoint or MCP does, when to use it, and its limitations. Review `evaluateGuide` to pick the best fit, then pass each chosen result's `id` and `resourceType` (as `type`) to `integrate`. Paginate with `cursor` from `meta.nextCursor` (`limit` defaults to 10, max 25; pagination stops at 40 results total). No authentication required.
Best practices for querying:
- Use focused keyword queries that include the product or provider name along with the endpoint details, for example "PayPal create invoice".
- Alternatively, use natural language queries such as "PayPal API to create an invoice".
- Avoid jumbled queries that cram many unrelated keywords into a single query, for example "paypal invoice payment delivery payments ordering".
- Avoid OR-separated queries such as "paypal invoice OR paypal create invoice OR paypal OR invoice creation".
- If you need to explore multiple intents, try each as a separate call.