Private beta. Discover 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/discover` is a sitemap crawler API that lists a website's
URLs the cheap way: an HTTP-first crawl plus sitemap parsing, with an
optional JavaScript render fallback for single-page apps. There is no
screenshot, no PDF, and no stored artifact. It returns a flat,
de-duplicated list of URLs and a count of where each one came from,
synchronously in a single call. It will be the lightweight "map the site"
primitive: point it at a domain, get back the pages
worth processing, then feed that list into
[the perceive endpoint](/docs/endpoints/perceive.md) or a crawl-mode ingest job.
Here is the smallest useful call. Send a URL, get its map back:
```bash
curl -X POST https://api.enconvert.com/v2/discover \
-H "X-API-Key: sk_your_private_key" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com"
}'
```
The response is a plain URL list with provenance counters. There are no
signed URLs, no operation ID, and no polling:
```json
{
"url": "https://example.com",
"mode": "hybrid",
"total": 47,
"urls": [
"https://example.com/",
"https://example.com/pricing",
"https://example.com/docs",
"https://example.com/blog/launch"
],
"pages_crawled": 12,
"truncated": false,
"robots_respected": false,
"sources": {"sitemap": 42, "crawl": 30},
"warnings": []
}
```
---
## Endpoints
| Method | Path | Purpose |
|--------|------|---------|
| `POST` | `/v2/discover` | Map a site's URLs over HTTP only and return a flat list with source counts. |
`/v2/discover` exposes a single path. It is stateless: there is no
operation row to re-fetch and no job to poll, so there is no companion
`GET` endpoint the way [perceive has one](/docs/endpoints/perceive.md).
**Content-Type:** `application/json` on the `POST`.
---
## 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