Agentic commerce readiness report
The visit in detail
Loading…
This couldn't be shown here. Open it as a page
- Why it matters
- It ties each agreement to the exact terms you published.
Fix
Developer · WeeksPlan step 4Waits on A checkable record of each agreement
Write the published terms' digest into every agreement record.
How Lens checks this next time: The agreement record contains your published terms' hash.
Where it sits
Agreement record · Provable needs bothThe record · R10.3 · not_met · 1 request
- Reason
- No agreement record passes the buyer gate (R10.2): No payment challenge Lens met declares an agreement record's hash.
- Requests
- 0x6a63…851a
- Standards
- LCP §2.5 · LCP §5.3
- Definition
- 0xcd423080a88aa39130d605cf372f3272cc5a95c32788af54d807cfb81cee0d93
- Identities
- anon
- Vantage
- cf-worker