Skip to main content
GET
/
company
Extract company info
curl --request GET \
  --url https://api.prefetch.io/company \
  --header 'X-API-Key: <api-key>'
{
  "success": true,
  "data": {
    "domain": "stripe.com",
    "url": "https://stripe.com",
    "company": {
      "name": "Stripe, Inc.",
      "emails": [
        "support@stripe.com"
      ],
      "addresses": [
        "354 Oyster Point Blvd, South San Francisco, CA 94080"
      ],
      "sources": [
        "jsonld",
        "footer"
      ],
      "confidence": 0.92
    }
  },
  "meta": {
    "requestId": "b9e1a2f3-4c5d-6e7f-8a9b-0c1d2e3f4a5b",
    "durationMs": 3210
  }
}

Documentation Index

Fetch the complete documentation index at: https://prefetch.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Overview

/company scrapes a website to identify the legal entity behind it. It looks for structured data (JSON-LD, schema.org), footer content, contact pages, and other signals to extract:
  • Company name — legal entity name (e.g. “Stripe, Inc.”)
  • Emails — contact and support email addresses
  • Addresses — physical locations including street, city, state, ZIP, country
  • Sources — where the data was found (jsonld, footer, contact, etc.)
  • Confidence — extraction confidence score (0–1)
This endpoint uses a hybrid approach: it first attempts a fast static fetch, falling back to headless Chrome only when needed.

Example request

curl "https://api.prefetch.io/company?url=https://stripe.com" \
  -H "X-API-Key: $PREFETCH_API_KEY"

Example response

{
  "success": true,
  "data": {
    "domain": "stripe.com",
    "url": "https://stripe.com",
    "company": {
      "name": "Stripe, Inc.",
      "emails": [
        "support@stripe.com"
      ],
      "addresses": [
        "354 Oyster Point Blvd, South San Francisco, CA 94080"
      ],
      "sources": ["jsonld", "footer"],
      "confidence": 0.92
    }
  },
  "meta": {
    "requestId": "b9e1a2f3-4c5d-6e7f-8a9b-0c1d2e3f4a5b",
    "durationMs": 3210
  }
}

Understanding confidence

The confidence score reflects how reliably the data was extracted:
RangeMeaning
0.8 – 1.0High confidence — data from structured sources (JSON-LD, schema.org)
0.5 – 0.79Medium confidence — data inferred from footer, about page
0.0 – 0.49Low confidence — best guess from unstructured content
A low confidence score doesn’t mean the data is wrong — it means you may want to verify it. Sites without structured data will generally score lower.

Authorizations

X-API-Key
string
header
required

Your Prefetch API key. Obtain one from the dashboard.

Query Parameters

url
string
required

The website URL to process. http:// is prepended automatically if no protocol is provided. Maximum 2048 characters.

Example:

"https://stripe.com"

Response

Company information.

success
enum<boolean>
required
Available options:
true
data
object
required
meta
object
required