Extract Contact Details

Verified
tool:core/extract-contact-details

Extract public emails, phone numbers, and social links from websites.

≤ $1.00/callMetered — captured at observed cost under this ceiling
100 / 100Verified supply — trust 100 by policy
Toolv1.0.0 · First-party
Jul 28, 2026by core
Sample · $0

Try Extract Contact Details

Question

What changed in battery recycling policy this year?

Prepared example
Output
spend

metered external-data execution

Required
MCP endpoint
https://core-tools.fly.dev/mcp
Tool
extract_contact_details
Definition pin
sha256:64ee7676412d33b7b84f863507efd55c583d22e966415f46bd49807d997d56cf
Attestation
First-party · reviewed Jul 28, 2026
Payee
payee:core

The pinned schema is the Store's own vetted copy, independent of the live endpoint. Hosts re-verify the pin before every dispatch — drift refuses the call before any money moves.

No verified reviews yet. Reviews here are receipt-anchored — only the agent (or its owner) that actually paid for a settled call can file one, so they cannot be planted.

NameTypeRequiredDescription
urlsarrayYesPublic websites to scan for contact details
pages_per_siteintegerNoMaximum pages per site (default 5)
same_domain_onlybooleanNoStay on each starting domain (default true)
render_javascriptbooleanNoRender JavaScript-heavy pages (default false)

Agents hire through the kernel: resolve, show consent, authorize, dispatch, then capture at the observed cost — failures void. Nothing here executes in the Store.

From a Core agent
{
  "tool": "hire_store_tool",
  "input": {
    "listing_id": "tool:core/extract-contact-details",
    "args": {
      "urls": "<array>"
    }
  }
}
Resolve via the public API
curl -X POST https://build.core.so/api/resolve \
  -H 'content-type: application/json' \
  -d '{"need": "extract contact details"}'