# AI Agent URL & API Compatibility Checker (`havio_ai/ai-agent-url-compatibility-batch-profiler`) Actor

Check public URLs and API endpoints before AI agents, MCP tools, RAG pipelines, crawlers, or browser clients use them. Detect HTTP status, redirects, content type, TLS, CORS, and server/browser readiness in structured JSON.

- **URL**: https://apify.com/havio\_ai/ai-agent-url-compatibility-batch-profiler.md
- **Developed by:** [HAVIO AI](https://apify.com/havio_ai) (community)
- **Categories:** AI, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 url profiles

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

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 examples already wired to this Actor's own input schema, see the [API](#api) section below.

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`).

# README

### AI agent URL and API preflight checker

Validate public URLs and API endpoints before an AI agent, MCP tool, RAG pipeline, crawler, scraper, or browser client depends on them.

This Actor is designed for a simple decision: **can this public URL be used reliably by an automated system?**

It checks 1-100 public HTTP/HTTPS URLs and returns structured JSON with HTTP status, final URL, redirect chain, content type, TLS certificate state, CORS behavior, server-agent readiness, and browser-client readiness.

### When to use this Actor

Use this Actor when you need to:

- validate URLs before adding them to an AI agent or automation workflow
- check whether a public API endpoint is reachable and what format it returns
- preflight web sources before adding them to RAG or retrieval pipelines
- inspect redirect chains before a crawler, scraper, or agent follows a URL
- check TLS certificate validity and upcoming expiry risk
- check CORS behavior for browser-based AI clients
- distinguish server-side accessibility from browser-client compatibility
- batch-check up to 100 public URLs without using an LLM

Typical search intents include **AI agent URL checker**, **API preflight checker**, **URL compatibility checker**, **CORS checker**, **TLS/SSL checker**, **redirect checker**, **MCP URL validation**, and **RAG source validation**.

### What each URL result contains

Each processed URL produces one dataset item with fields such as:

- `requested_url` - original public URL
- `final_url` - final destination after redirects
- `http_status` - returned HTTP status code
- `content_type` and `format_hint` - HTML, JSON, XML, CSV, text, or other
- `redirect_count` and `redirect_chain` - redirect behavior
- `server_agent_readiness` - whether a server-side agent can use the URL directly
- `server_agent_reasons` - reasons for blocked or caution states
- `browser_client_readiness` - browser-client compatibility based on CORS behavior
- `browser_client_reasons` - reasons for browser compatibility warnings
- `tls` - TLS version, issuer, validity, hostname verification, and expiry information
- `cors` - Access-Control-Allow-Origin and related CORS metadata
- `evidence` - per-probe success indicators

Readiness values are intended as deterministic network diagnostics, not as a guarantee that a third-party service will remain available.

### Input

Provide `urls` as an array of 1-100 unique public HTTP/HTTPS URLs.

Example:

```json
{
  "urls": [
    "https://example.com",
    "https://jsonplaceholder.typicode.com/users"
  ]
}
```

### Output for AI, MCP, and automation workflows

Results are stored as one structured dataset item per processed URL. The Actor uses no LLM, so the output is deterministic and can be consumed directly by AI agents, MCP workflows, API clients, RAG ingestion pipelines, monitoring jobs, or custom automation.

A calling system can use the readiness fields to decide whether to continue, retry, use a browser-capable path, request authentication, or reject the URL.

### Safety and scope

- Public HTTP/HTTPS targets only
- localhost and private/non-public IP targets are rejected
- non-public DNS targets are rejected
- no authenticated browsing or credential handling
- no JavaScript browser rendering
- no LLM calls
- maximum 100 URLs per run

### Pricing

Pay per event: **$0.001 per completed URL profile**, plus the small Actor start event shown by Apify.

You are charged for completed `url-profile` events. The primary billable event is one completed public URL compatibility profile.

### Example use cases

#### Check URLs before an AI agent uses them

Batch-test candidate tools, APIs, documentation pages, or data sources before passing them to an autonomous agent.

#### Validate RAG and retrieval sources

Check whether retrieval URLs resolve successfully, return usable content types, and have stable TLS before ingestion.

#### Diagnose browser-agent failures

Compare server-side reachability with CORS-based browser-client readiness to identify why a URL works from a backend but fails from a browser application.

#### Preflight public API endpoints

Confirm status, redirects, JSON/content type, TLS, and CORS before integrating a public endpoint into an automated workflow.

# Actor input Schema

## `urls` (type: `array`):

Enter public HTTP/HTTPS URLs to profile.

## Actor input object example

```json
{
  "urls": [
    "https://example.com",
    "https://jsonplaceholder.typicode.com/users"
  ]
}
```

# Actor output Schema

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

One structured dataset item per processed public URL, including HTTP status, redirects, content type, TLS, CORS, server-agent readiness, and browser-client readiness.

# 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 = {
    "urls": [
        "https://example.com",
        "https://jsonplaceholder.typicode.com/users"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("havio_ai/ai-agent-url-compatibility-batch-profiler").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 = { "urls": [
        "https://example.com",
        "https://jsonplaceholder.typicode.com/users",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("havio_ai/ai-agent-url-compatibility-batch-profiler").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 '{
  "urls": [
    "https://example.com",
    "https://jsonplaceholder.typicode.com/users"
  ]
}' |
apify call havio_ai/ai-agent-url-compatibility-batch-profiler --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,havio_ai/ai-agent-url-compatibility-batch-profiler"
        }
    }
}
```

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/W9jnQ2BFtSo1uki7C/builds/XTnOFUvseqYjOfu8x/openapi.json