There is no API yet. There are, however, a handful of plain URLs that do useful things right now — no key, no signup, no library.
Everything below is public and works today.
Every page has one address, and it never changes. Sub-pages hang off the same name.
exclusively.me/yourname
The one to print, pin and put in a bio. Case does not matter and there is no trailing slash to get wrong.
exclusively.me/yourname/menu
Any sub-page you have created, by its slug. Pro accounts can have up to ten.
Add /qrcode to any page address. You get an SVG by default, which is what you want for anything that will be printed — it stays sharp at any size, from a business card to a van.
/yourname/qrcode
Vector, brand-coloured, with the Beacon mark in the centre. Send this one to a printer.
/yourname/qrcode?format=png&size=600
For anywhere that will not take an SVG. Sizes from 80 to 2000 pixels; the result is snapped so every square lands on whole pixels and scanners stay happy.
/yourname/menu/qrcode
Each sub-page gets its own code, so you can tell which poster, table or leaflet people actually scanned.
At 300dpi, 600px is about 5cm square and 2000px is about 17cm. For a code people scan from a metre away, aim for 4cm or more.
Add /card to any page address for a PNG with your avatar, your name, your link and your QR code on it. Your page already uses one as its social preview — this is how you get the file for anything else.
/yourname/card?style=og
1200 × 630. The default, and the shape link previews use.
/yourname/card?style=square
1080 × 1080. For a grid post or a profile grid.
/yourname/card?style=story
1080 × 1920. Full height, for a story or a reel end card.
/yourname/card?style=label
800 × 1000, portrait, code-forward. Sized for a shelf card, a table tent or a window sticker.
Cards are generated once and kept. Change your name or photo and the address changes with it, so you never have to clear anything.
Codes and cards point at the page, not at a link. A link that is paused or out of its dates simply is not on the page that day.
Asking for the code of a page that has not been published gives you a page explaining why, rather than a broken image.
These endpoints are public and unmetered because that is friendlier. Fetch what you need, cache it your side, and it stays that way.
A read and write API is on the roadmap, and it is deliberately not half-shipped: authentication, tokens you can revoke, and rate limits worth the name are the price of entry, not extras. Until those are ready, /api answers 404 rather than offering something that might change under you.
Tell us what you are building and it will shape what gets built next.