Lentra
Home / Use cases

Is this you?

Nobody wakes up wanting provenance infrastructure. People wake up to one of these six mornings instead, and most of them do not yet know they are our client. If one of these reads like your calendar, this product was built for you.

01 · The publisher

Your traffic report is down again, and an AI answer above the search results is quoting yesterday's exclusive, unattributed.

Today

The server logs show a storm of fetches under generic user agents. The blocking dashboard says "mitigated". Nothing you hold tonight would survive ten minutes with opposing counsel.

When it breaks

Your lawyers ask for evidence of the taking. What exists: screenshots, a vendor dashboard you cannot export, and log files nobody signed. The case you know is real starts from almost nothing.

With records

Every machine visit since the capture node went in is a signed, chained record: the claimed agent, the real network, the content digest, and your robots.txt state at that exact second. Counsel starts from exhibits, not from anger.

02 · The IP litigator

You are drafting a complaint you know is true and cannot yet prove.

Today

Attribution collapses into "upon information and belief". The strongest exhibits were produced by your own team after the dispute began, and you know exactly how courts have been treating those lately.

When it breaks

Discovery becomes expensive roulette. Canary content and third-party subpoenas can carry a case, but they take months and depend on other people's cooperation.

With records

Your client's node hands you contemporaneous records the opposing expert verifies on their own laptop, offline. The staging argument dies before it is made, and the fight starts on the merits.

03 · The licensing lead

The AI company across the table says: show us that we took anything at all.

Today

Industry reports say reservations are ignored at scale, and you believe them. But for your own domains, specifically, this quarter, you hold nothing you could put on the table.

When it breaks

The negotiation stalls exactly where it always stalls: your leverage is a market narrative, theirs is your missing evidence.

With records

The taking, quantified and signed: which agents, which pages, how often, against which reserved uses. The conversation changes shape from whether to how much.

04 · The platform

Your terms prohibit scraping for training. This morning's crawl did not read them.

Today

Enforcement rests on canary listings, user reports and subpoenas to intermediaries. Every enforcement action turns into a credibility contest about what your own logs mean.

When it breaks

An industrial-scale scraper laundered through proxies is winning against a terms-of-service page, because the terms cannot testify.

With records

Ingress records put the platform's evidence on the table first: portable, signed, independent of anyone's cooperation. Terms become enforceable the moment their violation becomes provable.

05 · The AI provider

The regulator's letter asks how your crawlers honour reservations. Your answer is currently prose.

Today

The copyright policy says the right things. The proof behind it is internal logs no outsider has any reason to believe, written by the party they incriminate or exonerate.

When it breaks

An inquiry under the AI Act, a discovery request, a plaintiff's expert: each one asks the same question, and "trust our logs" is not an answer any of them accepts.

With records

A signed crawl ledger: reservations honoured, requests refused, every refusal kept as evidence of restraint. The inquiry is answered with records the asker can verify without you.

06 · The agent platform

Your agents fetched two million pages yesterday. Legal just asked which ones, and under what terms.

Today

Every fetch an autonomous agent makes is liability the platform inherits. The audit trail is whatever the agent framework happened to log, reconstructed after the question arrives.

When it breaks

One agent, one disallowed source, one consequential action later: the platform is explaining machine behaviour it cannot document.

With records

Agent traffic is passported at the session level: what was taken, from where, against which terms, and what the model was told. Auditable afterwards, instead of trusted in advance.

Not on the list?

The pattern matters more than the job title.

Every case above is the same sentence wearing different clothes: machine traffic touched something you answer for, and when the question came, you had a story where you needed a record. If that sentence lands, the rest of this site is for you.