Capability Store
    Company Intelligence
    Live
    GLOBAL

    Your team stops reading websites and starts comparing companies.

    One public company URL goes in. The company name, its target audience, its products and services and its market come back in the same four fields. Every company on the list is described the same way, so the list can be sorted instead of read.

    Where it runs today: your own systems call it over the REST API and your engineers call it from the command line.

    What changes

    Who inside your organisation is better off, and what they can show for it.

    • Partnerships Lead at an insurer or a distributor

      Screens an inbound partner or broker-pool request before the first call, with the same four fields for every applicant, not a different summary written by whoever opened the site.

      The tool returns company_name, target_audience, products_services and market from one public URL. Source: the emable capability catalogue, status live, exposure public.

    • Head of Growth at a bank or fintech entering a new market

      Builds a target list where every candidate is described in one shape, so the list can be ranked and handed over as a sheet, not as fifteen browser tabs.

      The company brief is step one of the European Market-Entry Pack, ceiling 1,000 credits of a 28,000 credit pack. Source: the emable capability catalogue. Composed execution of that pack is still commercially gated.

    • Sales operations owner in an adviser network

      Fills the company record in the CRM from the firm's own site, so the pipeline carries what a firm sells and to whom, not only a name and a domain.

      Runs over REST and CLI, one URL per call, up to 60 seconds. A response of status: running means poll again, not a failure. Source: manifest the declared surfaces and tool latency.

    • Product Lead at an insurtech or a wealthtech

      Scans adjacent players and competitors for what they sell and who they sell it to, taken from what each company publishes about itself.

      Sources: public pages retrieved from the submitted company URL. Limitation, verbatim: the result reflects available website content, not independently verified facts. Source: the emable capability catalogue.

    Two ways to get it

    Have it delivered, or let your own AI call it.

    As a service

    We run it for you and we wire it in. Give us the list of companies, or the point in your process where companies arrive, and we hand back the briefs in one shape: name, target audience, products and services, market, one row per company. We connect the same analysis to the place a company actually enters your business, a partner intake form, a CRM company record, a target list for one market. The brief is also step one of the European Market-Entry Pack, which pairs it with EU market data and a Validator test. That pack is quoted today and its composed execution opens only after the first commercial validation signal, so we agree the scope with you first. Write to us with three things: the market, where the company names come from, and the fields you want to sort on. A person replies. There is no self-serve run on this page.

    Tell us what you need

    One message, no form. We answer with what it would take.

    Through your own AI

    Connect it once and your own assistant does the qualifying. It calls analyze_company_url with one public URL and gets back company_name, target_audience, products_services and market, then repeats that for every company on your list and answers the questions above from the results. The tool sits in the company namespace on the Emable bundle endpoint, and it is also callable over REST and CLI. Two honest conditions. It needs an Emable API key carrying company:analyze and jobs:read, because OAuth and personal-token connections are refused with an actionable message rather than a silent failure. And it runs asynchronously, up to about 60 seconds, so a response of status: running means poll again. Status is live, not pilot.

    Connector
    https://api.emable.ai/mcp
    Tools it adds
    analyze_company_url

    What your AI can answer

    Connect it once, and your assistant answers these.

    Questions in your own words, each one landing on a published tool. Ask us and we answer the same ones for you.

    1. 1What does this company sell, and who do they sell it to? (analyze_company_url)?analyze_company_url
    2. 2Which market does this company operate in? (analyze_company_url)?analyze_company_url
    3. 3Here is a partner's website. Give me a brief before tomorrow's call. (analyze_company_url)?analyze_company_url
    4. 4A lead came in overnight. What do they do, before I route it? (analyze_company_url)?analyze_company_url
    5. 5Do these two firms serve the same audience, or different ones? (analyze_company_url, once per URL)?analyze_company_url
    6. 6Go through these fifteen domains and tell me which ones sell to advisers or brokers. (analyze_company_url, once per URL)?analyze_company_url
    7. 7Before this firm goes into the CRM, fill in name, audience, products and market. (analyze_company_url)?analyze_company_url
    8. 8Which of these prospects list a product line we do not cover yet? (analyze_company_url, once per URL)?analyze_company_url
    9. 9Which of these fifty domains are not publicly reachable, so I know what still needs a person? (analyze_company_url, the refusal is the answer)?analyze_company_url

    Company Intelligence answers these through the tools above. A question outside them is refused, not guessed.

    What it rests on

    The evidence, and the edges.

    Evidence

    • Status live, exposure public, provider emable, coverage GLOBAL, access read, data class derived. Source: the emable capability catalogue.
    • Fixed output contract: company_name, target_audience, products_services, market. Every company on a list comes back in the same four fields. Source: the capability output schema.
    • Input contract: one absolute public HTTP or HTTPS URL, maximum 2048 characters, one URL per call. Source: the capability input schema.
    • Sources: public pages retrieved from the submitted company URL. Evidence freshness: the public website is retrieved for the submitted run, so a brief is as current as the site. Source: the emable capability catalogue.
    • Latency: up to 60 seconds. A response of status: running means poll again, not a failure. Source: the tool latency field.
    • Charging: included, one public-URL analysis within the account quota. No credit ceiling above zero applies. Credits are the platform metering unit, not a price. Source: the emable capability catalogue.
    • Verified usage: "Not enough verified runs yet". Public statistics appear only after 20 verified runs across 5 different accounts. Source: the platform statistics rule.
    • Placement: the company brief is step one of the European Market-Entry Pack, ceiling 1,000 credits inside a 28,000 credit pack. Source: the emable capability catalogue. That pack's execution gate is not satisfied.

    The public website is retrieved for the submitted run.

    What it does not do

    • Only publicly reachable HTTP or HTTPS pages can be analyzed.
    • The result reflects available website content, not independently verified facts.
    • One URL per call. There is no batch endpoint, so a list of companies is a list of calls.
    • OAuth and personal-token connections cannot run this tool. It needs an Emable API key carrying company:analyze and jobs:read.
    • In a trial run: public HTTP or HTTPS URL only, one run.
    • No self-serve run on this page. Every route starts with a person or a connected client.
    • It reads a company, never a person. No contact data is returned and none is exported.

    Verified usage

    Not enough verified runs yet

    Public statistics appear only after 20 verified runs across 5 different accounts.

    The contract, for the people who will wire it

    Status, permissions, tools, schemas and where it runs. The same values the API returns, so nothing here can drift from what your client will actually get.

    Status, access and price
    Status
    Live
    public
    Provider
    emable
    Manifest version
    v1.0.0
    Countries
    GLOBAL
    Data class
    derived
    Access
    read
    Permissions
    • account:read
    • company:analyze
    Charging unit
    One public-URL analysis within the account quotaPricing model: included. No separate charge per run.Credits are the platform's metering unit, not a price. We quote the engagement.
    Tools and schemas

    Analyze company URL

    read

    analyze_company_url

    Turn one company's public website into a structured company-and-market brief so you can qualify it without manual research.

    Use it when

    • The user gives a company URL and needs its products, audience, or market summarized.
    • The caller holds an Emable API key with company:analyze and jobs:read.

    Do not use it when

    • The connection is OAuth or a personal token rather than an API key — this tool refuses those with an actionable message rather than a silent failure.
    • The target is not a public HTTP or HTTPS page.

    Returns

    A structured company and market brief.

    Typical latency

    Up to 60 seconds; poll again if the response returns status: running.

    Arguments

    NameTypeRequiredDescription
    company_urlstringyesAbsolute public HTTP or HTTPS URL of the company website.

    Example: Analyze a company before a market-entry check

    {
      "company_url": "https://example.com"
    }

    {"company_name": "...", "target_audience": "...", "products_services": ["..."], "market": "..."}

    Errors a caller must handle

    • invalid_api_keyThe credential is absent, invalid, expired, or revoked.Stop and reconnect with a valid key or OAuth grant.
    • missing_scopeThe identity lacks the `company:analyze` scope this tool requires.Request `company:analyze` and reconnect.
    • 422Input does not match this tool's schema.Correct the input using the schema returned with this tool.
    • capability_runs_disabledExecution is temporarily off for this capability.Keep discovery available and retry later; this is not a permanent failure.
    • api_key_requiredThe connection is not an Emable API key with company:analyze and jobs:read.Reconnect with an API key carrying both scopes; OAuth and personal tokens are not supported for this tool.

    Input schema

    {
      "type": "object",
      "properties": {
        "company_url": {
          "type": "string",
          "format": "uri",
          "maxLength": 2048,
          "description": "Absolute public HTTP or HTTPS URL of the company website."
        }
      },
      "required": [
        "company_url"
      ],
      "additionalProperties": false
    }

    Output schema

    {
      "type": "object",
      "properties": {
        "company_name": {
          "type": "string"
        },
        "target_audience": {
          "type": "string"
        },
        "products_services": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "market": {
          "type": "string"
        }
      },
      "required": [
        "company_name",
        "target_audience",
        "products_services",
        "market"
      ],
      "additionalProperties": false
    }
    Surfaces and connectors
    rest
    cli

    No standalone MCP URL is deployed for this capability yet.

    Specialist workspace, sign in required
    Sources, limits and support

    Sources

    Public pages retrieved from the submitted company URL.

    Limitations

    Only publicly reachable HTTP or HTTPS pages can be analyzed.

    The result reflects available website content, not independently verified facts.

    Tell us what you want answered, and we will tell you what it takes.