Agent-native

Built for agents, not only developers.

Agents read the docs, call MCP and wire the API. You add the key.

One prompt. Paste into any coding agent.

Read https://berrycrawl.com/llms.txt and https://docs.berrycrawl.com/docs/guides/agent-quickstart, then integrate Berrycrawl into this repository.

First inspect the repository's language, framework, server entry points, package manager, existing environment files, and test commands. Do not ask me to paste a secret into chat. Tell me to create a Berrycrawl API key in the dashboard and add this variable to the server-side environment file or secret store:

BERRYCRAWL_API_KEY=bc_...

Wait until that variable exists in the environment you will use. Then implement the smallest server-side integration for the feature I asked for. Use the endpoint and request shape from the Berrycrawl docs, keep the key out of browser bundles and source control, add a focused test or local verification path, and report the files changed and the command I can run to verify it.

If the feature starts a crawl or extraction job, persist the returned id and poll GET https://api.berrycrawl.com/api/v1/jobs/{id} until the status is COMPLETED, FAILED, or CANCELLED. Do not create a second job when polling a known id.

Read the agent quickstart

Agent-readable docs. Plain text and JSON at stable URLs.

$ curl -s https://berrycrawl.com/llms.txt

Open llms.txt

[ 05 / 07 ]Developers

Ship it in a few lines of code.

Typed SDKs in nine languages. One OpenAPI contract.

scrape.ts

$ npm i berrycrawl

import { Berrycrawl } from "berrycrawl";

const berrycrawl = new Berrycrawl({
  apiKey: process.env.BERRYCRAWL_API_KEY,
});

const page = await berrycrawl.scrape({
  url: "https://example.com/pricing",
  formats: ["markdown", "links"],
});

200 OK · response

{
  "success": true,
  "data": {
    "markdown": "# Pricing\n\nSimple plans for every team.",
    "links": ["https://example.com/signup"]
  },
  "metadata": {
    "url": "https://example.com/pricing",
    "statusCode": 200
  }
}

Testing? Scrapes and brand lookups of berrycrawl.com are free.

SDK docs API reference OpenAPI

Build the feature. Skip the crawler project.

100 free credits. No card required.

Get an API key Connect your agent

Read https://berrycrawl.com/llms.txt and https://docs.berrycrawl.com/docs/guides/agent-quickstart, then integrate Berrycrawl into this repository. First inspect the repository's language, framework, server entry points, package manager, existing environment files, and test commands. Do not ask me to paste a secret into chat. Tell me to create a Berrycrawl API key in the dashboard and add this variable to the server-side environment file or secret store: BERRYCRAWL_API_KEY=bc_... Wait until that variable exists in the environment you will use. Then implement the smallest server-side integration for the feature I asked for. Use the endpoint and request shape from the Berrycrawl docs, keep the key out of browser bundles and source control, add a focused test or local verification path, and report the files changed and the command I can run to verify it. If the feature starts a crawl or extraction job, persist the returned id and poll GET https://api.berrycrawl.com/api/v1/jobs/{id} until the status is COMPLETED, FAILED, or CANCELLED. Do not create a second job when polling a known id.

import { Berrycrawl } from "berrycrawl"; const berrycrawl = new Berrycrawl({ apiKey: process.env.BERRYCRAWL_API_KEY, }); const page = await berrycrawl.scrape({ url: "https://example.com/pricing", formats: ["markdown", "links"], });

{ "success": true, "data": { "markdown": "# Pricing\n\nSimple plans for every team.", "links": ["https://example.com/signup"] }, "metadata": { "url": "https://example.com/pricing", "statusCode": 200 } }