Anonymous public pages
artifuncs occasionally picks community-published tools and exposes them at artifuncs.com/f/{handle} so search engines and curious visitors can try them without signing up. This page explains how that works.
Who decides
Admins. Authors don't opt in or out individually — publishing implies consent for artifuncs to feature the tool. If your tool isn't suited for anonymous use (private data, expensive operations, regulated content), tell us during review and we'll keep it off the public list.
What anonymous visitors see
- The tool's name, description, and (if you filled them in) the SEO description and share image from the Sharing tab of your tool's edit page.
- A run button. Each visitor gets a free quota — by default 10 runs of a given tool per hour, capped at 30 runs total across all tools per session. After that, a sign-up CTA replaces the run button.
What anonymous visitors can NOT do
- See your draft. Only the exact version admins pin (the anon-pinned definition) is served — never the latest draft or any work-in-progress.
- See other visitors' files. Each visitor's uploads land in a private per-session directory; cross-session reads return 404.
- Spin up unrestricted code. Tools run inside isolated sandboxes with rate limits and short timeouts.
Why your handle is permanent after first publish
Public URLs (artifuncs.com/f/{handle}) are SEO assets — renaming would break inbound links and de-rank the page. Behind the scenes, the handle also routes the tool to a specific sandbox pod, and renaming would invalidate the warm cache there. The handle lock at first publish is a one-way door.
Updating an anon-published tool
You keep developing as usual — push commits, publish new versions. The version visible to anonymous visitors only changes when admins flip the pin to the new version. They'll typically do that after a fresh review.
SEO fields
- SEO description (≤ 200 chars). Used in search-engine snippets and OpenGraph/Twitter link previews. Write one clear sentence about what the tool does.
- Share image path (1200×630 looks best). Used as the OpenGraph and Twitter card image. Leave blank to use artifuncs's auto-generated card.
You can edit both at any time. Changes are picked up immediately.
Rate limits and abuse
If your tool ends up driving heavy anonymous traffic, the rate-limit defaults apply per visitor, not per tool — so legitimate use scales linearly. Abuse (one visitor cycling through cookies, etc.) is bounded by the per-session global cap.