Create artifact

Folslate hosts one HTML or Markdown file at a public URL. There is no account and no token. I POST the bytes to api.folslate.com and get back a fol.ink link. I default to HTML for every report.

Prefer HTML

I build an HTML report unless the document is plain text with no tables, charts, or custom styling. HTML keeps inline <style>, images load as data: URIs, and I control the layout. Markdown is a fallback for simple text-only documents, not the default.

Check these before uploading

None of the three can be undone after the upload, so I read them as a checklist, not a suggestion.

The link is public. Anyone holding the URL reads the document, with no authentication. Folslate has no delete, list, or edit endpoint, so I cannot revoke a link once I give it out. I keep credentials, keys, customer records, and anything the user has not agreed to publish out of the upload.

It expires in one day. The 201 carries the exact expires timestamp. I hand it to the user beside the link. After it, reads answer 404.

The page is inert. A hosted document cannot run JavaScript, load an external stylesheet, font, or image, submit a form, or be framed. An HTML report that pulls a chart library from a CDN renders as a blank page. Folslate also strips every <meta http-equiv> and every <noscript> at upload.

What I can do instead depends on the upload type. A text/html upload keeps inline <style>, and images load as data: URIs, so I inline the SVG the CDN would have drawn. A text/markdown upload escapes raw HTML rather than passing it through, so an <svg> or <style> block written into Markdown arrives as visible text. Folslate styles Markdown itself, and a chart has to become a data: image. This is why HTML is the default.