MCP & API
AdsCrawl for HTTP API
Call AdsCrawl from any server-side HTTP client. Use the REST API for rendered content, PNG screenshots and remote browser sessions without adopting a language SDK.
What you can do
Rendered web content
Read JavaScript-rendered pages as Markdown, HTML or structured article JSON.
Page screenshots
Capture a viewport or full page through the screenshot API.
Browser workflows
Use Remote CDP for navigation, clicks and form input across multiple steps.
Before you start
- An AdsCrawl account and API key.
- cURL for this example, or your preferred server-side HTTP client.
- Set ADSCRAWL_API_KEY in the environment of the process running your client. Keep it out of browser code and source control.
SETUP METHOD 01
HTTP API
Send JSON requests with your API key in the x-api-key header.
Prepare the key
Set ADSCRAWL_API_KEY in the environment of the process running your client. Keep it out of browser code and source control.
Request rendered Markdown
POST /html with contentMode set to markdown. This example saves the response as page.md.
curl --fail-with-body -sS https://api.adscrawl.net/html \ -H "content-type: application/json" \ -H "x-api-key: $ADSCRAWL_API_KEY" \ -d '{"url":"https://example.com","contentMode":"markdown"}' \ --output page.mdCheck the result
Open page.md and look for Example Domain. Check the HTTP status before parsing other response types. Use POST /screenshot for PNG data and POST /cdp/sessions for interactive work.
Usage & limits
- API requests and browser sessions use your AdsCrawl account credits. Installing a client does not include a separate usage allowance.
- Close remote sessions after use. A disconnected client or closed viewer does not confirm that the server-side session has stopped.
- Choose timeouts and retries per endpoint. A local timeout does not prove that remote work has stopped.