# PDF Text Intake Auditor (`nexgenwatch/pdf-text-intake-auditor`) Actor

Judges whether a PDF is ingestible before you spend on extraction: text-layer presence, page count, encryption, scan likelihood, per-page text density, metadata, a SHA-256, and a READY\_FOR\_RAG / NEEDS\_OCR / REJECT verdict. You supply the PDFs (base64 or key-value-store keys).

- **URL**: https://apify.com/nexgenwatch/pdf-text-intake-auditor.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 pdf intake checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## PDF Text Intake Auditor

Judges whether a PDF is ingestible before you spend on extraction: text-layer presence, page count, encryption, scan likelihood, per-page text density, metadata, a SHA-256, and a READY\_FOR\_RAG / NEEDS\_OCR / REJECT verdict.

### What you submit

`files` — pdf files (base64 or key-value-store keys). Locally-supplied PDFs — each item is a base64 data string (optionally a data: URL) or a key naming an entry in the run's key-value store. Per file: text-layer presence, page count, encryption, scan likelihood, per-page text density, document metadata, SHA-256, warnings, and a READY\_FOR\_RAG / NEEDS\_OCR / REJECT verdict. A completed verdict bills; an unreadable/oversized/rejected file is delivered unbilled. Untrusted-file guards: size + page caps, decompression-bomb guard, no macro/JS execution.

### Untrusted-file guards

Inputs are treated as untrusted: a byte-size cap (decompression-bomb guard) rejects oversized files before parsing, a page cap bounds inspection, and embedded JavaScript / auto-actions are **reported as warnings, never executed**. Files are inspected, not run.

### Output & billing

One row per target. A complete evidenced verdict carries `outcome: answer` and is the only billable outcome; blocked / unreachable / unparseable / rejected targets carry that status and are not billed (push-then-charge — failures can only undercharge).

### Pricing

| Event | Price (USD) | When it fires |
| --- | --- | --- |
| `apify-actor-start` | $0.02 | once when the run starts (reserved; never charged in code) |
| `pdf_intake_check` | $0.05 | once per **complete evidenced verdict** delivered (blocked / unreachable / unparseable / rejected never bill) |

Volume tiers reduce the per-verdict price as usage grows: $0.05 → $0.045 → $0.04 → $0.0335.

### Why this and not the obvious alternative

a per-file RAG-readiness intake VERDICT with a content hash and OCR-need call — not a PDF-to-text dump; it judges whether a document is ingestible before you spend on extraction.

# Actor input Schema

## `files` (type: `array`):

Locally-supplied PDFs — each item is a base64 data string (optionally a data: URL) or a key naming an entry in the run's key-value store. Per file: text-layer presence, page count, encryption, scan likelihood, per-page text density, document metadata, SHA-256, warnings, and a READY\_FOR\_RAG / NEEDS\_OCR / REJECT verdict. A completed verdict bills; an unreadable/oversized/rejected file is delivered unbilled. Untrusted-file guards: size + page caps, decompression-bomb guard, no macro/JS execution.

## `maxBytes` (type: `integer`):

Reject files larger than this (decompression-bomb guard).

## `maxPages` (type: `integer`):

Cap pages walked for density.

## `userAgent` (type: `string`):

Override the transparent crawler UA.

## Actor input object example

```json
{
  "files": [
    "JVBERi0xLjQK...(base64 of a small PDF)"
  ],
  "maxBytes": 26214400,
  "maxPages": 300,
  "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "files": [
        "JVBERi0xLjQK...(base64 of a small PDF)"
    ],
    "maxBytes": 26214400,
    "maxPages": 300,
    "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/pdf-text-intake-auditor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "files": ["JVBERi0xLjQK...(base64 of a small PDF)"],
    "maxBytes": 26214400,
    "maxPages": 300,
    "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)",
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/pdf-text-intake-auditor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "files": [
    "JVBERi0xLjQK...(base64 of a small PDF)"
  ],
  "maxBytes": 26214400,
  "maxPages": 300,
  "userAgent": "Mozilla/5.0 (compatible; NexGenWatchBot/1.0; +https://apify.com/nexgenwatch)"
}' |
apify call nexgenwatch/pdf-text-intake-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/pdf-text-intake-auditor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/VjhC5xtrlRmUsjxbJ/builds/9Y9dd60hBKML32Zb7/openapi.json