Credit cost summary
Credits are deducted from the same balance as the app and the REST API. Paid runs are charged up front against a quoted ceiling and reconciled on completion — you are billed only for what was delivered, and unearned credits are refunded automatically.
Account and jobs (free)
enrichley_get_account_status
Your available credits and billing-cycle allowance. In Claude this renders as an account card with a Refresh button. Free — use it any time to check your balance or confirm the connection works.
“Check my Enrichley credit balance.”
enrichley_list_jobs
Recent jobs across People Search, Company Lookalike, Email Finder, and Email Validation, with their status.
“List my recent Enrichley jobs.”
enrichley_get_job_status
A single job’s status and progress. When a paid run reaches a terminal state, the status includes settled_credits — the amount actually kept after reconciliation, so you can see exactly what a run ended up costing.
For Company Lookalike, a completed run can also include partial: true. This boolean appears only when Enrichley has validated persisted evidence that the provider rate limit ended the batch early or that the provider had no more matching companies before the requested quantity was reached. The job remains completed, and its progress and settlement reflect what was actually delivered; counts, targets, and previews alone never create the partial signal. Check the discovery coverage before continuing: More available can be fetched in another run, while All available companies saved means provider exhaustion made coverage complete and there is nothing more to fetch.
“Check the status of that run and tell me the settled credits.”
enrichley_get_job_metadata
A bounded, safe summary of a job — which service, which search, and its headline numbers.
enrichley_get_result_schema
The column catalog for a service’s results, so your assistant knows what fields a download will contain.
enrichley_get_download_instructions
Download instructions for an already-paid People Search or Company Lookalike result set (up to 50,000 rows). Result rows never travel through the assistant — see Downloads below.
Discoveries (free)
A discovery is a saved search: its targeting can be previewed, refined, and eventually run. Your assistant can manage them for both services:“Create a lookalike search seeded from stripe.com, limited to Texas — look up the right state filter first.”
Once a discovery has been paid for, its targeting is locked — your assistant will be told to create a new discovery instead of editing the paid one.
null deletes it. The exclude object patches only its direct children, filters: null clears every filter, and an empty filter patch is rejected. This MCP update behavior does not change how other Enrichley access paths edit discoveries.
For industry filters, search by display name first, then use the returned canonical numeric NAICS code. Do not submit the industry display label directly. State and city lookup tools return their own canonical numeric IDs.
Previews (free)
enrichley_preview_company_lookalike
Runs a discovery’s saved targeting and returns a sample of matched companies with match scores, plus the total available. Always free. Preview companies stay locked until a paid run purchases them.
“Preview the stripe lookalike and tell me how many matches there are.”
enrichley_preview_people_search
Runs a discovery’s saved targeting and saves a sample of up to 10 people onto the discovery. Your plan includes 100 free previews per billing cycle, shared between the app and MCP; each preview reports how much of the allowance remains. Saved preview people accumulate on the discovery and are eligible for Email Finder later — free previews included.
Use the prepared run quote, not preview arithmetic, as authoritative for net paid availability: it applies the full saved/recent-repeat exclusion set of up to 300 entries, and the up-to-10 preview sample does not bound a material difference from the gross preview estimate. A material difference is not an arithmetic error and must not be adjusted using preview arithmetic. The prepared quote is shown unchanged, and you confirm both proposed_result_count and estimated_max_credits before the run starts.
enrichley_confirm_paid_people_search_preview
Offered only after the free preview allowance is exhausted. Reserves up to 10 credits, settles at 1 credit per person actually saved, and refunds the rest. Requires your explicit confirmation of the stated ceiling — it is never invoked on its own.
Paid runs: quote first, then confirm
Every paid run is a two-step flow. The prepare step is free and returns a quote stating the exact quantity, current availability, and a maximum credit ceiling. The run step executes only that unchanged quote after you explicitly confirm it.“Quote me 25 companies from the stripe lookalike.” → the assistant prepares a quote → you confirm → “Run it.”How the charge works: the run is charged up front against the confirmed ceiling, then reconciled when the job completes. You are billed only for what was actually delivered; everything else is refunded automatically.
enrichley_get_job_status reports the final settled_credits once the run is terminal.
Email Finder is all-or-nothing by design: it quotes the full population of saved people eligible for email search on a discovery — there is no “find 50 of them.” Contacts whose email is not found cost nothing. See Email Finder for how eligibility works.
The quote card in Claude
In Claude, prepare tools render an interactive quote card: the service, the search name, the quantity (with quick-pick chips and a free-form amount for People Search and Company Lookalike), an Update quote button that re-prices a changed quantity, and a Confirm run button showing the maximum credits. Confirming from the card starts the run directly.A run you confirm from the card starts immediately, but the confirmation happens outside the assistant’s view — so the assistant may not know the run exists. The card shows the run ID; mention it, and the assistant can pick up tracking from there. In clients without cards, the assistant quotes and confirms conversationally instead, and always requires your explicit confirmation before running.
Email validation (1 credit)
enrichley_validate_email
Validate a single email address — the same catch-all-aware validation as the REST API. Fixed price of 1 credit per call, so it charges without a quote step. It accepts exactly one address per call.
“Validate jane.doe@example.com.”
Catch-all and slow domains can take a while; if a validation times out, the assistant is told to retry shortly. Timed-out attempts that never validated are not billed as valid results.
Downloads
Paid People Search and Company Lookalike result sets are downloaded by you, never routed through the assistant — your data stays out of the conversation context.enrichley_get_download_instructions returns two paths, rendered as a card in Claude:
- Open in Enrichley — a button that opens the result set in the Enrichley app and starts the CSV export for you. If you’re asked to sign in, you’re returned to the export afterward.
- Terminal alternative — a
curlcommand using your API key (as the$ENRICHLEY_API_KEYenvironment variable — never paste the key into the chat) that streams the CSV directly to your machine.
The usage envelope
Every tool result includes a usage object so your assistant can pace requests:
The account-status and email-validation tools additionally report
creditsRemaining and creditsConsumed. Missing values are null, never 0.
Rate limits and pacing
Each service is paced independently. When a limit is reached, the tool reply says exactly how long to wait — “Enrichley tooling is temporarily rate limited. Retry in about N seconds.” — and your assistant is expected to wait that long before retrying. While waiting on a job, the assistant checks status at most three times per turn with increasing waits, then reports the last known state rather than polling forever.Errors
Failed calls keep the same envelope shape withok: false, an HTTP-style status, and a bounded error message. The MCP isError flag is set so your assistant can detect the failure and decide how to retry or report the issue.
Resources
The server publishes one static resource,enrichley://usage-guide — a markdown document covering credits, quotas, result meanings, and retry guidance. Most clients fetch it automatically the first time the Enrichley server is selected.
Clients that support interactive tool cards (MCP Apps) also receive four card resources: the account status card, the preview results table, the run quote card, and the download handoff card. Clients without card support get the same information as bounded text.