Developers

A name goes in.
The business comes back.

One GraphQL endpoint resolves a brand, a legal entity, or an operating location from the same query — and returns the record behind the answer, not just a yes.

Read the docs ▸Open the console ↗

~1.5s

median KYB response, v2 API

92%

match rate with a person's name

for searches that don't match

query {
  brand(name: "blue bottle coffee", state: "CA") {
    name
    legalEntities {          # 2
      name
      registrations {        # 40, across 29 states
        jurisdiction
        status
      }
      officers {             # the people attached
        name
        role
      }
    }
    locations {              # 99 operating
      address
      operatingStatus
      cardRevenue12m
    }
  }
}

Blue Bottle Coffee — fixture values, matching the resolution graph

The graph, without a diagram of a graph

The query and the traversal are the same shape.

In GraphQL you write the shape of the answer you want, and nesting depth is how far the traversal goes. So the graph does not need illustrating — it is what the query already says, read sideways.

One query

Nesting depth is traversal depth

query {
brand(name: "blue bottle coffee") {
name
legalEntities {
name
registrations {
jurisdiction
status
}
}
locations {
address
cardRevenue12m
}
}
}

You write the shape of the answer you want. The shape you wrote is the traversal.Blue Bottle Coffee — fixture

One endpoint, two products

Coverage first. The filing when you need it.

Both products answer the same call. What changes is how much of the record comes back with the answer.

Identify

Confirms a business is real, not just registered.

The resolved business — legal names and the DBAs it trades under
Operating locations, and the card revenue observed at them
The sources behind each attribute, so the answer can be cited

For onboarding at volume: marketplaces, platforms, and anyone whose applicants are real businesses that never filed anything interesting.

Verify

Adds the full Secretary of State record.

Everything Identify returns
Corporate registrations, status, and the officers on the filing
Watchlist hits against the business and the people behind it

For regulated programs where the filing itself is the evidence: banks and sponsor banks, lenders, and payments compliance.

One credit is one cent, and every rate is published. Filters bill on each business you screen; attributes bill only on the fields that come back, so an empty field costs nothing. A free tier covers browsing, search and preview.

See full pricing →

What you can resolve

The same call, whatever you have to go on.

You rarely get a clean legal name. The graph is built so a brand, an address, or a person's name is enough to land on the right business.

InputWhat comes backTypical use

BrandA trade name, with or without a stateThe brand, and the legal entities and locations that sit behind itMarketplace and platform onboarding

Legal entityA registered name, or a name plus a stateRegistrations and officers, and the DBAs the entity trades underRegulated KYB and diligence

Operating locationA street address, or a business name plus an addressThe location, the brand it belongs to, and card revenue observed thereMerchant underwriting and site checks

PersonA person's name alongside the businessA higher-confidence business match, plus officers and watchlist hitsBeneficial-owner and officer screening

Screening runs at 1B+ requests a month, in real time, across wires, ACH, and P2P.

Agent-ready

Let the agent check
before it answers.

The same resolution is available over MCP through the enigma.verify tool. An agent asks whether a business is real, Enigma resolves it against the record, and the answer arrives carrying its sources — grounded, not recalled.

MCP access is available on the Max plan and above.

See plans →

agent session · mcpenigma.verify

Surfaces