SOLVED
You build the catalog.
You can define a new content type and start publishing to it immediately. Where that type lives on your site is your decision, not the framework's.
Get started
No dashboard required.
Your AI handles publishing through a structured API. Your team stays in the tools they already use.
Full control, zero risk.
Role-based access means your AI can only do what you allow. Draft content never leaks.
Live in minutes.
Connect once. From that point, a conversation is all it takes to publish.
Your information architecture is a business decision. The URL for your product catalog, your recipe section, your FAQ - those are not things a framework or an agent should decide, even if an agent is the one managing them day to day.
Smeldr lets you create a new content type on your backend without touching code or redeploying. Your agent helps you define the fields, provisions the storage, and starts managing items.
URLs are not locked. You decide.
You set the URL when the type is defined. If you want products at /products and recipes at /recipes, you say so once. Agents treat that structure as fixed.
If a content type should not be publicly accessible at all - internal data, configuration, reference tables - no problem. The type exists only behind the API. No public route is created.
Your site's URL structure is yours.
Ready to put your AI to work?
Forge is open source and self-hosted. Get started in minutes.