lev8 API

The lev8 API turns a natural-language objective into matching entities or a requested contact detail. It is designed for server-side products that need live-web people and business intelligence without building a search pipeline from scratch.

External API access is being rolled out in stages. Your lev8 contact will provide the API base URL and enable the entity and contact types available to your workspace.

Start with Entity Search

Send an objective to POST /v1/entity-search. Results arrive incrementally over Server-Sent Events (SSE), so your application can process each batch before the full search finishes.

curl --no-buffer "$LEV8_API_BASE_URL/v1/entity-search" \
  --request POST \
  --header "Content-Type: application/json" \
  --header "Accept: text/event-stream" \
  --header "x-api-key: $LEV8_API_KEY" \
  --header "Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000" \
  --data '{
    "entity_type": "company",
    "objective": "AI infrastructure startups in the United States founded since 2023",
    "limit": 20
  }'

Quickstart

Make your first streaming request and handle the result.

Authentication

Create, store, and rotate an API key safely.

Entity Search

Review request fields, entity types, and response behavior.

Contact Search

Find an email address or phone number with a JSON request.

Credit balance

Check the credits currently available to your API key’s billing account.

Errors

Handle HTTP errors and failures after an SSE stream starts.

API behavior at a glance

Authentication uses an x-api-key header. API keys are separate from user sessions and internal service credentials.
Every accepted search gets a lev8 request ID. Preserve it when contacting support.
Results stream as entity_search_batch events, followed by entity_search_done and [DONE].
POST /v1/contact-search returns one email or phone lookup as JSON after billing settles.
GET /v1/credit/balance reports the credits currently available for new requests.
Entity Search reserves credits up to the requested limit and settles against the number of unique returned entities. Contact Search reserves one lookup at the configured contact-type price.
Idempotency prevents duplicate execution and duplicate billing; the current API does not replay a previous SSE or JSON response.

Credit history and bucket-detail endpoints, SSE replay, and client-controlled API scopes are not part of the current public API.

Getting started

API reference

API behavior

Start with Entity Search

Quickstart

Authentication

Entity Search

Contact Search

Credit balance

Errors

API behavior at a glance

​Start with Entity Search

Quickstart

Authentication

Entity Search

Contact Search

Credit balance

Errors

​API behavior at a glance

Start with Entity Search

API behavior at a glance