> ## Documentation Index > Fetch the complete documentation index at: https://www.forager.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Forager is a REST API for B2B people, company and job post data: contact lookups (phone numbers, personal emails, work emails), person, company and job post search, and bulk data feeds. > Server: https://api-v2.forager.ai. Send the API key in the X-API-KEY header. Most paths include {account_id}. Read FORAGER_API_KEY and FORAGER_ACCOUNT_ID from the environment; never put the key in client-side code, logs or prompts. > To add Forager to a project, follow https://www.forager.ai/docs/guides/agent-quickstart.md. To pick an endpoint, read https://www.forager.ai/docs/guides/choose-an-endpoint.md. For end-to-end builds, see https://www.forager.ai/docs/recipes/overview.md. > Most requests spend credits. Do not guess costs; use https://www.forager.ai/docs/api-overview/credit-pricing.md and ask the user before spending credits. > Use only endpoints and fields defined in https://www.forager.ai/docs/openapi.yaml. Forager has no MCP server for the API yet; the /mcp endpoint on this site searches the documentation only. # Website lookup API > Retrieve details about a website: domain, web rank, traffic and associated web technologies. ## When to use this endpoint You have a company domain, a Forager `organization_id` or a LinkedIn company slug and want the website's traffic ranks and the web technologies detected on it. ## Example request ```bash cURL theme={"theme":{"light":"github-light","dark":"github-dark"}} curl -X POST "https://api-v2.forager.ai/api/$FORAGER_ACCOUNT_ID/datastorage/website_detail_lookup/" \ -H "X-API-KEY: $FORAGER_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "domain": "acme.com" }' ``` Set `FORAGER_API_KEY` and `FORAGER_ACCOUNT_ID` as in the [quickstart](https://www.forager.ai/docs/api-overview/send-your-first-request.md). ## Example response ```json 200 (illustrative values) theme={"theme":{"light":"github-light","dark":"github-dark"}} { "id": 7731, "domain": "acme.com", "tranco_rank": 48213, "similarweb_rank": 51000, "similarweb_traffic": 820000, "website_technologies": [ { "web_technology_id": 1189, "is_active": true, "name": "Example CMS" }, { "web_technology_id": 2042, "is_active": false, "name": "Example Chat Widget" } ] } ``` ## Credits Each request costs **1 credit**. See [API credits and pricing](https://www.forager.ai/docs/api-overview/credit-pricing.md) for how credits are charged and how to check what you spent. ## OpenAPI ````yaml POST /api/{account_id}/datastorage/website_detail_lookup/ openapi: 3.0.3 info: title: Forager public API version: 1.0.0 description: Forager public API endpoints documentation servers: - url: https://api-v2.forager.ai security: [] tags: - name: Job Posts description: >- Search the Forager job-post index. Use these endpoints to find job postings by attributes such as title, location, posted date, or hiring organization, and to retrieve aggregate totals for a given query before paginating through full results. - name: Organizations description: >- Search the Forager organization index. Filter companies by attributes such as industry, headcount, location, keywords, and web technologies, and retrieve total match counts alongside the result set. - name: People description: >- Look up people and their records. Use the search endpoints to find people by role, employer, location, or skills, and the detail-lookup endpoints to fetch a full person record by ID, email, or phone number. Contact data has its own sections: Phones, Personal Emails, and Work Emails. - name: Phones description: >- Retrieve phone numbers for a known person. Provide identifying information (such as a LinkedIn handle or Forager ID) and get back the available phone numbers. - name: Personal Emails description: >- Retrieve personal email addresses for a known person. Returns addresses on free webmail / consumer providers (Gmail, Outlook, Yahoo, iCloud, Proton, and similar); corporate, educational, and other custom domains are excluded to keep deliverability high. - name: Work Emails description: >- Find and verify a person's work email address. Submit a lookup (single or bulk), poll the job for its result, and optionally receive the result by webhook when the job completes. - name: Websites description: >- Look up information about a website, including the organization that owns it and the technologies detected on the domain. - name: Users description: >- Manage your Forager account. Retrieve the current authenticated user, create and revoke API keys used to authenticate requests to the rest of the API, and review the credit balance-change log that records every lookup charge or adjustment against your account. - name: Autocomplete description: >- Resolve free-text input into the canonical IDs used elsewhere in the API. Each endpoint returns matching options for a search term (industries, organizations, organization keywords, locations, person skills, web technologies) so they can be passed as filters to the search endpoints. - name: Feedback description: >- Report verification feedback for contact data (phone numbers, personal emails, work emails) returned by Forager person lookups. Use these endpoints to submit whether a contact value is valid/invalid and whether it belongs to the matched person — every submission is stored as a new row and is used to improve the accuracy of future lookups. paths: /api/{account_id}/datastorage/website_detail_lookup/: post: tags: - Websites summary: Website Details Lookup description: >- The Website Details Lookup endpoint retrieves detailed information about a specific website, including its domain, web rank, traffic, and associated web technologies. This API is useful for analyzing website performance, understanding technology stack, and integrating website data into your applications. operationId: datastorage_website_detail_lookup_create parameters: - in: path name: account_id schema: type: integer required: true requestBody: content: application/json: schema: $ref: '#/components/schemas/WebSiteLookupRequest' application/x-www-form-urlencoded: schema: $ref: '#/components/schemas/WebSiteLookupRequest' multipart/form-data: schema: $ref: '#/components/schemas/WebSiteLookupRequest' responses: '200': content: application/json: schema: $ref: '#/components/schemas/WebSite' description: '' '403': $ref: '#/components/responses/AuthenticationFailed' security: - Api-Key: [] components: schemas: WebSiteLookupRequest: type: object description: WebSite lookup API request serializer. properties: domain: type: string organization_id: type: integer organization_linkedin_public_identifier: type: string WebSite: type: object description: WebSite serializer. properties: id: type: integer readOnly: true domain: type: string format: uri maxLength: 200 tranco_rank: type: integer maximum: 2147483647 minimum: 0 nullable: true description: The Tranco three month average traffic rank similarweb_rank: type: integer maximum: 2147483647 minimum: 0 nullable: true similarweb_traffic: type: integer maximum: 9223372036854776000 minimum: 0 format: int64 nullable: true website_technologies: type: array items: $ref: '#/components/schemas/WebSiteTechnology' readOnly: true required: - domain - id - website_technologies WebSiteTechnology: type: object description: WebSiteTechnology serializer. properties: web_technology_id: type: integer readOnly: true is_active: type: boolean title: Is active? name: type: string description: Get WebTechnology name. readOnly: true required: - name - web_technology_id responses: AuthenticationFailed: description: >- The X-API-KEY header is missing, the key is not valid, or the key does not have permission for this resource. content: application/json: schema: type: object properties: detail: type: string example: detail: Authentication credentials were not provided. securitySchemes: Api-Key: type: apiKey in: header name: X-API-KEY ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.