Search Public Endpoints

# Search Public Endpoints Describe your goal in `q`. Search returns matching public endpoints and evaluates what each one does, when to use it, and its limitations so the agent can select the best fit. ## Request `POST /v1/search` ```json { "q": "Get Current Weather" } ``` ```json { "q": "Add tracking details for an existing paypal order" } ``` `q` is required and capped at 512 characters. No other body field is accepted; unknown fields return `400`. **Query parameters** - `limit` — results per page (default 10, max 25) - `cursor` — pass `meta.nextCursor` from the previous response Pagination stops at 40 results total; a cursor past 40 is rejected. ## Response Each result carries `id`, `resourceType`, `name`, `description`, `method`, `url`, and `evaluateGuide`;. - `resourceType` — the kind of entity, for example `endpoint`. Pass it to `/v1/integrate` as the resource's `type`. - `evaluateGuide` — an evaluation of the endpoint in three parts: a brief summary, recommended use cases, and unsupported use cases or limitations. `meta` carries `q`, `total`, and `nextCursor` (absent on the last page). ## Idempotency Search is read-only and does not create or mutate data, so it is safe to retry. No idempotency key is required. Responses may still change between calls as the public catalog changes over time. ## Errors `400` invalid input, `429` rate limited, `500` server error.