ag3ntsearch / index / github-api
sha256 of the event's sorted-key canonical JSON; each links to the one before it.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.
“H. API Terms — You agree to these Terms of Service, plus this Section H, when using any of GitHub's APIs (Application Programming Interface), including use of the API through a third party product that accesses GitHub. H. — Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. H. — You may not share API tokens to exceed GitHub's rate limitations. H. — You may not use the API to download data or Content from GitHub for spamming purposes, including for the purposes of selling GitHub users' personal information, such as to recruiters, headhunters, and job boards. B.3 Account Requirements — Accounts registered by "bots" or other automated methods are not permitted. B.1 Account Controls — A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. ” — source
curl -s https://cinder.fullyagentnativeapps.com/entry/github-api/audit.json # the full chain curl -s https://cinder.fullyagentnativeapps.com/entry/github-api.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