Enigma Technologies, Inc.

Energized to be at Clay partner day and hosting the Sculpt happy hour tonight in SF from 5 - 7:30 PM PST. GTM teams using Clay are building smarter account lists every day. We spend our time on the layer underneath: what a business actually looks like right now, how it's connected to the businesses around it, and whether it's still operating. If you're at partner day, come find J.T. Levin & Jake Olsen tonight for a drink and a conversation about the difference linked data makes for GTM teams. See you there.

Agents are being handed work that used to take an analyst. Research, enrichment, monitoring, diligence, and answers someone acts on. They are good at the reasoning part. What they cannot do on their own is resolve which business they are looking at, and that is not a model problem. The signal that separates two businesses does not live in any one dataset. We wrote about why resolution is the step that decides it, and why we joined TinyFish's Data Partners Alliance. https://lnkd.in/gutdgDAN

Agents are built to reason, not resolve. Reaching the data is the first problem. The second is knowing which business it belongs to. An agent that can't resolve a business doesn't throw an error. It returns an answer, and the next agent in the chain treats it as fact. Enigma is a founding partner in the TinyFish Partners Alliance. What we bring is business identity that arrives already resolved: the entity, its network, and the source behind every link.

Quantum Lending Solutions ran a head-to-head KYB comparison on 2,000 real records. Enigma returned a 90% match rate against roughly 80% from the provider they had inherited, while lowering direct costs by 35%. Further, Quantum Lending Solutions now sees 10% fewer applications landing in a manual review queue each month. 3 things decided the switch, according to Quantum Lending Solutions analytics and risk team: 1. Better data reduced operational cost, not just API costs: every point of match rate improvement is a case that never reaches manual review. The cost reductions were the line item however, the manual review savings were the multiplier. 2. Terms built for a mid-market lender: a structure fit for where the company is now, with room to adjust as volume grows, rather than an enterprise-tier minimum 3. A short path to production: documentation, test records, and a test environment, with no rearchitecting of the existing compliance workflow. If reducing manual reviews while improving match rates is on your roadmap, the full case study has the details on how to get started and to connect with our team: https://lnkd.in/eMpijt7B

Leading up to our September 15 rooftop event, we've been reading up on authorization tied to current data, if this is on your radar, signup to join the conversation -> https://luma.com/3wruxqtb "To an institution seeing only its own data, a repeat offender looks like a first-time visitor every time." That quote from Liminal's Identity Fraud Intelligence report stood out to us and should stop anyone running point-in-time third-party risk or vendor verification. In the same research, Liminal and Unico traced 949 identity documents back to one entity, an actor who had targeted 30 separate businesses. Here's the problem: you cleared that business against what you could see, on the day you looked. You had no way to know that actor has already closed their operating business, and you lack the data to know when  the company you approved changed. Because it does change. New controlling parties. A license revoked in one state while operations continue in another.  A website gone with an ominous warning on Google “Permanently Closed” That's just the ordinary churn of legitimate businesses. You didn't get it wrong at onboarding. The answer stopped being current, and nothing in a traditional KYB stack is watching for that. Most institutions bought a system that catches fabricated businesses at the door, and assumed it also told them whether a real business was still what it was. Those are two different jobs. The annual refresh most teams rely on is just a snapshot, sometimes eight months stale by the time it runs. The solution isn't checking more often. It's having live signals to act on, and the trust to actually act on them.

Leading up to our September 15 rooftop event, I've been reading up on authorization tied to current data, if this is on your radar, signup to join the conversation -> https://luma.com/3wruxqtb "To an institution seeing only its own data, a repeat offender looks like a first-time visitor every time." That quote from Liminal's Identity Fraud Intelligence report stood out to me and should stop anyone running point-in-time third-party risk or vendor verification. In the same research, Liminal and Unico traced 949 identity documents back to one entity, an actor who had targeted 30 separate businesses. Here's the problem: you cleared that business against what you could see, on the day you looked. You had no way to know that actor has already closed their operating business, and you lack the data to know when  the company you approved changed. Because it does change. New controlling parties. A license revoked in one state while operations continue in another.  A website gone with an ominous warning on Google “Permanently Closed” That's just the ordinary churn of legitimate businesses. You didn't get it wrong at onboarding. The answer stopped being current, and nothing in a traditional KYB stack is watching for that. Most institutions bought a system that catches fabricated businesses at the door, and assumed it also told them whether a real business was still what it was. Those are two different jobs. The annual refresh most teams rely on is just a snapshot, sometimes eight months stale by the time it runs. The solution isn't checking more often. It's having live signals to act on, and the trust to actually act on them. Enigma Technologies, Inc. + Proof + Liminal can't wait to see you on September 15

🔒 You already trust this icon enough to hand over your credit card number. Why not your invoices? Every HTTPS padlock is backed by a certificate authority proving who's really behind a website. Business Certificates use that same technology on companies: a continuously verified identity, bound directly to a document the moment it's signed. Tamper with it afterward, and the seal breaks. We recently demoed it live with Enigma Technologies, Inc.: what a certified invoice looks like, and what happens the second someone tries to alter it. 📝 🔗 Link to catch the session on-demand in the comments.

Regulators in several states are now treating med spas as medical clinics, meaning they must be specially registered and licensed. On paper, most of these med spas are still just salons, but the procedures they offer (injectables, lasers, peels) are medical, and oversight is finally treating them that way. So we looked at how 12,646 med spas describe themselves in their own filings. 85.9% classify under a beauty-industry code, the same bucket as nail salons and day spas, rather than a medical one. In New York, 87.9% of traditional medical practices register as professional corporations, the structure the state requires for physician-owned medicine. Among med spas, the pattern flips: most file as standard LLCs. Even though plenty of med spas certainly run compliant management-services structures, the industry codes that represent these businesses are still self-reported. So when a business offering medical procedures files like a salon, that gap is exactly what a registration-only KYB check waves through, and exactly what regulators are now chasing. Registration tells you what a business calls itself. Not what it does. Read our full analysis: https://lnkd.in/eG846frq

A KYB check is a timestamp: true the day you run it, trusted for months after the business changes hands, loses a license, or faces sanctions exposure. That gap is the #2 fraud category in the U.S., part of $212B in suspicious activity, according to Financial Crimes Enforcement Network, US Treasury research. Today we're announcing our solution with Proof to close it. Business Certificates bind continuously verified business identity (Enigma) to the people and systems authorized to act for it (Proof), then cryptographically sign that identity into every wire, contract, and piece of content the business puts into the world. The timestamp problem becomes a non-issue when verification stays current and every action is signed. You can read more on the partnership in our latest article -> https://lnkd.in/gBmEePKg Want to learn more about Business Certificates, use cases, and get your questions answered live? Join our CTO Ryan Green and Proof's CTO Eric Fleischman & Sr. PM Abbie Kaiser Thursday July 23 → https://hubs.la/Q04nXSGX0

So excited to partner with Hicham and the Enigma Technologies, Inc. team. We talk a lot about identity, but commerce and trust sit at the intersection of two parties. One is most often a business. People must know they're doing business with who they intend to. Proof now ensures the businesses on our platform are vetted and verified. Business identity is also being threatened by the same forces as personal identity - forgery, false records, fraudulent statements, email compromise. Every organization must claim their identity online to protect their own brand, voice, data, and financial flows. Proof's business certificates and content certification tackles things like business email compromise, request for payment fraud, false records, and so much more. We believe x401 will soon be the standard for agentic authorization and it's critical that businesses can participate too, certifying agentic commerce in their name.