Scrape Website
Coming soon. This endpoint isn’t available yet. Calls to it won’t work until it launches.
The Website Scraping API fetches a company’s homepage and returns it as structured JSON.
Pass a domain such as acme.com. A full URL is reduced to its host, so https://www.acme.com/about becomes acme.com. The homepage is always the page fetched.
What comes back:
- Title, description, and Open Graph text
- H1–H3 headings
- Navigation and footer links
- Key pages: contact, about, pricing, careers, demo, blog, docs, privacy, terms, login, and signup. Each is a URL or
null, never guessed. - Emails and phone numbers found on the page
- Social profiles
- Detected technologies
- A text excerpt of the visible copy, and counts
It never returns raw HTML or images.
Use this endpoint to:
- Qualify accounts from what their website says
- Find contact, pricing, careers, and demo pages
- Detect the technologies a company uses
Cost:
Each domain served costs 1 scrape token, whether it’s fetched now or served from the 30-day cache. Scrape tokens are a separate balance from regular tokens. See get_billing.
Outcomes:
- A site that blocks the direct fetch may first return
status: "pending"withretry_after_seconds. Ask again after that delay. - A domain with no data returns HTTP
200withstatus: "not_found". pendingandnot_foundcost nothing. Readstatus, not the HTTP code, to tell a hit from a miss.
Authorizations
Pass your API key as a Bearer token. Keys follow the format ms_XXXXXXXXXXX.
Headers
Identifies the calling client. Any non-empty value is accepted — MoltSets does not validate its contents. Requests without this header are rejected with 403 Forbidden (error.code: forbidden).
Body
The company's domain, e.g. acme.com. A full URL such as https://www.acme.com/about is reduced to acme.com. The homepage is fetched.
"acme.com"
Response
Success — status is ok, pending, or not_found. The full response schema will be published at launch.
