The internet learned how to answer machines.
It has not learned how to stand behind its answers. Machines read the open web and act on what they find — prices move, accounts close, claims are paid — while the infrastructure underneath can show only a URL and some bytes.
LENTRA gives every machine fact a passport: a signed record captured at the moment of observation, and an open tool that checks it without us.
field groups per record
signature over all of them
calls to us to verify one
Edit any value. The signature is re-checked in your browser on every keystroke.
Not faster. Not cheaper. Provable.
Humans read pages
Trust is habitual. An error costs seconds and stays on one screen.
Machines consume state
Trust must be provable. An error costs money and does not stay put.
Errors propagate
A wrong fact no longer stops at a page. It travels through every system that relied on it.
An error no longer stays on one page.
One stale fact enters a pipeline and keeps going: into a price, into a limit, into a report filed with somebody entitled to ask where it came from. Run it both ways.
Illustrative sequence, not measured data.
Solved. Providers reach almost anything.
Being solved. Rendering and scale are commodities now.
Still open. Nothing ships an object the buyer can hand to a third party.
Provenance cannot be reconstructed after the fact. It must be captured at the moment of observation, or it does not exist. A machine fact without provenance is just a claim.
Source. Time. Method. Context. Quality. Rights.
The object carries not only data, but the right to rely on it.
What actually answered?
The endpoint that really responded, after redirects, with the certificate it presented. A fact attributed to a domain must be traceable to the machine that served it.
When was it true, and was it live?
The instant of observation, established by a time source that is not our own wall clock, together with the cache posture. A timestamp tells you when you asked — not when the world looked that way.
How was it obtained?
Plain request, rendered browser or API call; whether scripts executed; what was interacted with. Two observations of one URL by different methods are two different facts.
From where, into which market?
Egress region, network class and market frame. The open web is not one place: price, availability and content are a function of where the observer stands.
How strong is the fact?
Status, content hash, size, and corroboration by independent observations. Provenance says where a fact came from; corroboration says whether one source should have been enough.
What may be done with it next?
The legal envelope travelling with the fact: basis, the pinned version of the terms, permitted and prohibited use, retention, jurisdiction. Rights should travel with the data.
Freshness is not metadata. It is part of the fact.
If the data came from cache, the machine should know it came from cache. Never present old state as fresh state. The same bytes, forty minutes apart, are two different facts — and only one of them justifies moving money.
Trust that requires permission to verify is not trust. It is dependency.
Verification works without us
The format is open, the verifier is open, and the check needs no account, no key from us, and no network call to us.
We bind our own hands first
Each record carries the digest of the one before it. A proof system whose operator can rewrite the past is worthless.
Issuance stays answerable
Anyone can verify. Responsibility remains with the issuer — and that responsibility is what is actually sold.
Open verification is not generosity. It is distribution.
History can change. It cannot change quietly.
Every record carries the digest of the record before it. Rewriting one entry does not quietly correct the past — it detaches everything issued after it. Click any record below and watch the chain answer.
A quiet edit is the failure mode this is designed against. It is not a promise; it is arithmetic.
Nothing in the stack answers this question.
| Layer | What it establishes | What it leaves open |
|---|---|---|
| Observability | Explains your system: traces, logs, latency. | Says nothing about the external fact the system consumed. |
| Governance | Tells you what the agent did. | LENTRA tells you what the agent knew. |
| Identity | Answers who acted. | LENTRA answers what they acted on. |
| Payments | Prove who paid. | LENTRA proves what justified the action. |
| C2PA | Proves where a piece of content came from. | LENTRA proves what a machine observed, and under which rights. |
| LENTRA | What the machine observed, when, how, from where, and under which rights. | Your policy decision. That judgement stays with you. |
AI systems need more than observability. They need evidence.
One line of integration. A permanent chain of evidence.
We do not replace your data provider — we make its output defensible. Execution providers are not competitors, they are the distribution layer. Easy to add, easy to remove, and everything already issued stays verifiable forever.
A standard has no right to lock the door behind the user.
- WEB_DATA_ENDPOINT=https://api.your-provider.com/v1 + WEB_DATA_ENDPOINT=https://gateway.lentra.io/v1/via/your-provider response body : identical response header : x-lentra-passport: lp_01J8Q4…
We do not sell data. We sell the right to trust a machine with a decision you are responsible for.
- Money is made on control, not traffic
- Execution is priced like a commodity. Accountability is not. Margin sits in passports, policy, journals and audit reporting.
- Pay for successful evidence
- A delivered, verifiable fact is billable. A provider's failed attempt is not.
- Failure is part of the audit trail
- We do not hide failure, we classify it. A refusal is evidence of what the system declined to rely on.
- A closed target stays closed
- We do not turn blocked sources into a technical challenge. Responsibility is incompatible with anonymity.
Willingness to pay follows the cost of being wrong, not the volume of traffic.
Standards do not win tenders. They win the habits of auditors.
SSL did not win because everyone loved SSL. It won because its absence became suspicious. A fact without a passport should eventually feel the same way. The company is not the standard — the format is the standard, and the company operates the responsibility layer around it.
The more consequential the decision, the more valuable the proof behind it.
Finance and scoring
A decision challenged months later needs its input reproduced, not described.
Insurance
Underwriting on external signals requires provenance that survives a dispute.
Security and brand protection
Enforcement rests on what was observed, when, and from where.
Dynamic pricing
Machine-set prices must be explainable per market and per moment.
Marketplaces and moderation
Action against a seller is only as strong as the record behind it.
Agent platforms
An agent acting on the open web is undocumented liability without provenance.
For regulated automation, proof is not a feature. It is permission to automate.
Early, and specific about it.
LENTRA is a working project, not a finished platform. The format is drafted and the verifier is public today; the gateway is in build; issuer keys are demonstration keys until formal custody is in place.
- Now Draft, open
- Passport format v0.1 and a public verifier that runs without us.
- Now In build
- Gateway in front of existing web-data providers. One line of configuration.
- Next 2026
- First deployments with regulated design partners; issuer keys under formal custody.
- Next 2027
- Auditors reading passports directly; the format enters checklists and procurement.
- Later 2028
- Data providers issuing compatible passports themselves.
Estimate. Dates state intent and sequence, not commitments already met.
Every machine fact, with a passport.
The end state is boring. Like SSL. Like a notary. Like a power socket. Infrastructure wins when people stop thinking about it.