Treg People Search API Guide: Features, Integration & Examples

1. Treg overview

Public Treg materials position Treg as “OpenRouter for agent tools”: one catalog token for many external APIs (enrichment, SEO, social, scraping, and more), with server-side credential injection.

Treg people search is the lead-enrichment surface in that catalog. This article explains how developers reach a supported slice of that capability through jevtypesafe.org — an independent prepaid host, not the official Treg product.

2. People Search API on this host

The hosted People Search API finds a work email when upstream succeeds (optional verify in the same call). Inputs: full_name + company domain, and/or linkedin_url.

Response shape: upstream data plus host usage (credits_charged, retail_usd, remaining_tokens, treg_call_id). Upstream COGS is never returned to clients.

Product landing: People Search API.

3. How the API works

• Developer authenticates with Authorization: Bearer jv_live_…
• This host validates the key and prepaid balance
• Eligible calls relay to Treg’s routed treg.people.email.find
• Successful calls debit prepaid credits on this host (see usage in the response)
• Upstream $0 (for example many misses) → $0 debit here

4. Integration examples

Minimal curl against production. Replace the key placeholder; never commit real keys.

curl https://jevtypesafe.org/api/v1/people/email/find \
  -H "Authorization: Bearer jv_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"full_name":"Jane Doe","domain":"acme.com","verify":true}'

More languages and error codes: People Search API documentation.

5. How to access via Jev prepaid accounts

Create an account on this host, top up prepaid packs if needed, create a jv_live_ key, then call the endpoint. Decide (/api/v1/decide) and People Search share the same balance.

We do not hand out raw Treg tokens. Optional ICP gating with Jev decide remains a separate call in your agent workflow.

Get a key: API key guide.

6. Pricing explanation

Treg’s catalog side is described publicly as provider-rate metering with 0% Treg markup. On jevtypesafe.org, People Search is billed from your prepaid balance — see the live landing, docs, and each response’s usage fields.

Packs and token math live on the Pricing page. Failed auth or validation does not invent upstream charges.

See Pricing and the People Search landing for billing notes.

7. FAQ

• Is this the official Treg API? No — independent host with Treg-powered enrichment routing.
• Can I download model weights? Not applicable; this is an enrichment API path, not a downloadable people-search model.
• Does a miss always cost money? If upstream reports zero cost, this host does not debit credits for that call.
• Where are rate limits? Subject to prepaid balance and host abuse controls; upstream outages map to a safe people_upstream error.