Business verification
2 Kyckr operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.
Who they are
Kyckr connects to primary company registries — the government sources of record — and returns filed data on request rather than a cached aggregate of it. Coverage and fields differ by jurisdiction because the registries themselves differ. It is used where a KYB answer has to trace back to an official source.
What a flow can call
/companies?isocode=$data.company_jurisdiction&name=$data.business_nameSearches one registry jurisdiction by company name.
/companies/$data.kyckr_company_idRetrieves a previously discovered company record.
Where it sits in the decision
Company checks answer whether the entity applying exists, who controls it, and whether its filings support the application. They usually run early: if the company cannot be verified, most of what follows is moot, and the flow can decline or refer before spending on anything else.
Whatever Kyckr returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.
Common questions
Add Kyckr as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Kyckr in a decision without ever seeing the secret.
Yes. Kyckr runs a separate sandbox host, so a flow executing in Sandbox can make the real call against test credentials and you can read the actual response shape in the trace before anything reaches a customer. The flow does not change when it graduates — only which credentials answer.
2 operations: “Search a company registry”, “Read a company record”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Search a company registry”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.
Company checks answer whether the entity applying exists, who controls it, and whether its filings support the application. They usually run early: if the company cannot be verified, most of what follows is moot, and the flow can decline or refer before spending on anything else.
Also in Business verification
Baselayer1 operationAutomated business verification for banks and fintech lenders.
baselayer.com
Creditsafe3 operationsCompany credit reports and ownership data, globally.
creditsafe.com
Middesk2 operationsBusiness identity verification from US public records.
middesk.com
Serpro4 operationsThe Brazilian government's data processing company.
serpro.gov.brReady when you are
Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.