Airtable attachment links expire. VibeKit's don't — your photos stay up.
Airtable's attachment URLs are temporary by design. The link the API hands you works today and expires later — quietly. Hot-link those images on a website and everything looks perfect at launch; come back after a while and your product photos, headshots, and logos have decayed into broken-image icons. No error, no warning, just gaps where pictures used to be.
Your photos should not have a half-life. VibeKit serves images on links that simply keep working, so a site that looked right on launch day still looks right months later.
Why Airtable images break
Every attachment URL Airtable returns is built to expire. That's fine inside Airtable itself, but anyone who copies those URLs into a website ships a page that silently rots. It's one of the most common ways an Airtable-backed site degrades — and because the images load fine at first, nobody notices until a visitor does.
Links with no expiry date
When your app reads records through VibeKit, attachment fields come back with VibeKit's own image links instead of Airtable's temporary ones. Each link is signed — it can't be guessed, and one app's images are never reachable from another — and the image is delivered through the proxy with long-lived caching, so it loads fast and keeps loading. Images get the same treatment as the rest of your data: served from cache, instantly (see edge cache).
On by default
There is nothing to switch on and nothing to configure. The data your agent receives already contains working image URLs, so it builds pages the ordinary way — an image tag pointing at a link that stays alive. The ready-made prompts VibeKit writes for your agent describe exactly this shape, so the first version it builds is already the durable one.
What that means for your site
No re-uploading attachments to separate hosting. No image pipeline to maintain. No discovering, three weeks after launch, that half your gallery is blank. Your photos stay up because the links underneath them never go bad.
Record-level security
Every request only ever returns the records that belong to the signed-in user — enforced on the proxy, not in the browser.
Request logs
Airtable keeps no record of individual API calls. The proxy logs every one — who called, what they read or wrote, and when.
Quick Proxies
A public link per record that serves one field: a redirect, an image, a file or a QR code. No app code.
Try it on your own base
Paste a token, point at a view, hand the prompt to your agent.