# Inspect IIIF Cookbook dependency fields

**Use case:** 

Inspect bounded manifest/resource observations for the IIIF Cookbook rights recipe and example.org viewer origin. This fetches changing public sources and is not a free demo. Complete useful reports cost $0.05. Post-run data access may cost extra. Run for full dataset JSON or OUTPUT. Coverage does not prove healthy resources, browser rendering or full conformance.

## Input

```json
{
  "manifestUrl": "https://iiif.io/api/cookbook/recipe/0008-rights/manifest.json",
  "viewerOrigin": "https://example.org"
}
```

## Output

```json
{
  "observedAt": {
    "label": "Observedat",
    "format": "string"
  },
  "manifestUrl": {
    "label": "Manifesturl",
    "format": "string"
  },
  "coverage": {
    "label": "Coverage",
    "format": "string"
  },
  "resources": {
    "label": "Resources",
    "format": "array"
  },
  "findings": {
    "label": "Findings",
    "format": "array"
  },
  "requestCount": {
    "label": "Requestcount",
    "format": "integer"
  },
  "byteCount": {
    "label": "Bytecount",
    "format": "integer"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The IIIF Publication Preflight Actor is ready to run with the inputs already set for "Inspect IIIF Cookbook dependency fields". [Sign up or log in](https://console.apify.com/create-task-from-example/itOi458wAwhFiToUF) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Inspect IIIF Cookbook dependency fields" task

The IIIF Publication Preflight Actor will start running based on the input automatically. You can also change all the input fields, like public manifest url and optional viewer origin, to match your specific use case.

### 3. Receive the "Inspect IIIF Cookbook dependency fields" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as observedat, manifesturl, coverage, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Inspect IIIF Cookbook dependency fields" task via API](https://apify.com/l3digital/iiif-publication-preflight.md).

## About this Actor

This example demonstrates how to use [IIIF Publication Preflight](https://apify.com/l3digital/iiif-publication-preflight.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/l3digital/iiif-publication-preflight.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/l3digital/iiif-publication-preflight.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).