canonical: https://jentic.com/apis/brex.io/brex

# Brex KYC API Documentation

The Kompany KYC API (brex.io) provides programmatic access to official business register data across more than 200 jurisdictions for know-your-customer and know-your-business workflows. Agents can search for companies by name, registration number, LEI, or ISIN, retrieve original commercial register documents, and monitor companies for changes such as ownership, address, or status updates. The API also supports retrieving shareholder structures, ultimate beneficial owners, and concise company reports for compliance, onboarding, and risk-screening use cases.

## For AI agents

Look up companies in official business registers worldwide, fetch UBO and shareholder data, and monitor entities for changes. Useful for KYB onboarding, AML screening, and counterparty due diligence.

## Scope

Does not handle sanctions screening, adverse media, or ID document verification - use for official business register lookups, UBO data, and entity monitoring only.

## Capabilities

- Search business registers by company name, registration number, LEI, or ISIN across 200+ jurisdictions
- Retrieve concise and full company reports including legal form, status, address, and registration history
- Pull ultimate beneficial owner (UBO) data and shareholder structures for AML and KYB workflows
- Order original commercial register documents and certified extracts directly from source registers
- Register companies for monitoring and receive notifications when registry data changes
- Resolve LEIs and ISINs to underlying legal entity records for trade and securities compliance

## Use cases

### KYB Onboarding for B2B Customers

Verify business customers during onboarding by retrieving live data directly from the official commercial register in the customer's jurisdiction. The API supports searches by name and registration number, returns the legal form, status, registered address, and directors, and can fetch the certified register extract as evidence of verification. Coverage spans 200+ jurisdictions, so a single integration replaces dozens of country-specific connectors and typically completes a check in seconds.

Example prompt: Search for company 'Acme GmbH' in country DE via /api/v1/company/search/name/{country}/{name}, then retrieve the concise report and confirm the company status is 'active'

### Ultimate Beneficial Owner Discovery

Run AML and sanctions-driven UBO checks by retrieving shareholder hierarchies and beneficial owner data for a target company. The API exposes ownership chains so an agent can traverse from a top-level entity down to natural persons holding more than a configured threshold. This is critical for compliance teams onboarding corporate clients in regulated sectors such as banking, payments, and crypto.

Example prompt: Retrieve the shareholder list for company id 12345 and identify all natural persons with ownership greater than 25 percent

### Continuous Counterparty Monitoring

Register an existing customer or supplier portfolio for ongoing monitoring so the agent receives notifications whenever the source register publishes a change such as a director removal, address change, or insolvency filing. Notifications can be polled via the notification list endpoints and used to trigger downstream remediation workflows. This replaces periodic manual re-screening with event-driven compliance.

Example prompt: Register company id 78910 for monitoring via POST /api/v1/company/monitoring/register/{id} and then list any notifications produced in the last 7 days

### AI Agent KYC Workflow Through Jentic

An AI compliance agent uses Jentic to discover and call the brex.io KYC operations without holding the raw API key. The agent searches for 'verify a company in a business register', loads the concise report schema, and executes the call using a Jentic-vaulted credential. Combined with sanctions and adverse media APIs, this enables a fully automated onboarding decision in under a minute.

Example prompt: Use Jentic to search 'look up a company in a business register', load the brex.io operation, and execute it with country=GB and name='Stripe Payments UK Ltd'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api/v1/company/search/name/{country}/{name} | Search companies by name within a country |
| GET | /api/v1/company/deepsearch/lei/{number} | Resolve a company by LEI |
| POST | /api/v1/company/deepsearch/isin | Resolve companies by ISIN |
| POST | /api/v1/company/monitoring/register/{id} | Register a company for change monitoring |
| GET | /api/v1/company/monitoring/list | List currently monitored companies |
| GET | /api/v1/company/notification/list | List monitoring notifications |
| GET | /api/v1/company/announcement/{id} | Retrieve a company announcement |

## Key resources

- **Company Search** — Search registers by name, registration number, LEI, or ISIN across multiple jurisdictions
- **Company Reports** — Concise and full company reports including status, address, and directors
- **Shareholders and UBO** — Shareholder structures and ultimate beneficial owner data for AML workflows
- **Original Documents** — Order certified extracts and original register filings
- **Monitoring** — Register entities for change monitoring and consume notifications

## Why Jentic

- **Setup:** Wiring the Kompany KYC API by hand means setting the user_key header on every request, learning its business-register search and deepsearch endpoints, and managing monitoring subscriptions and notifications yourself. Through Jentic you install once, import the KYC API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The KYC API puts the company or monitoring id in the URL path (/api/v1/company/monitoring/register/{id}, /api/v1/company/announcement/{id}), so a rule can pin your agent to one company record: it can look it up and read its announcements and nothing else. You choose the operations it may call, so registering a company for monitoring is not included unless you add it.
- **Credential handling:** Your Kompany user_key is stored once, encrypted, by your own Jentic One instance and injected as the user_key header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'verify a company in a business register', and Jentic returns the matching brex.io operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **OpenCorporates API** — Open data on companies from official registers worldwide, often free for non-commercial use
- **Clearbit** — Firmographic and technographic enrichment for already-verified companies
- **FullContact** — Person and company enrichment with social and contact data

## FAQ

### What authentication does the Kompany KYC API use?

The API uses an API key passed as a query or header parameter (the `user_key` security scheme defined in the OpenAPI spec). Through Jentic, the key is stored encrypted in your Jentic One instance and never enters the agent's context - the agent receives a scoped execution token instead.

### Can I retrieve ultimate beneficial owner data with the Kompany KYC API?

Yes. The shareholder and UBO endpoints expose ownership structures for registered entities so you can identify natural persons with controlling interests. Combine these with the concise company report to build a full KYB record for AML screening.

### What countries does the Kompany KYC API cover?

Kompany sources data directly from official commercial registers in more than 200 jurisdictions, including all major EU member states, the UK, US, and APAC markets. Search endpoints take an ISO country code so you can route a query to the correct register.

### How do I monitor a company for changes through Jentic?

Search Jentic for 'monitor a company for register changes', load the brex.io schema, and call POST /api/v1/company/monitoring/register/{id} with the company id you want to watch. Notifications can then be polled via GET /api/v1/company/notification/list. Get started with Jentic One, the self-hosted execution layer.

### What are the rate limits for the Kompany KYC API?

The OpenAPI spec does not declare explicit rate limits; Kompany applies plan-based throttling depending on your contract. For agent workloads, Jentic batches and retries register lookups so you stay within whatever quota your key allows.

### Is the Kompany KYC API free?

No. Kompany charges per register lookup and offers tiered subscription plans. Pricing depends on the jurisdictions and document types you need; contact Kompany sales via https://kycapi.kompany.com/ for current rates.

### Can I limit what my agent is allowed to do with the Kompany KYC API?

Yes. Because Jentic One is self-hosted, your own rules decide which Kompany operations and credentials the agent may use. Since the company or monitoring id sits in the URL path, such as /api/v1/company/announcement/{id}, you can pin the agent to a single company record so it only looks up that entity and reads its announcements. You choose the operations it may call, so a write action like POST /api/v1/company/monitoring/register/{id} stays off limits unless you explicitly allow it.