Brex KYC API Documentation
60
AI ReadinessAI-Aware (B-)60/100
Community OpenAPI document · agent-readyData EnrichmentCompany DataapiKey54 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For 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.
Use for: I need to verify that a counterparty company is registered and active, Find all shareholders and ultimate beneficial owners for a German GmbH, Search for a company by name in the UK companies house, Retrieve the original commercial register extract for a Spanish SL
Not supported: Does not handle sanctions screening, adverse media, or ID document verification - use for official business register lookups, UBO data, and entity monitoring only.
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.
Install Jentic One Beta
Connect the KYC API Documentation to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the KYC API Documentation, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrex.io%2Fbrex" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrex.io%2Fbrex" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with KYC API Documentation API.
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
Patterns agents use KYC API Documentation API for, with concrete tasks.
★ 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.
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.
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.
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.
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
54 endpoints — the kompany kyc api (brex.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
K
KYC API Documentation
- AI-Aware (B-)60/100
52
Foundational Compliance64
Developer Experience & Jentic Compatibility47
AI-Readiness & Agent Experience93
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
52
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C-Signals: 4
83%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
25%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
7%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
47
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
37%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
93
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
93%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using KYC API Documentation API through Jentic.
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.
GET STARTED