Machine-readable, user-authorised
What the apps can do
6 verified operations across 8 independently owned apps. Each row names the real transport, its availability and what it needs. Each entry describes an operation. Your agent still needs the app's own identity and allowlist.
Reviewed 2026-11-07. App-owned declarations and client execution remain separate work; see the boundary notes below.
Link Check
2 documented operations.
Verified operation set · Storage: no stored records.
- inspect-page POST /api/inspect · Public read
Read one public HTTPS page and return bounded metadata, icon, share-image and discovery findings. Raw HTML only.
Needs: public-https-url. Verified 2026-11-06.
- read-health GET /healthz · Public read
Read public liveness and the exact deployed source revision. It does not query storage or prove a user journey.
Needs: none. Verified 2026-11-06.
Here / there
3 documented operations.
Verified operation set · Storage: the app owns its records.
- read-invitation GET /r/:resource/api/invitation · Public read
Read one visitor book's current invitation state, contribution limits and exact form paths. It never returns the guest code or private media.
Needs: none. Verified 2026-11-06.
- list-public-items GET /api/items · Public read
Read only the currently public, approved contributions. Pending, hidden and deleted items are excluded.
Needs: none. Verified 2026-11-06.
- submit-postcard POST /r/:resource/api/guest-postcard · Guest invitation
Submit one short postcard for owner review. Requires the app-issued guest code, explicit consent and a browser-rendered PNG; it cannot publish, moderate or read private records.
Needs: guest-invitation-code, consent. Verified 2026-11-07.
Linkarooie
1 documented operation.
Verified operation set · Storage: the app owns its records.
- read-public-profile GET /p/:handle/ · Public read
Read one explicitly published profile snapshot. Draft profile edits and owner configuration stay private.
Needs: none. Verified 2026-11-06.
LDraw
No remote operation is published. Use the app interface or its local files.
Limited claims · Storage: this browser only.
Paperwork
No remote operation is published. Use the app interface or its local files.
Verified operation set · Storage: this browser only.
Carry / forward
No remote operation is published. Use the app interface or its local files.
Limited claims · Storage: this browser only.
Launch Kit
No remote operation is published. Use the app interface or its local files.
Verified operation set · Storage: this browser only.
Hello World
No remote operation is published. Use the app interface or its local files.
Limited claims · Storage: no stored records.
What this catalogue cannot do
- It does not grant an agent access, a credential, a token or a reusable guest code.
- It does not execute an operation, schedule one or approve a change. Effect operations still need their own app-issued permit and confirmation.
- It does not make an unavailable app available. A limited app says so and keeps its own release boundary.
- It is not a second app registry. The manifest, composition and release controls remain authoritative.
Related: agent fit assessment, trust boundaries, release practice. App-owned capability declarations are tracked in the repository backlog.