Tools API · web search
Search the web with a dedicated tool key and normalized results.
/v1/serp/searchtapi.17.wtfUse a tool key
Open Tools Studio, select SERP, and create a tool key. Set it as LM0_TOOL_API_KEY on your server. Requests go to tapi.17.wtf, using Bearer authentication or x-api-key. A model API key returns 403. Available package credits are required. The currently implemented operation is GET /v1/serp/search.
Query parameters
| Parameter | Type / requirement | Description |
|---|---|---|
q | string · required | Trimmed search query, 1–2048 characters. |
num | integer · optional | Results per page, clamped to 1–10; default 10. |
start | integer · optional | Result offset, clamped to 0–10,000; default 0. Page is floor(start / num) + 1. |
sort | string · optional | date or relevance. Other values normalize to relevance. |
gl | string · optional | Country hint; provider support varies. |
hl | string · optional | Language hint; provider support varies. |
proxy | boolean-like string · optional | true, 1, or yes enables proxy where supported. |
proxyCountry | string · optional | Two-letter proxy country code. |
raw | boolean-like string · optional | Provider hint; public response remains normalized. |
Example request
Use URL encoding for search terms. For the next page with num=10, use start=10.
curl --get https://tapi.17.wtf/v1/serp/search \
-H "Authorization: Bearer $LM0_TOOL_API_KEY" \
--data-urlencode "q=API gateway documentation" \
--data-urlencode "num=10" \
--data-urlencode "start=0"Response fields
Successful responses contain success, tool, operation, request_id, provider, credits_charged, and data.
data contains query, normalized params, meta (totals, page, perPage, searchTime), results, spelling, pagination, and providerMeta. Each result includes position, title, url, displayUrl, description, and optional date, image, thumbnail, site, metadata, and breadcrumbs. Optional fields can be null and metadata richness varies by provider. providerMeta.fallbackUsed indicates fallback.
Response headers include x-request-id, x-lm0-tool, and x-lm0-credits-charged. Errors use success: false, request_id, and error.code / error.message.
Cost, fallback & limits
Successful operations charge the configured per-call price from your shared package balance. Failed execution releases the reservation and records zero billed credits. See Tools Studio for current pricing. The tools API currently allows 150 requests per minute per key. The service can fall back to configured backup providers after eligible upstream failures; search hints may behave differently across providers.