Content-Type & Charset Auditor

Audit public URLs for Content-Type correctness, charset declarations, MIME sniffing protection, HTTPS delivery, and common response metadata problems.

Why use this Actor

API and web teams need recurring MIME and response-contract validation because wrong Content-Type or charset declarations silently break clients, browsers and crawlers.

Key features

• Buyer-native inputs aligned to content type contract.
• Predictable structured output in the default Apify Dataset.
• Pay Per Event pricing tied to measurable result rows or reports.
• Optional MCP connector delivery for downstream automation and AI agents.

Quick start

Start with this working example and replace the target values with your own:

{
  "urls": [
    "https://example.com",
    "https://www.python.org"
  ]
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• urls — URLs: Configure URLs for this Actor run.
• expectedKind — Expected content kind: Configure Expected content kind for this Actor run.
• previousSnapshots — Previous response snapshots: Configure Previous response snapshots for this Actor run.
• failRunOnMismatch — Fail on MIME/contract mismatch: Configure Fail on MIME/contract mismatch for this Actor run.
• maxUrls — Maximum URLs: Configure Maximum URLs for this Actor run.
• concurrency — Concurrency: Maximum URLs audited in parallel.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include dataset.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.001000 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Detailed documentation

Validate response MIME metadata against lightweight observed content signatures and track response-contract drift.

Why use this Actor

Incorrect Content-Type or charset declarations can break API clients, browser rendering, downloads, crawlers, integrations, and security assumptions. Header presence alone is not always enough: a server can claim JSON while returning HTML, a proxy can remove nosniff, or a deployment can silently change response metadata. This Actor combines declared MIME evidence with bounded content-signature checks, expected-kind validation, and reusable snapshots so release and monitoring workflows can detect those failures deterministically.

Key features

• Parses Content-Type media type and charset.
• Checks X-Content-Type-Options nosniff and HTTPS delivery.
• Performs bounded signature detection for HTML, JSON, XML, common images, PDF, text, and binary responses.
• Flags declared MIME type mismatches against observed content.
• Supports an expected content kind for release or API contract validation.
• Captures Content-Disposition as part of the response metadata snapshot.
• Emits a normalized response-contract snapshot and fingerprint.
• Compares previous snapshots and reports drift/regression evidence.
• Supports fail-after-evidence behavior for automated mismatch gates.

Input

Provide urls. expectedKind can be auto, html, json, xml, text, image, or pdf. previousSnapshots enables drift detection. failRunOnMismatch can turn the Actor into a CI gate after evidence is written. maxUrls bounds batch size.

Output

Each result contains the final URL, status, score, raw Content-Type, declared kind, sniffed kind, expected kind, mismatch flag, charset, nosniff state, HTTPS state, Content-Disposition, response fingerprint, changed fields, regression state, issue codes, and an agentAction.

Example

{
  "urls": ["https://example.com"],
  "expectedKind": "html",
  "previousSnapshots": {},
  "failRunOnMismatch": false
}

Use cases

• API response contract QA.
• CDN and reverse-proxy migration checks.
• Browser MIME-hardening reviews.
• Static asset validation.
• Technical SEO response checks.
• Scheduled response-metadata drift monitoring.

Pricing

Billing is pay per audited URL result. The Actor uses bounded direct HTTP requests and requires no paid API or external AI model.

Limitations

Content sniffing is intentionally heuristic and bounded; it is not a full file-format parser. Compressed, encrypted, streaming, or proprietary formats may be classified conservatively. Authenticated/private endpoints are outside scope.

Privacy and permissions

Only bounded content from public HTTP(S) responses is inspected. Private and reserved network targets are rejected before requests are made.

Input reliability — 25 October 2026

Target lists are validated before network work, trimmed and deduplicated. Empty lists and malformed baselines are rejected rather than silently auditing a default website. Exact duplicate targets produce one result. Existing output fields and prices are preserved.