API Reference

Endpoint: POST https://api.lcr.net/contents

Auth: Send your API key as a Bearer token: Authorization: Bearer <api-key>. Get a key at app.lcr.net.

The Contents API turns any public URL into clean, structured, LLM-ready data in real time, at scale, powered by the Grass network.

Request parameters

Text options

Output size & truncation

Every result field — html, markdown, and text — is truncated to maxCharacters, which defaults to 20,000. To return a whole large page (for example full HTML), raise the limit and, for text, ask for the full body:

{
  "urls": ["https://example.com"],
  "text": { "verbosity": "full", "maxCharacters": 200000 }
}

html and markdown always cover the full page up to maxCharacters. Passing text: false omits only text.

Response schema

{
  "requestId": "e492118ccdedcba5088bfc4357a8a125",
  "results": [
    {
      "title": "Page Title",
      "url": "https://example.com/page",
      "id": "7668765c-2b66-4c50-b1ff-8c4bed8500c3",
      "publishedDate": "2024-01-15T00:00:00.000Z",
      "author": "Author Name",
      "image": "https://example.com/image.png",
      "favicon": "https://example.com/favicon.ico",
      "html": "Full page content as html...",
      "text": "Full page content as text...",
      "markdown": "Full page content as markdown..."
    }
  ],
  "statuses": [
    {
      "id": "7668765c-2b66-4c50-b1ff-8c4bed8500c3",
      "status": "success",
      "source": "livecrawled",
      "httpStatusCode": 200,
      "strategy": "fast",
      "credits": 1
    }
  ],
  "searchTime": 1301
}

Top-level fields

results[]

Only present for URLs that were successfully fetched.

statuses[]

One entry per requested URL, regardless of success or failure.

statuses[].source values

Only meaningful on success entries.

statuses[].strategy values

The strategy field records the fetch tier resolved or attempted for the URL.

A blocked URL does not produce a status entry: policy rejections fail the whole request with HTTP 451 (see Blocked content).

statuses[].credits values

Credits reflect the fetch strategy used for the URL.

Error handling

The endpoint returns HTTP 200 even when individual URLs fail. Per-URL errors appear in the statuses array.

On error, statuses[].error includes:

Request-level errors

These apply to the request as a whole, not individual URLs.

Blocked content

The API does not fetch disallowed content. When any requested URL is blocked, the whole request is rejected with HTTP 451 (CRAWL_WEBSITE_NOT_PERMITTED): no per-URL statuses entry is produced and no credits are charged.

Prohibited Categories

We strictly enforce access restrictions on the following domain types:

• Government & Military Entities: .gov, .mil, and state/national official administrative portals.
• Gambling & Betting Sites: Online casinos, sportsbooks, lotteries, and betting exchanges.
• Illicit & Illegal Content: Platforms hosting illegal goods, dangerous materials, pirated intellectual property, or explicit/exploitative media.
• Google Search & Redirect URLs: Search result and redirect pages.
• Cryptocurrency Mining: Mining pools and related sites.
• Banking & Payment Sites: Banks, payment processors, and financial institutions.

Categories are policy-driven and may change. Blocked attempts are logged for abuse monitoring.

Response Code: 451 Unavailable For Legal Reasons

If a request targets a restricted or blacklisted domain, our API returns an HTTP 451 error status.

Example Error Response

{
  "message": "website not permitted",
  "timestamp": "2026-01-01T00:00:00.000Z",
  "path": "/contents"
}

Rate limiting

Our API enforces rate limits to ensure stability and consistent service across all accounts.

The LCR Contents API enforces rate limits based on your subscription plan. Each plan has a maximum number of requests per second (RPS).

If you exceed your plan's rate limit, the API returns a 429 Throttle Exception response.

Note: Your rate limit is determined by your active subscription plan.

• Higher Concurrency: Need greater throughput? Higher dedicated concurrency limits and custom RPS caps are available upon request for enterprise workloads.

Need higher limits? Contact our support team or your account manager to request a concurrency upgrade.