Utilities & AI

URL Intelligence API API

The URL Intelligence API cleans and classifies URLs as clean JSON.

4 actionsLive JSON1,000 free creditsMCP-ready

🤖 Using an AI assistant? Copy this link into ChatGPT / Claude / Cursor — it reads every endpoint and parameter instantly and tells you if this API fits your use case.

The primary classify endpoint returns the final URL, cleaned and canonical URLs, domain, registrable domain and a short-link flag, and you can extract an entity, batch and resolve a catalog URL. It is built for link analysis, content pipelines and moderation that need normalized, classified URLs. One ReefAPI key, one shared credit pool, the standard envelope.

Live example

Real request and response JSON

Captured from the indexed primary action, classify, on Jul 18, 2026, 5:19 PM UTC.

Captured request

{
  "method": "POST",
  "url": "https://api.reefapi.com/enrich-url/v1/classify",
  "headers": {
    "x-api-key": "$REEF_KEY",
    "content-type": "application/json"
  },
  "body": {
    "url": "https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x"
  }
}

Captured response

{
  "ok": true,
  "meta": {
    "api": "enrich-url",
    "endpoint": "classify",
    "mode": "live",
    "latency_ms": 1146.7,
    "record_count": 1,
    "bytes": 0,
    "cache_hit": false,
    "subcalls": [
      {
        "api": "url-resolver",
        "action": "full",
        "status": "ok",
        "latency_ms": 779.9
      }
    ],
    "entity_type": "product",
    "platform": "amazon"
  },
  "data": {
    "input_url": "https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x",
    "final_url": "https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x",
    "cleaned_url": "https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20",
    "canonical_url": "https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20",
    "domain": "www.amazon.com",
    "registrable_domain": "amazon.com",
    "is_short_link": false,
    "redirect": {
      "redirected": false,
      "wall_redirect": null,
      "hops": 0,
      "chain_hosts": [
        "www.amazon.com"
      ]
    },
    "entity_type": {
      "value": "product",
      "confidence": 0.9,
      "source": "platform-map"
    },
    "platform": "amazon",
    "identifier": null,
    "recommended": {
      "engine": "amazon",
      "action": "product",
      "params": {
        "product_id": "B08N5WRWNW"
      }
    },
    "tracking": {
      "is_affiliate": true,
      "affiliate_network": "amazon_associates",
      "affiliate_type": "network",
      "merchant_hint": "amazon",
      "stripped_params": [
        "utm_source"
      ]
    },
    "preview": {
      "title": "Amazon.com",
      "description": null,
      "image": null,
      "site_name": null,
      "og_type": null
    },
    "provenance": {
      "resolver": {
        "status": "ok",
        "engine": "url-resolver"
      }
    }
  }
}

Actions

What the URL Intelligence API API does

Action	Description	Concrete use case	Key params
classify	Any URL → final_url, cleaned_url (tracking stripped), domain, entity_type{value,confidence,source}, platform, recommended{engine,action,params} (the Reef deep-fetch card; web-extract fallback for unknown hosts), tracking{affiliate,stripped_params}.	Ops teams call classify to get any URL → final_url, cleaned_url (tracking stripped), domain, entity_type{value,confidence,so….	url, deep
extract_entity	Any URL → a lightweight entity card with title, image, description, price, author and publication date — great for link previews and deciding which Reef engine to call next. Use the recommended{} field from classify for the full deep-fetch.	Developer tools call extract_entity to get any URL → a lightweight entity card with title, image, description, price, author and publica….	url
batch	Classify up to 20 URLs in one call (the link-list cleanup + routing use-case): per-URL ok/error, each independently resolved + classified.	Validation workflows call batch to get classify up to 20 URLs in one call (the link-list cleanup + routing use-case).	urls
catalog_resolve	META (no network): given a known platform name OR a URL's host, return which Reef engine+action handles it and the param key it needs — the routing table itself (url-resolver marketplace engine_hints + the non-marketplace platform map). For agents discovering 'which engine for X'.	Data-quality teams call catalog_resolve to get mETA (no network).	platform, url

Code samples

Call classify from your stack

curl -X POST https://api.reefapi.com/enrich-url/v1/classify \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"url":"https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x"}'

import requests

r = requests.post(
    "https://api.reefapi.com/enrich-url/v1/classify",
    headers={"x-api-key": REEF_KEY},
    json={
  "url": "https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x"
},
)
print(r.json()["data"])

const res = await fetch("https://api.reefapi.com/enrich-url/v1/classify", {
  method: "POST",
  headers: {
    "x-api-key": process.env.REEF_KEY,
    "content-type": "application/json",
  },
  body: JSON.stringify({
  "url": "https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x"
}),
});
const { ok, data, meta, error } = await res.json();

MCP one-liner

Ask your MCP-connected assistant: call reefapi.enrich-url.classify with {"url":"https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x"}.

Use cases

Who uses this API and why

Content pipelines call classify to clean and canonicalize URLs before storage.
Moderation uses classify to flag short links and risky domains.
Commerce uses catalog_resolve to map a product URL to a known item.

FAQ

Questions developers ask before integrating

What is the URL Intelligence API API?

URL Intelligence API API is a ReefAPI endpoint group for url intelligence api It returns live JSON through POST requests under /enrich-url/v1.

Is the URL Intelligence API API free to try?

Yes. ReefAPI starts with 1,000 free credits, no card required. URL Intelligence API calls use the same shared credit balance as every other ReefAPI engine.

Do I need a URL Intelligence API login or account?

No login to URL Intelligence API is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

How fresh is the URL Intelligence API data?

The page example is captured from a live classify call, and production requests fetch live data through ReefAPI rather than a static sample.

How many credits does the URL Intelligence API API use?

URL Intelligence API actions currently cost 1-2 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Can I call URL Intelligence API from an AI assistant or MCP client?

Yes. Connect ReefAPI once through MCP and your assistant can call enrich-url actions with the same key, credit pool and JSON envelope used by normal REST requests.

Is the URL Intelligence API API a URL Intelligence API scraper?

It is the managed alternative to a DIY URL Intelligence API scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same url intelligence api back as clean JSON.

Why does my URL Intelligence API scraper keep getting blocked?

Most URL Intelligence API scrapers break on anti-bot defenses, rate limits and IP bans that need rotating residential proxies and browser fingerprinting to clear. ReefAPI handles all of that for you — no proxies, no captchas, no maintenance — and returns live JSON. Blocked or failed calls are free.

docs / enrich-url

URL Intelligence API

base /enrich-url/v14 endpoints

post/enrich-url/v1/classify2 credits

Any URL → final_url, cleaned_url (tracking stripped), domain, entity_type{value,confidence,source}, platform, recommended{engine,action,params} (the Reef deep-fetch card; web-extract fallback for unknown hosts), tracking{affiliate,stripped_params}.

Parameter		Allowed / range	Description
url	required	—	Any http(s) URL — short/affiliate/tracking/canonical — or a bare host (stripe.com). Redirects are followed + tracking stripped by the inner url-resolver (SSRF-guarded). Private/internal targets are blocked there.
deep = false	optional	—	Advanced: when true, run an additional structured-data pass even when the page type was already identified, for deeper detail. Default false = fastest, most cost-efficient path.

Try in playground →

post/enrich-url/v1/extract_entity2 credits

Any URL → a lightweight entity card with title, image, description, price, author and publication date — great for link previews and deciding which Reef engine to call next. Use the recommended{} field from classify for the full deep-fetch.

Parameter		Allowed / range	Description
url	required	—	Any http(s) URL — short/affiliate/tracking/canonical — or a bare host (stripe.com). Redirects are followed + tracking stripped by the inner url-resolver (SSRF-guarded). Private/internal targets are blocked there.

Try in playground →

post/enrich-url/v1/batch2 credits

Classify up to 20 URLs in one call (the link-list cleanup + routing use-case): per-URL ok/error, each independently resolved + classified.

Parameter		Allowed / range	Description
urls	required	—	Up to 20 URLs (array or comma-separated). Each is resolved + classified independently; per-URL ok/error.

Try in playground →

post/enrich-url/v1/catalog_resolve1 credit

META (no network): given a known platform name OR a URL's host, return which Reef engine+action handles it and the param key it needs — the routing table itself (url-resolver marketplace engine_hints + the non-marketplace platform map). For agents discovering 'which engine for X'.

Parameter		Allowed / range	Description
platform	optional	—	A platform name (instagram/youtube/github/amazon/…) to resolve to its Reef engine+action. Omit both platform and url to list the full table.
url	optional	—	Optional URL whose host is mapped to its Reef engine (no network fetch — host-only routing lookup).

Try in playground →

Example request · classify

curl -X POST https://api.reefapi.com/enrich-url/v1/classify \
  -H "x-api-key: $REEF_KEY" \
  -H "content-type: application/json" \
  -d '{"url":"https://www.amazon.com/dp/B08N5WRWNW?tag=aff-20&utm_source=x"}'

Response shape

{
  "ok": true,
  "data": { /* the result */ },
  "meta": {
    "latency_ms": 240,
    "record_count": 12,
    "completeness_pct": 100
  },
  "error": null
}