timzinin-com Company Lookup API

The Company Lookup API from timzinin-com — 1 operation(s) for company lookup.

Operations 1

POST /api/company-lookup Company Profile Lookup #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/timzinin-com:timzinin-com-company-lookup-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

timzinin-com-company-lookup-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Zinin M2M Hub Company Lookup API
  description: Pay-per-call data & tool APIs
  version: 1.0.0
  x-guidance: 'Zinin M2M Hub — pay-per-call data & tool APIs for AI agents. Each POST /api/{slug} operation below is a distinct paid tool: call GET /api/{slug}/schema first for the exact input shape, then POST with a signed PAYMENT-SIGNATURE header (x402 v2, USDC — see x-payment-info per operation) or omit it to receive a 402 with full payment requirements in the PAYMENT-REQUIRED header. The same catalog is also available as MCP JSON-RPC tool bundles at POST /mcp/{bundle} — see GET /.well-known/x402 for the list of bundles.'
tags:
- name: Company Lookup
paths:
  /api/company-lookup:
    post:
      summary: Company Profile Lookup
      description: 'Turn a domain or company name into one unified company card: website tech stack (CMS, ecommerce, key tech) for domains, plus a live GLEIF registry match (legal name, jurisdiction, status, LEI). Keyless, no login — built for AI agents and sales.'
      operationId: call_company_lookup
      x-payment-info:
        price:
          mode: fixed
          currency: USD
          amount: '0.010000'
        protocols:
        - x402: {}
        network: eip155:8453
        payTo: '0x409D32aD39C02BC9B23a8b2d447532ed801b12dE'
        asset: '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              title: Company Lookup input
              type: object
              schemaVersion: 1
              properties:
                companies:
                  title: Companies
                  type: array
                  description: Company domains (e.g. "stripe.com"), legal names (e.g. "Monzo Bank Limited") or LEIs to look up. One row per entry. Add a country hint after a pipe — "stripe.com | US" — to keep the registry match inside one country; same-named companies exist in several. An LEI is used as-is, with no name search.
                  maxItems: 100
                  editor: stringList
                  prefill:
                  - stripe.com | US
                  - Monzo Bank Limited | GB
                maxConcurrency:
                  title: Max concurrency
                  type: integer
                  description: How many companies to look up in parallel.
                  default: 10
                  minimum: 1
                  maximum: 30
              required:
              - companies
      responses:
        '200':
          description: Actor run succeeded and payment settled
          content:
            application/json:
              schema:
                type: object
                properties:
                  results:
                    type: array
                    items:
                      type: object
                    description: Actor output items — shape is actor-specific (varies per tool); see this operation's own requestBody schema/description for what the underlying actor produces.
                  meta:
                    type: object
                    properties:
                      run_ms:
                        type: integer
                        description: Actor run duration in milliseconds
                      item_count:
                        type: integer
                        description: len(results)
                      settled:
                        type: boolean
                        description: Whether the x402 payment was confirmed settled by the facilitator
                      transaction:
                        type:
                        - string
                        - 'null'
                        description: On-chain settlement transaction hash, null if unsettled
                    required:
                    - run_ms
                    - item_count
                    - settled
                    - transaction
                required:
                - results
                - meta
        '400':
          description: Malformed PAYMENT-SIGNATURE header or request body
        '402':
          description: Payment required or invalid — see PAYMENT-REQUIRED header
        '409':
          description: Payment payload already used
        '502':
          description: Actor run failed
        '504':
          description: Actor run timed out
      tags:
      - Company Lookup