# Built-Hidden Asset Finder (`z3n_m4nt1s/built-hidden-asset-finder`) Actor

Compare a file manifest or packaged project tree against its docs to surface built-but-undocumented scripts, pages, configs, and modules.

- **URL**: https://apify.com/z3n\_m4nt1s/built-hidden-asset-finder.md
- **Developed by:** [theCR8Fconclave SYST3MS](https://apify.com/z3n_m4nt1s) (community)
- **Categories:** Developer tools, AI, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.25 / actor start

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/platform/actors/running/actors-in-store#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

## Built-Hidden Asset Finder

Compare a supplied file manifest or packaged project tree against its documentation to find scripts, pages, configs, and modules that exist but are not represented in the docs.

### Portable Apify input

Supply `path` and `content` records. Markdown files and records under `docsPath` form the documentation corpus.

```json
{
  "files": [
    {"path": "docs/README.md", "content": "This repo documents the public API."},
    {"path": "public-api.js", "content": "console.log('claimed')"},
    {"path": "scripts/worker.py", "content": "print('built but undocumented')"}
  ],
  "docsPath": "docs",
  "maxFiles": 5000
}
```

For a prepared image or local run, omit `files` and provide `rootPath` instead. The verified synthetic manifest is in `examples/sample-input.json`.

### What it returns

Each default-dataset item contains:

- relative file path
- broad file kind
- whether the normalized file token appears in documentation
- hidden score
- normalized token used for comparison

`OUTPUT.json` also records the scan root/input mode, scanned-file count, hidden-file count, and all result items.

### Use cases

- AI-built repo verification
- stale README and handoff checks
- inherited-project inventory
- technical diligence preparation
- rebuild-prevention checks

### Interpretation boundary

This is a fast filename-to-documentation comparison, not semantic code understanding. A result means “present but not named in the supplied docs,” not “malicious,” “unused,” or “secret.” Review findings before acting.

### Output links

The run output exposes the default dataset plus `OUTPUT.json` in the default key-value store. Schemas live in `.actor/output_schema.json` and `.actor/dataset_schema.json`.

# Actor input Schema

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

Portable input for Apify runs. Supply path/content records from a repo or project; markdown records are treated as documentation.

## `rootPath` (type: `string`):

Optional local/container folder to scan when files are already packaged with the Actor. Ignored when file manifest is supplied.

## `docsPath` (type: `string`):

Optional docs folder/file to compare against.

## `maxFiles` (type: `integer`):

Maximum files to inspect.

## Actor input object example

```json
{
  "files": [
    {
      "path": "docs/README.md",
      "content": "This repo documents the public API only."
    },
    {
      "path": "public-api.js",
      "content": "console.log(\"claimed\")"
    },
    {
      "path": "scripts/secret-worker.py",
      "content": "print(\"built but undocumented\")"
    }
  ],
  "rootPath": ".",
  "docsPath": "",
  "maxFiles": 5000
}
```

# Actor output Schema

## `dataset` (type: `string`):

Structured result items from this run.

## `output` (type: `string`):

Run summary and all result items in the default key-value store.

# 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": [
        {
            "path": "docs/README.md",
            "content": "This repo documents the public API only."
        },
        {
            "path": "public-api.js",
            "content": "console.log(\"claimed\")"
        },
        {
            "path": "scripts/secret-worker.py",
            "content": "print(\"built but undocumented\")"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("z3n_m4nt1s/built-hidden-asset-finder").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": [
        {
            "path": "docs/README.md",
            "content": "This repo documents the public API only.",
        },
        {
            "path": "public-api.js",
            "content": "console.log(\"claimed\")",
        },
        {
            "path": "scripts/secret-worker.py",
            "content": "print(\"built but undocumented\")",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("z3n_m4nt1s/built-hidden-asset-finder").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": [
    {
      "path": "docs/README.md",
      "content": "This repo documents the public API only."
    },
    {
      "path": "public-api.js",
      "content": "console.log(\\"claimed\\")"
    },
    {
      "path": "scripts/secret-worker.py",
      "content": "print(\\"built but undocumented\\")"
    }
  ]
}' |
apify call z3n_m4nt1s/built-hidden-asset-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,z3n_m4nt1s/built-hidden-asset-finder"
        }
    }
}

```

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/XWPtD0jxccGJmq4K9/builds/WzZxEhwehYZ7gAB1c/openapi.json