WEB DATA & EXTRACTION · FOR AI AGENTS
Enigma
Look up U.S. businesses, legal entities and card-revenue signals through API or MCP.
Enigma connects agents to a maintained U.S. business graph, including brands, operating locations, registrations and card-transaction analytics. Its remote MCP tools support business research while GraphQL provides a programmable data interface.
Your integration checklist
- Capabilities
- What you need from your owner
- Create an Enigma account, choose a plan covering the required interface and obtain an API key. Current pricing places API access in Pro and MCP access in Max; confirm account entitlements and credit limits.
- Authentication
- Key-based MCP uses x-api-key at https://mcp.enigma.com/http-key. The separate https://mcp.enigma.com/http endpoint supports browser authentication.
- Your first task
- Match one business using its name, official domain and location, then inspect the returned brand and legal-entity identities before requesting additional attributes.
- Billing & payment
- Plans include credits; data pulls charge by returned attributes or the selected check. Some screening operations charge per request. Free Console viewing does not establish free API or MCP access.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- The remote MCP is labeled beta. Card revenue can represent only part of total revenue. Coverage, observation periods and account limits vary; a brand, location and legal entity are different records.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Resolve the business entity before buying enrichment
Editorial recommendation · Reviewed 2026-11-03
When to choose this service
Choose Enigma when U.S. business identity, registrations or card-activity signals are essential. A general web search may be sufficient for a company’s public product description.
Business-resolution infrastructure and maintained commercial data supply records outside an agent’s context. A local enrichment script still needs that external corpus and its collection relationships.
Suggested workflow
- Start with a precise name, domain and address. Check the matched entity type and reject a similarly named business in another location.
- Select only attributes needed for the task. Review per-fill versus per-request pricing before expanding a list or requesting screening data.
- Keep observation windows and entity IDs with the output. Compare card metrics only on a compatible basis and corroborate consequential business claims with additional evidence.
Acceptance checks before real work
- Card revenue is not automatically the company’s total revenue.
- An empty field is unknown, not a zero value or a clean screening result.
- Confirm that location-level data has not been mistaken for the entire brand.
If the workflow fails
Honor Retry-After on throttling and distinguish a daily limit from a short burst limit. Recheck match inputs before paying for another enrichment; preserve unresolved identities rather than merging them by name.