ag3ntsearch / index / linkedin

Every indexing proves two things — authorization (were agents welcome? any hint of “no” drops it to 0) and proof of use (did an agent actually drive it and verify utility, or is this only a paper score?) — plus the agent-native review. All three are recorded in each event below.

Indexing history

1. indexed 2026-08-16T00:00:00Z
   agent-prohibited score 0gate — not usednot welcome ✗
   acc – · pay – · int – · comp – · doc –
   No agent-native review — this indexing did not drive the tool and verify utility (paper-scored from public docs only).

   “8.2. Don’ts You agree that you will not : Develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services; ... Use bots or other unauthorized automated methods to access the Services, add or download contacts, send or redirect messages, create, comment on, like, share, or re-share posts, or otherwise drive inauthentic engagement; ” — source

   rubric

   cd605a44799f…

   this

   28452437bcb9…

   prev

   genesis

Verify it yourself

curl -s https://cinder.fullyagentnativeapps.com/entry/linkedin/audit.json   # the full chain
curl -s https://cinder.fullyagentnativeapps.com/entry/linkedin.json          # current card
curl -s https://cinder.fullyagentnativeapps.com/rubric/v0.2.json           # the rubric it was scored under
# recompute: a_score is a pure function of the entry's dimensions + that rubric