# AI agents

> Give an agent company data through our hosted MCP server, with the same tools as the REST API.

Canonical: https://corpoapi.com/industries/ai-agents

## What the server exposes

The hosted server exposes search, company, verify, batch verify, coverage and VAT as tools an MCP client can call. One key covers the API and the MCP server, and an error keeps the same code it has on the REST surface, so an agent can branch on it.

- Hosted MCP server, same key as the REST API
- OpenAPI 3.1 contract for typed calls
- Stable error codes, returned as tool errors

## One lookup, from register to answer

An agent is asked to confirm a company. It checks coverage to see which registers exist, searches the name, then calls company with the number. For example, in Sweden, the search for Klarna returns Klarna Business Services Aktiebolag at 5567370431, and the company call returns its Göteborg address, Aktiebolag legal form and both identifiers, SE-ORGNR 5567370431 and EU-VAT SE556737043101.

- coverage: free and needs no key
- search: free, returns candidates with a match type
- company se/5567370431: active, Aktiebolag, Göteborg
- One company is billed once a day, so repeat calls add nothing

## Autonomous calls, bounded spend

Search, coverage and usage are free, the same company is billed at most once a day, and batch verify checks up to 100 companies in one request. The first 100 starter calls are free, then $0.01 each, so a long agent run stays cheap.

- Free search, coverage and usage
- Same company billed once a day
- Batch up to 100 companies per call

## FAQ

### Does the MCP server need a separate key?

No. It uses the same key and the same billing as the REST API, and errors come back as tool errors with the same codes.

### Can an agent discover coverage on its own?

Yes. The coverage tool is free and needs no key, so an agent can check which registers are available before it plans a task.

### How fast is a company lookup?

Against our Sweden dataset on 15 October 2026, a lookup returned in 193 ms at the median and 201 ms at p95 with a cold cache. With the dataset indexed, the same lookup returned in 58 ms at the median. The MCP tool and the REST endpoint read the same data path.