Private beta. Lookup is callable today with your normal API key, on every plan including Founding, and it draws on your monthly ops allowance like any other call. It is not announced or generally available: the request and response shapes can change without notice, and there is no stability or support commitment, so do not build anything load-bearing on it yet. The roadmap is on
Coming Soon, and every release is announced in
the changelog.
`POST /v2/lookup` is a web search API built for LLM agents: it runs a
search in one of six categories and hands back a flat, provider-neutral
result list. Set `perceive_top` and it also renders the top-N result URLs
in a real browser, so an agent gets the search-engine results page (SERP)
*and* the page content behind each hit in a single round trip. As a SERP
API alternative it collapses the usual stack (hit a search API, parse its
results, then fan out a scraper) into one call. It will be EnConvert's
answer to Firecrawl `/search`.
Serper is the search provider behind it. The request and response speak
a neutral search vocabulary (`category`, `country`, `locale`,
`time_filter`), so a future provider swap does not change the contract
you code against.
Here is the smallest useful call. Send a query, get the top web results
back:
```bash
curl -X POST https://api.enconvert.com/v2/lookup \
-H "X-API-Key: sk_your_private_key" \
-H "Content-Type: application/json" \
-d '{
"query": "headless chrome pdf rendering"
}'
```
The response is a flat result list plus provenance for support
correlation:
```json
{
"lookup_id": 81423,
"query": "headless chrome pdf rendering",
"category": "web",
"total": 10,
"results": [
{
"title": "Generate PDFs with headless Chrome",
"url": "https://example.com/guide/chrome-pdf",
"snippet": "Render a page and print it to PDF...",
"position": 1
},
{
"title": "Print to PDF with the Chrome DevTools Protocol",
"url": "https://example.dev/cdp/print-to-pdf",
"snippet": "Page.printToPDF returns base64 PDF data...",
"position": 2
}
],
"perceive_top": 0,
"perceive_operation_ids": [],
"credits": 1,
"cost_cents": 0.06,
"warnings": []
}
```
---
## Endpoints
| Method | Path | Purpose |
|--------|------|---------|
| `POST` | `/v2/lookup` | Run one search and, optionally, auto-perceive the top-N result URLs. |
`/v2/lookup` is a single-call endpoint with no separate status or
retrieval path. When you auto-perceive, each rendered page becomes a
first-class [perceive](/docs/endpoints/perceive.md) operation with its own
`operation_id`, which you can re-fetch later through
`GET /v2/perceive/{operation_id}`.
**Content-Type:** `application/json`.
---
## Authentication
Authenticate with a private key in the `X-API-Key` header for
server-to-server calls. This is the path the examples below use.
```http
X-API-Key: sk_your_private_key
```
Public keys with a JWT bearer token also work, using the same flow as
every other endpoint: generate a token with your `pk_` key, then send it
as `Authorization: Bearer