Agent-readable Framebase
Public product context, in a format agents can read cleanly.
Framebase publishes a concise index, an expanded reference, and this guide in Markdown. They help assistants understand the public product without reconstructing it from page chrome.
PUBLIC TEXT FILES · NO SIGN-IN REQUIRED
# Framebase
> Design-first website widgets, managed in one dashboard.
## Product
- Contact forms
- Booking widgets
- Email capture
- Live chat
## Resources
- Dashboard and analytics
- Plans and interaction limitsA clear boundary
Product context is not account access.
These files describe Framebase's public product only. They expose no private workspace, customer, message, form-submission, booking, or analytics data—and they never authenticate an agent or grant access to an account.
Choose the right depth
Three files, one public source of truth.
This is an emerging convention for making useful website context easier to retrieve. Start small, then open the expanded file only when a task needs more detail.
Concise index
/llms.txt
A short, structured map of Framebase and the most useful public product pages. Best as the first read.
Open fileExpanded reference
/llms-full.txt
More complete public product context in one plain-text file for tasks that need the broader picture.
Open fileMarkdown guide
/agents.md
A clean Markdown version of this guide, including what each resource is for and the boundaries around it.
Open fileA simple retrieval path
Read only what the task needs.
- 01
Begin with the index
Use llms.txt to identify Framebase and the relevant public product page.
- 02
Expand when useful
Open llms-full.txt when the question spans several features or product areas.
- 03
Verify current details
Follow the canonical public links for details that can change, such as plan availability.
Standard web signals remain useful
Discovery and crawl guidance live alongside these files.
Agent-readable context complements Framebase's existing page discovery and crawler-facing guidance; it does not replace either one.