ArsenAI Enrich Match

ArsenAI Enrich Match sends an existing business-search result and selected application fields to Lendflow’s ArsenAI enrichment service. The service enriches business-owner match data using the selected source. The Workflow Builder block is ArsenAIEnrich, and its service ID is arsen_ai_enrich.

Requirements

Application field	Requirement	Notes
Business legal name	Required	Uses the legal name on the application.
Business address city	Required	Uses the city from the business address.
Business address state	Required	Must be a valid state.
Business address street	Optional	May be unavailable when the selected source is Experian Business Quick Search.
Business address ZIP code	Optional	May be unavailable when the selected source is Experian Business Quick Search.
Completed source-service result	Required	The selected source must already have a stored request and a non-empty response. Accepted sources are Clear ID Confirm Business Search, Experian Business Quick Search, and LexisNexis Contact Card. Clear is selected by default.

API flow

Run the chosen source service and wait until it has stored both a request and response.
Call Enrich Business Credit Application.
Set provider to arsen_ai_enrich.
Supply options.arsenAIEnrichSource when you do not want the default Clear source.
Optionally include stage_id; when supplied, it must be a valid underwriting workflow-stage UUID for the application.
Treat {"data":{"onqueue":true}} as queue acceptance, not completed enrichment.
Poll Get Commercial Data with services[]=arsen_ai_enrich.

{
  "provider": "arsen_ai_enrich",
  "options": {
    "arsenAIEnrichSource": "experian_business_quick_search"
  },
  "stage_id": "6ff8f7f6-1eb3-3525-be4a-3932c805afed"
}

Data	API response path
Stored ArsenAI response	`commercial_data.arsen_ai_enrich`
Lifecycle message	`statuses.arsen_ai_enrich`
Stored request	`request_data.arsen_ai_enrich`

The API queues a background job. Inside that job, Lendflow builds the source-specific payload, posts it to ArsenAI, stores the JSON response and HTTP status, and marks a failed provider response as failed.

Data Orchestration availability and flow

ArsenAI Enrich Match is not included in the current Data Orchestration service catalog. Run the prerequisite source and arsen_ai_enrich through the enrichment API or the Workflow Builder block rather than selecting it as a Data Orchestration service step.

What the service returns

Response area	Meaning
Stored request	The exact source-specific payload sent by Lendflow after sensitive-value obfuscation.
Stored response	Raw JSON returned by ArsenAI for the selected source.
Source relationship	The request’s `external_service.source` identifies which upstream result was enriched.
Enrichment fields	Provider-controlled and source-dependent. The repositories do not define one stable public response schema for `arsen_ai_enrich`.

Representative response

The checked-in implementation validates that ArsenAI returns JSON, but it does not provide a sanitized response fixture or a stable field contract. The following empty object is intentionally schematic so that this guide does not invent provider fields:

{}

Actual successful responses can contain source-dependent fields. Read the stored object at commercial_data.arsen_ai_enrich as raw provider JSON.

Response attributes

Attribute	Type	Meaning	Possible values or units	When returned
Stored response root	Object or array	JSON returned by ArsenAI.	Raw, source-dependent JSON with no stable field catalog in the current repositories.	After ArsenAI returns valid JSON.
Response fields	Unknown	Enrichment output defined by ArsenAI for the selected source.	Provider-controlled; types, enumerations, and null behavior are not defined in the checked-in schema.	Only when the provider returns those fields.
`request_data.arsen_ai_enrich.existing_data.business_name`	String	Application business legal name sent for enrichment.	Application text.	In the stored request.
`request_data.arsen_ai_enrich.existing_data.business_address.city`	String	Application business city sent for enrichment.	Application text.	In the stored request.
`request_data.arsen_ai_enrich.existing_data.business_address.state`	String	Application business state sent for enrichment.	Application text.	In the stored request.
`request_data.arsen_ai_enrich.external_service.source`	String	Upstream service used as the enrichment source.	One of the three supported source IDs.	In the stored request.
`request_data.arsen_ai_enrich.external_service.data`	Array	Stored response from the selected upstream service.	Source-dependent data.	In the stored request after the prerequisite exists.

Errors and statuses

An unsupported options.arsenAIEnrichSource value fails Lendflow request validation.
If the selected source lacks either its stored request or response, Lendflow returns Response for the chosen source {service_id} is missing. and does not call ArsenAI.
Missing business name, city, or state fails the ArsenAI payload validation. Street, ZIP, owner names, and business telephone can be null under the validated rules.
A non-JSON or failed ArsenAI response causes the queued job to fail.
Success means Lendflow stored ArsenAI’s JSON response. It is not a guarantee that any particular enrichment field is present or non-null.

FAQ

Which source is used when I omit the option?

Lendflow defaults to clear_id_confirm_business.

Must I run the source service first?

Yes. The selected source must have both a stored request and a non-empty stored response before ArsenAI Enrich Match runs.

Why does this guide not list ArsenAI response fields?

The current repositories do not define a stable public response schema or sanitized response fixture. The stored response is raw and source-dependent, so listing fields would invent an unsupported contract.

Can this service run in Data Orchestration?

No. It is not included in the current Data Orchestration service catalog.