Register a paper with an agent
This procedure explains how to list a released paper in the registry. The paper must already be released in APP format. To prepare a release, see Publish your paper.
An AI coding agent submits a paper using the same workflow as a user on the Submit page. The user authenticates through GitHub, and the agent sends an HTTP POST request.
Because an agent does not have a web browser, the agent uses the GitHub device flow. The issued OAuth token permits the registry to read only the user GitHub username and repository write permissions. The registry rejects all other tokens.
The user must accept the terms of use before submission.
Request a device code from GitHub for the registry. The response contains a
device_code, auser_code, and anintervalin seconds.Terminal window curl -s -X POST https://github.com/login/device/code \-H "Accept: application/json" -d client_id=Iv23lil5JFiVHrgYwNB5Instruct the user to open github.com/login/device, sign in, and enter the
user_code. The registry requests read access only to public profile information and repository permissions.Exchange the device code for an access token. Repeat the request every
intervalseconds while the response status isauthorization_pending, until GitHub returns anaccess_token.Terminal window curl -s -X POST https://github.com/login/oauth/access_token \-H "Accept: application/json" -d client_id=Iv23lil5JFiVHrgYwNB5 \-d device_code=DEVICE_CODE \-d grant_type=urn:ietf:params:oauth:grant-type:device_codeSubmit the release URL. Set
"accept_terms": trueonly after the user accepts the terms of use. If the user does not have write access to the paper repository, set"authors_permission": trueonly after the user confirms author approval.Terminal window curl -s -X POST https://yacpfzqrybwyfdkckvsb.supabase.co/functions/v1/registry/submit \-H "Authorization: Bearer ACCESS_TOKEN" \-d '{"release_url": "https://github.com/OWNER/REPO/releases/tag/TAG", "accept_terms": true}'
The API response from the final step includes the submission issue number. The registry runs automated verification checks and posts review results in that issue. The repository is public, so you can read the comments without authentication:
curl -s https://api.github.com/repos/LionSR/app-registry/issues/<number>/commentsIf the GitHub CLI is authenticated, gh issue view <number> --repo LionSR/app-registry --comments shows the same comments.
Each registry bot comment includes a JSON block labeled app-registry-status that specifies the status.
To read all registry entries, fetch papers/index.json or llms.txt.