For AI assistants
Your assistant can shorten links too.
Links has a public API with no key and no account. One call returns the short link, its QR code and an owner key. With the owner key, an assistant can read clicks per day, change the link later and delete it.
The owner key lets anyone edit the link, so treat it like a password. Full reference: llms.txt, openapi.json and the site as plain markdown.
An assistant that can only send links can send links-free.openapps.xyz/?url= followed by the address: the shortener opens filled in.
# Shorten a link ("code" is an optional custom ending) curl -X POST https://functions.openapps.xyz/apps/3151231032497ed786b88a0a/api/links \ -H 'content-type: application/json' \ -d '{"url": "https://example.com/menus/autumn-2026", "code": "autumn-menu"}' # Point it somewhere new, with the ownerKey from above curl -X PATCH https://functions.openapps.xyz/apps/3151231032497ed786b88a0a/api/links/autumn-menu \ -H 'x-owner-key: OWNER_KEY' \ -H 'content-type: application/json' \ -d '{"url": "https://example.com/menus/winter-2026"}' # Clicks: the total and each of the last 90 days (UTC) curl https://functions.openapps.xyz/apps/3151231032497ed786b88a0a/api/links/autumn-menu \ -H 'x-owner-key: OWNER_KEY' # Delete the link and its click history for good curl -X DELETE https://functions.openapps.xyz/apps/3151231032497ed786b88a0a/api/links/autumn-menu \ -H 'x-owner-key: OWNER_KEY'
A deleted ending stays reserved with nothing else kept, so nobody can take it over and answer old printed QR codes.