Enigma provides comprehensive data on U.S. businesses, offering insights into their identity and financial health to support sales, marketing, risk assessment, and compliance processes.
Enigma provides comprehensive data on U.S. businesses, offering insights into their identity and financial health to support sales, marketing, risk assessment, and compliance processes. On Nagent, Enigma is exposed as a fully-configurable business intelligence integration that any agent can call — 19 actions, and API key authentication. No code is required to wire Enigma into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Enigma to automate the kinds of tasks business intelligence teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Enigma into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Enigma, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ENIGMA_CREATE_LISTTool to create a new list to organize and group entities in Enigma. Use when you need to create a list for data generation or enrichment purposes. The list can be populated using search criteria (entityType and prompt) to find matching entities.
Input parameters
Name of the list to create
List generation type.
Optional description of the list's purpose or contents
File format for list export. Defaults to PARQUET
Search input configuration for list creation.
URI of an input file to use for list creation
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_CREATE_SUGGESTIONTool to create a suggestion for data correction, enhancement, or analysis feedback in Enigma. Use when you need to submit feedback or suggest improvements to data in the Enigma platform.
Input parameters
Specific field being suggested for modification
Core data for the suggestion. Typically contains entities array with type and message fields
Proposed value being suggested in JSON format
Email address of the person making the suggestion (required)
List of parent entity identifiers
User identifier for the suggestion author
Identifier for an entity in the Enigma system.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_DELETE_LISTTool to delete an existing list permanently from the system. Use when you need to remove a list by its ID. Returns confirmation with the ID of the deleted list.
Input parameters
Unique identifier of the list to delete permanently from the system
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_ACCOUNTTool to retrieve information about the current API account via GraphQL. Use when you need to check customer ID, billing details, pricing plan, credit availability, or auto-recharge settings.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_AGGREGATE_COUNTSTool to get aggregate counts of operating locations and their associated brands or legal entities. Use when you need summary counts rather than detailed entity information. Supports filtering by open operating locations.
Input parameters
Field to count: 'brand' for brand counts, 'operatingLocation' for location counts, 'legalEntity' for legal entity counts
Type of entity to aggregate. Currently only OPERATING_LOCATION is supported
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_ATTRIBUTE_GROUPSTool to retrieve attribute groups for Enigma entity types. Returns JSON metadata describing available attributes organized into logical groups (ID, Name, Address, etc.) with their corresponding GraphQL field paths. Use when you need to discover queryable fields for Brand, OperatingLocation, or LegalEntity entities.
Input parameters
The entity type to get attribute groups for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_BACKGROUND_TASKTool to get the status and results of a background task by ID. Use when checking async operation progress or retrieving results from previously initiated long-running operations.
Input parameters
The ID of the background task to retrieve (must be a valid UUID format)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_BUSINESSTool to retrieve detailed business information using an Enigma ID. Returns comprehensive business profile including addresses, names, websites, associated people, industries, and more. Use when you need complete business details for a specific Enigma ID obtained from a prior search or match operation.
Input parameters
Comma-separated list of attributes to return (e.g., 'industries,address,phones'). If not specified, returns all available attributes.
Unique Enigma identifier for the business (e.g., B00233ee1f5e, B000189f2c74d)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_DECISIONTool to retrieve a screening decision by its request ID. Use when you need to check the status, alert status, assignee, or timestamps of a previously created decision. Requires case management to be enabled for the account.
Input parameters
The decision ID (request_id from screening response). UUID format expected.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_GRAPH_QL_SCHEMA_EXTENDEDTool to retrieve extended schema information for Enigma's GraphQL API. Returns metadata about available types, fields, projections, and data asset metadata. Use when you need to explore the GraphQL schema structure or understand what data types and fields are available.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_LIST_MATERIALIZATIONTool to retrieve a specific list materialization by its unique ID. Returns detailed information about the materialized list including status, progress, and results location. Use when you need to check the status or retrieve results of a list materialization operation.
Input parameters
Unique materialization identifier (UUID format) to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_GET_SANCTIONED_ENTITYTool to retrieve detailed information about a specific sanctioned entity by its ID. Returns full entity profile including names, aliases, DOB, nationality, addresses, documents, and program designations. Use this when you need complete information about a known sanctioned entity from screening results.
Input parameters
Output format for the response. 'structured' returns organized entity data, 'raw' returns unprocessed data, 'display' returns human-readable format, 'attributes' returns attribute list
Provider of the sanctions list (e.g., 'ofac')
Record ID of the entity to retrieve. This is the numeric identifier from the sanctions list (e.g., '43085')
Collection within the provider (e.g., 'sdn' for Specially Designated Nationals, 'non_sdn' for non-SDN lists)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_KYB_VERIFICATIONThis tool performs a Know Your Business (KYB) check on a U.S. business by querying Enigma's dataset of legal entities based on official state records. It verifies business information and returns comprehensive details about the business, including best match, legal entities, brands, and watchlists. Supports U.S. businesses only.
Input parameters
Name of the business to verify
Comma-separated list of additional attributes to include in the response
Number of matches to return
Address details of the business Include street address and ZIP code for best match quality.
Package type for the response. Can be 'identify' or 'verify'
Minimum match confidence score (0 to 1) Name or address formatting variations can lower scores; tune this threshold accordingly.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_LIST_DECISIONSTool to retrieve multiple screening decisions with pagination and filtering options. Use when you need to list, search, or review historical screening decisions by alert status, assignee, date range, tag, or decision status.
Input parameters
Number of results per page. Default is 10
Filter by the request tag assigned during screening
Page number for pagination (0-indexed). Default is 0
Filter by alert status. Use true to show only alerted decisions, false for non-alerted
Filter by decision status (e.g., 'pending_review', 'approved', 'rejected')
Filter decisions up to this date (format: YYYY-MM-DDTHH:MM, e.g., '2024-12-31T23:59')
Filter decisions from this date (format: YYYY-MM-DDTHH:MM, e.g., '2024-01-01T00:00')
Filter by the user ID to whom decisions are assigned
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_MATCH_BUSINESSTool to match business records against Enigma's SMB data asset using fuzzy matching on business name and location. Use when you need to identify a business profile and obtain an Enigma ID for further data retrieval.
Input parameters
Name of the business to match
Number of top matches to return. Default is 1
Potential business owner information.
Business address for matching.
Business website URL to help with matching
Set to 'MTX' to prioritize matches with revenue data availability
Minimum match confidence score (0 to 1). Only return matches with confidence above this threshold. Default is 0.5
Set to 1 to include non-matching results in the response
Type of entity to match: 'business' for business entities or 'business_location' for specific business locations
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_SCREENING_VERIFICATIONA tool to screen customers and transactions against sanctions and other watchlists. This endpoint allows for independent verification without requiring any external resource IDs.
Input parameters
Unique identifier or description for this screening request (echoed in response)
List of searches to perform. Each search can be ENTITY (structured) or TEXT (free-text)
Optional caller identifier for tracking purposes
Query type to execute. Default: 'enigma_data'
Optional configuration to customize thresholds, weights, and watchlist groups
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_SEARCH_GRAPH_QLTool to search and retrieve entities from Enigma's comprehensive U.S. business database. Returns brands (customer-facing identities), operating locations (physical/virtual spaces), or legal entities (government registrations) based on search criteria. Search precision is approximately 94% for all entity types. Use when you need to find business information by name, address, phone, website, or TIN.
Input parameters
Tax Identification Number (TIN/EIN) for legal entity searches
Name of the business, brand, or legal entity to search for
Phone number to search for (helps identify specific locations)
Address criteria for narrowing search results.
Website URL to search for
Type of entity to search for: BRAND (customer-facing identity), OPERATING_LOCATION (physical/virtual location), or LEGAL_ENTITY (government-registered entity)
Minimum confidence score for results (0.0-1.0). Default is determined by Enigma. Higher values return more precise matches.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_SEARCH_LISTSTool to search and retrieve user-created lists via GraphQL. Returns paginated list connections with cursor-based pagination. Use when you need to query, filter, or browse entity lists.
Input parameters
Input parameters for searching and filtering lists with cursor-based pagination.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENIGMA_VERIFY_BUSINESS_V2Tool to verify business identity using Enigma's KYB v2 endpoint. Performs comprehensive business verification including TIN verification, SSN verification, watchlist screening, and business bankruptcy checks. This is the current recommended version of the KYB API. Use when you need to verify a business's identity, check compliance, or assess business risk.
Input parameters
Tax Identification Number (TIN/EIN) for verification (format: 12-3456789 or 123456789)
Business name for verification. Provide either 'name' or 'names', not both
Array of Tax Identification Numbers (max 1)
Comma-separated list of additional attributes: 'watchlist' (watchlist screening), 'tin_verification' (TIN verification), 'ssn_verification' (SSN verification), 'business_bankruptcy' (bankruptcy checks). Example: 'watchlist,tin_verification'
Array of business names (max 2). Use for both operating names and legal names. Provide either 'name' or 'names', not both
Maximum number of top matching entities to return (default: 10)
Person associated with the business (e.g., owner, officer).
Business address information.
KYB package type: 'identify' (basic matching) or 'verify' (includes TIN/SSN verification and screening). Default is 'verify'
Business website URL
Array of business website URLs (max 1)
Array of business addresses (max 2). Provide either 'address' or 'addresses', not both
Minimum confidence threshold for matches, between 0.0 and 1.0 (default: 0.5)
Array of persons to screen against watchlists (max 4)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 41 agents privately built on Nagent that already use Enigma.
Build on Nagent
Connect Enigma to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Enigma, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Enigma is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Enigma is connected, you configure its 19 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Enigma steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Enigma event fires, the agent kicks off automatically.
Every Enigma action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Enigma ships with 19 pre-built business intelligence actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Enigma together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Enigma-based workflows tailored to your business.