Every AI product cites the passage it built the answer from. That catches invention. It does not catch a real citation from a bad source. Lens closes that gap at the document and claim level, on in-house models, with the evidence attached to every flag.
Retrieval traces the answer back to a real passage. It does not audit what that passage is worth. Lens does, per document and per claim, with the reason exposed for every score.
of new English-language online articles are AI-generated. Your retrieval index is drinking from that river.
Graphite, Q1 2026mean rate at which AI-judge verdicts flip between two identical runs. Grounding a bad source in a citation just launders it.
arXiv, 2026third-party document-level standards your framework can call today. That is the seat this program opens.
The gap Lens fillsFull evidence-attached scoring output, delivered through the integration surface that fits your stack.
Standing working session with the engineering team. What ships next is shaped by what your framework actually calls, not by a survey.
A named engineer on the Lens applied research team, same time zone as your integration lead. Not a shared inbox.
Multiple integration surfaces sized to your stack. Wired end to end with your team on the shape that fits.
A per-call rate held for the duration of the cohort. Volume ceiling agreed in advance. No surprise metering.
Some partners prefer quiet through the term. The program does not require the logo.
A running integration seeing production shape and volume, not a proof-of-concept parked on a branch.
Thirty minutes on the agreed cadence. What was called, what worked, what did not, what to change. Engineering team on every one.
Anonymized. Distributional. Never a specific user query. Terms written into the program agreement.
A call with the next cohort or a quote after program close. Both optional.
Draft an email with the two sentences below and the one integration surface you have in mind.
Thirty minutes with the applied research team. What you are building, where the check would sit, what would count as working.
Keys issued and your integration surface stood up. First calls verified end to end with your team.
First real calls. First working session. First look at the roadmap you now have a seat at.
Terms are negotiated per partner and written into the program agreement. Details on the intro call.
Private deployment is handled on the enterprise track. Start on the enterprise page.
Set per partner in the program agreement, sized against integration depth. Two-weeks notice on either side is the default exit clause.
The engineering team. Every application, read within one business day.
Fill this in and it goes straight to the Lens team. Every application is read within one business day.
Two other lanes are open. Send a campaign log and get a pilot audit back, or talk about verification inside a regulated stack.