# Dev Utilities Validator (`engineertsaistudio/dev-utilities-validator`) Actor

Deterministic validation and normalization for JSON Lines, file checksums, and SVG accessibility structure. Pay-per-event pricing, no AI wrapper, no scraping -- pure validation logic for developers and AI agents.

- **URL**: https://apify.com/engineertsaistudio/dev-utilities-validator.md
- **Developed by:** [Studio EngineerTsai](https://apify.com/engineertsaistudio) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 validation results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Dev Utilities Validator — Apify Actor (pay-per-event)

Deterministic validation and normalization for JSON Lines, file checksums, and SVG accessibility structure. Wraps the exact same real, tested logic already shipped as the `etsa-mcp-dev-utilities-001` MCP server (`dev_utilities_core.py`) — one proven capability, a second distribution manifestation, not a rewrite.

### Operations (`input.operation`)

- `jsonl_validate` — validate newline-delimited JSON text (`input.text`)
- `checksum_manifest` — SHA-256 manifest for explicit file paths (`input.paths`)
- `svg_viewbox_check` — structural/accessibility check of SVG markup (`input.markup`)

### Pricing (pay-per-event, configured live in the Apify Console's Publishing > Monetization wizard)

- `actor-start`: $0.01 — charged once the Actor validates input and starts
- `validation-result`: $0.02 — charged once per successful result
- Platform usage cost is included in the above prices, not passed through to the caller (verified on the real Review screen)

No rental, no per-compute-unit billing — matches Apify's 2026 pay-per-event migration (rental pricing being retired).

### Local testing (real, done)

Tested against the real, installed `apify` Python SDK (v4.0.1) in an isolated venv, using `APIFY_LOCAL_STORAGE_DIR` for local storage and `ACTOR_TEST_PAY_PER_EVENT=1` to exercise the real pay-per-event charging path locally (`Actor.charge()`) without a live platform account. All three operations produced correct, verified output:

- `jsonl_validate`: correct valid/blank/invalid counts and type breakdown
- `svg_viewbox_check`: correct PASS/FAIL and per-check breakdown
- `checksum_manifest`: correct SHA-256 digest, independently verified

### Deployed and public

Real, published, public Apify Actor: https://apify.com/engineertsaistudio/dev-utilities-validator (Actor ID `3EV4NAlqaqMV0TSfG`). Built (0.0.3), test-run succeeded against a live sample (2 valid records, 1 invalid line correctly reported), and pay-per-event monetization is Active. Payout/KYC completeness for real payouts is tracked separately and not implied by publication alone.

### Agentic payments

Pay-per-event Actors with limited permissions are eligible for Apify's agentic payment paths (x402 / Skyfire), meaning an AI agent — not just a human — could discover, run, and pay for this Actor once published. This is a first-class distribution rail for a deterministic, non-scraping tool like this one.

# Actor input Schema

## `operation` (type: `string`):

Which validation to run.

## `text` (type: `string`):

Required when operation is jsonl\_validate.

## `paths` (type: `array`):

Required when operation is checksum\_manifest. Paths must exist inside the Actor's run environment (e.g. supplied via a prior file-download step).

## `markup` (type: `string`):

Required when operation is svg\_viewbox\_check.

## Actor input object example

```json
{
  "operation": "jsonl_validate"
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("engineertsaistudio/dev-utilities-validator").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("engineertsaistudio/dev-utilities-validator").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 '{}' |
apify call engineertsaistudio/dev-utilities-validator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,engineertsaistudio/dev-utilities-validator"
        }
    }
}

```

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/3EV4NAlqaqMV0TSfG/builds/wsfAqJ1mIcO2eXKdF/openapi.json