> ## Documentation Index
> Fetch the complete documentation index at: https://developer.moltsets.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IP to Company

> Identify the company or companies associated with an IPv4 address. Pass an IP from your website visitor logs, server request data, or analytics platform and get back the domain of the organisation behind that traffic. Best suited for B2B use cases — consumer ISP addresses will typically not resolve to a named company. Use this to de-anonymise B2B web traffic, trigger account-based workflows, or feed website visitor identification pipelines.



## OpenAPI

````yaml /openapi.json post /ip_to_company
openapi: 3.1.0
info:
  title: MoltSets API
  version: 1.0.0
  description: >-
    Identity resolution API. Resolve emails, LinkedIn profiles, IP addresses,
    and emails into enriched contact and company data.
servers:
  - url: https://api.moltsets.com/api/v1/tools
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Search
    description: >-
      Search and filter company and business profiles by name, domain, industry,
      size, or revenue.
  - name: Get Valid Emails
    description: Resolve and enrich valid business and personal email addresses.
  - name: Get Carrier-Verified Mobile Phones
    description: Enrich carrier-verified mobile phone numbers.
  - name: Get Full Business Profile
    description: Resolve identifiers to full business profiles and company firmographics.
  - name: Get Ad Audience
    description: >-
      Resolve identifiers to hashed email (HEM) and mobile advertising IDs
      (MAIDs) for audience matching.
  - name: Get Company
    description: Resolve IP addresses to company data.
  - name: Account
    description: Account management tools. Free — do not consume credits.
paths:
  /ip_to_company:
    post:
      tags:
        - Get Company
      summary: IP to Company
      description: >-
        Identify the company or companies associated with an IPv4 address. Pass
        an IP from your website visitor logs, server request data, or analytics
        platform and get back the domain of the organisation behind that
        traffic. Best suited for B2B use cases — consumer ISP addresses will
        typically not resolve to a named company. Use this to de-anonymise B2B
        web traffic, trigger account-based workflows, or feed website visitor
        identification pipelines.
      operationId: ipToCompany
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - ip_address
              properties:
                ip_address:
                  type: string
                  description: IPv4 address to resolve.
                  example: 8.8.8.8
      responses:
        '200':
          description: Success
          content:
            application/json:
              examples:
                found:
                  summary: Data found
                  value:
                    results:
                      companies:
                        - domain: acme.com
                          percentage: '1.0'
                    status: ok
                    metadata:
                      tokens_charged: 1
                      tokens_remaining: unlimited
                      daily_results_remaining: 9876
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorBadRequest'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorUnauthorized'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorNotFound'
        '422':
          description: Invalid Input
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorInvalidInput'
        '429':
          description: Rate limit exceeded
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorRateLimit'
components:
  schemas:
    ErrorBadRequest:
      type: object
      properties:
        error:
          type: string
          example: Bad Request
        message:
          type: string
          example: >-
            The server cannot process the request due to a client error (400 Bad
            Request).
    ErrorUnauthorized:
      type: object
      properties:
        error:
          type: string
          example: Unauthorized
        message:
          type: string
          example: Invalid API key.
    ErrorNotFound:
      type: object
      properties:
        error:
          type: string
          example: Not Found
        message:
          type: string
          example: No match was found for the data provided.
    ErrorInvalidInput:
      type: object
      properties:
        error:
          type: string
          example: Invalid Input
        message:
          type: string
          example: Message describing the nature of the invalid input.
    ErrorRateLimit:
      type: object
      properties:
        error:
          type: string
          example: Too Many Requests
        message:
          type: string
          example: Rate limit exceeded. Maximum 100 requests per second.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Pass your API key as a Bearer token. Keys follow the format
        `ms_XXXXXXXXXXX`.

````