메뉴
Use Explee Search APIs to find companies and people with natural-language targeting and optional AI scoring. USE WHEN finding accounts, prospects, or converting an ICP to filters.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
| name | Explee Search |
| description | Use Explee Search APIs to find companies and people with natural-language targeting and optional AI scoring. USE WHEN finding accounts, prospects, or converting an ICP to filters. |
Use this skill for lead generation, ICP targeting, account research, and people discovery.
Auth & endpoints: see explee-api-core. These are all POST calls (template T3) with
X-API-Key; cookie mode via explee-auth-cookie. The orchestrator / Worker selects cookie-first
with key fallback.
POST /public/api/v1/search/nl-to-filters — natural language → filtersPOST /public/api/v1/search/companiesPOST /public/api/v1/search/companies-by-domainsPOST /public/api/v1/search/peoplePOST /public/api/v1/search/people-by-domainsnl-to-filters first.Wrap any call in template T3 from explee-api-core.
nl-to-filters — natural-language ICP → structured filters. The body field is query
(verified against the live API; {"definition": …} here returns HTTP 422):
{"query":"B2B fintech in Europe hiring SDRs"}
It returns { "focus": "companies"|"people", "companies_filters": {…}, "people_filters": {…} }.
Feed those returned *_filters objects into the search endpoints below.
companies / people — pass the companies_filters / people_filters object from
nl-to-filters. The exact accepted field set isn't pinned here — confirm against
https://api.explee.com/public/api/docs before a paid run.
Shared reference for all Explee skills: base URL, full endpoint catalog, API-key authentication, canonical curl templates, and shared error/retry/guardrail rules. Other Explee skills reference this instead of repeating boilerplate.
Cookie/session and EXPLEE_SECRETS KV credential model for Explee: build the Cookie header, the cookie-first/key-fallback rule, and the cookie-vs-tracking-param pitfalls. USE WHEN setting up or refreshing Explee auth. Endpoints and API-key auth: see explee-api-core.
Orchestrate an end-to-end AutoGTM flow: ICP query → account/person discovery → enrichment → prioritized outreach list. USE WHEN building a full GTM pipeline from a natural-language objective.
Route user intent to the correct Explee product skill (Search, Enrichment, Agents, AutoGTM), using cookie-first auth with API-key fallback. USE WHEN a user has an Explee task but hasn't named the specific product.
Run Explee pre-built and custom AI agents, then poll run status and return structured outputs. USE WHEN running agent workflows for extraction, reasoning, or automation.
Use Explee enrichment APIs to find emails for contacts in single or batch mode and track async task status. USE WHEN completing outreach data or finding/verifying work emails.