# Firmable for security teams

> Security ratings watch the perimeter and your email gateway filters the inbox. Firmable gives your security agents the business side of each vendor and sender: what the vendor runs, what kinds of AI tools it uses, and which company a domain really belongs to.

- Web page: https://developer.firmable.ai/solutions/security
- Get a free API key: https://platform.firmable.com/sign-up
- Full API reference: https://docs.firmable.com/api-reference/overview

Works alongside: Third-party risk platform, Security ratings, Email security, Security operations agent.

Firmable doesn't scan networks or IP ranges. It adds business context to the security tools you already run.

## From vendor intake to SOC triage.

Third-party risk and email security tasks where knowing the business behind a vendor or domain speeds up the call.

### Tier vendors before the questionnaire

Your security agent asks: "Which vendors run the software our questionnaire asks about?"

Pull up to 20 technologies each for up to 200 vendors in one call, and the full stack for any vendor you need, then tier and prefill the questionnaires.

Calls: [`bulk_get_tech_intel`](https://docs.firmable.com/api-reference/overview), [`get_tech_intel`](https://docs.firmable.com/api-reference/overview)

For security teams: Reviews ordered by what vendors actually run.

### Find AI in the supply chain

Your security agent asks: "Which of our vendors use AI tools that could touch our data?"

Read the footprint area of AI adoption for up to 100 vendors per call: the categories of AI tools in use and the main tool in each. Add withEvidence for every tool.

Calls: [`POST /ai-adoption`](https://docs.firmable.com/api-reference/overview), [`get_ai_adoption`](https://docs.firmable.com/api-reference/overview)

For security teams: An audit question answered across the vendor list.

### Triage business email compromise

Your security agent asks: "This invoice came from a lookalike domain. Does it belong to the supplier?"

Check the sending domain against the supplier while the email is in triage, before anyone pays.

Calls: [`owns_domain`](https://docs.firmable.com/api-reference/overview)

For security teams: Fraudulent invoices stopped in the SOC, not after payment.

### Attribute a domain

Your security agent asks: "Which business is behind this domain?"

Look the domain up and attach the company's name, size, industry and country to the incident.

Calls: [`GET /company`](https://docs.firmable.com/api-reference/overview)

For security teams: Analysts see the business, not just the domain.

### Deduplicate the vendor inventory

Your security agent asks: "Are these two vendor records the same business?"

Look each vendor up for its Firmable ID, then compare records across procurement and security tools.

Calls: [`GET /company`](https://docs.firmable.com/api-reference/overview), [`is_same_business`](https://docs.firmable.com/api-reference/overview)

For security teams: One vendor, one record, one review.

## Example: Pull the stack for a vendor list

A bulk_get_tech_intel call on the Firmable MCP server, with placeholder domains. Up to 200 companies, 20 technologies each.

```
{
  "name": "bulk_get_tech_intel",
  "arguments": {
    "items": [
      { "domain": "vendor-one.example" },
      { "domain": "vendor-two.example" }
    ]
  }
}
```

## Where it fits in your security stack.

- **In the TPRM platform.** Call the REST API at vendor intake, with one developer key.
- **In the SOC.** Add the MCP server to your triage agent so it can check domains mid-investigation.
- **Across the vendor list.** Tech Intelligence covers 200 vendors a call, and AI adoption 100.
- **Next to your scanners.** Keep perimeter and network scanning where they are. Firmable adds the business context.
