Enterprise · For teams
Enterprise data access for teams.
Four layers, one brief. Start with the layer your team needs first. The documents a procurement team asks for are published for the whole platform, and a pilot runs before any order.
Choose the layer
Four layers, each with its own product page.
Proxies give your team the exit: residential, mobile, ISP, datacenter and IPv6. Enterprise proxies.
The SERP API returns parsed search results for 17 verticals. Enterprise SERP API.
The web scraping API returns clean Markdown from a page, behind the Web Unlocker access layer. Enterprise web scraping API.
Collectors run ready-made scrapers, datasets ship ready-made or custom lists. Enterprise collectors and datasets.
For procurement
What your team can review before the first order
Data Processing Agreement. The DPA sets roles, data categories and audit rights (section 9). It is published at /dpa/.
Sub-processors. Categories of sub-processors, with purpose and location, are published at /subprocessors/. The named list is sent under a DPA on request.
Billing agreement. For card charges, applicable taxes such as VAT are added where required and shown on the invoice. See /billing-agreement/.
Acceptable Use Policy. What is allowed and what is not, in one page: /aup/.
KYC and Sanctions Policy. When we ask for identity checks, including for unusually large orders: /kyc/.
Pilot before the order. Five ready-made pilots. A free sample within two working days and a quote within 24 hours of your check. The pass criterion is written before the pilot starts: /pilot/.
How a first project starts
Three steps, in writing.
1. Send the brief: sources, markets, the output you need and how often. Use the enterprise brief form.
2. Run a pilot with a pass criterion agreed up front. The sample comes within two working days; the quote within 24 hours of your check. See the pilot page.
3. Order, with the invoice and the taxes shown as in the billing agreement.
Before you brief us
Questions teams ask
Do you sign a Data Processing Agreement?
Yes. The DPA is published at /dpa/. It sets the roles, the categories of data and the audit rights.
Can we see your sub-processors before we buy?
The categories are published at /subprocessors/. The named list is sent under a DPA on request.
Do you offer a service level agreement?
Our commitments are the ones in the Terms of Service. If your procurement needs a different written commitment, put it in the brief and we answer in writing before the order.
Where do we start?
Send the brief through the enterprise form, or start with a pilot. Both lead to a written scope before any order.
Tell us what your team needs.
Send sources, markets, output and cadence. The enterprise team answers with a scope, or with the product that already fits.