Create your account
Sign up with your name, your email, a password and a name for your account. That form creates your user and sends a verification email; it does not create a workspace yet. The workspace name it asks for only labels your account’s identity record internally: the guided onboarding is what actually creates your first workspace, from the business name you give it there. Submitting the form does not sign you in; sign in afterwards. You can also Continue with Google or Continue with GitHub. That signs you in right away and, on first use, also creates a workspace named after you (renameable in Configuration), the one shortcut where signing up and getting a workspace happen in the same step. Google verifies your email as part of the sign-in; with GitHub, as with the form, you verify it through the email wondeya sends. Either way you can sign in and build before verifying; only publishing waits for a verified email. You are the owner of a workspace you create. You can invite teammates later asadmin (can edit and publish) or member (can read).
The guided onboarding
Sign in with no workspace yet and wondeya opens the builder instead of an empty console. It is resumable: a workspace with no published page still sends you back here on your next visit, so nothing is lost by closing the tab mid-way. Explore wondeya on my own, next to the first step, backs out into the empty console at any point if you would rather build by hand.1
Business name
Type your business name. One call provisions a workspace, an agent, a project and a draft home page, and proposes your public address at
your-name.wondeya.app, checked live and renumbered automatically when it is taken (your-name-2, and so on). A handful of names are reserved by the platform: www, api, admin, app, console, cdn, widget, docs, mail, cname, status, blog, wondeya, woku.2
Tell us what you do
Describe your business, typed or spoken (wondeya transcribes audio for you). From that description, a model drafts your page’s hero copy and SEO metadata in both Spanish and English, plus your agent’s own conversational description of itself. This fails soft: if generation is refused or unavailable, your page simply keeps its plain fallbacks and nothing breaks.
3
Knowledge
Upload a document or add a URL the same way the agent’s Knowledge tab does later, because this step reuses that exact pipeline. Add as much or as little as you want now; you can always add more once you are inside the console.
4
Logo
Upload your logo and wondeya derives your favicon set, your brand colour (snapped to the closest Tailwind-700 shade) and your page’s Open Graph image from it. Skip it and wondeya generates a letter-in-circle monogram instead and derives the same set from that, so a business with no logo yet still leaves with a coherent brand.
5
Images
Upload the images your agent may show. Each one gets a vision-drafted description on the spot, the same pass the Assets tab runs later, so an image is usable in an answer the moment it lands.
your-name.wondeya.app serves it.
If you build by hand instead
Skipping onboarding, or working from a workspace you already have, means assembling the same pieces yourself in the console.1
Create a workspace
A signed-in account with no workspace lands on a one-field screen: give it a name (2 to 60 characters) and you are its owner. Skip this if you already have one.
2
Create your site
The console opens on Projects; create your first project from the empty state. A project is one site, with a name and a public address at
your-site.wondeya.app. A workspace can run several.The address is proposed live from the name (Winter offer becomes winter-offer) and you can type your own. It is checked as you type: it must be unique across all of wondeya, and the same names reserved for onboarding above are reserved here too. A taken or reserved name is refused with a suggestion you can accept.3
Create your agent
In Agents, create your first agent: the brain that holds the knowledge, the images and the identity it answers with. You configure it once, and it can answer on many pages and, through the widget, on sites you already have.
4
Upload your knowledge
Open your agent’s Knowledge tab and add the material it is allowed to answer from: documents (PDF, Markdown, plain text or Word, up to 10 MB each) and URLs (a page wondeya fetches and reads for you, on a cadence you pick: Once, Daily or Weekly). Documents are divided into topics automatically during indexing; curating that taxonomy, and writing claims by hand, is done over API v1 or MCP today, not from this tab. See Knowledge for the exact operations.Indexing runs in the background: a source appears as
Queued, moves to Processing, and lands on Ready with a chunk count or on Failed with a reason you can act on. An agent with no Ready source cannot answer anything yet.5
Add your images
In your agent’s Assets tab, upload the images it may show: PNG, JPEG, WebP, GIF or AVIF, up to 8 MB each.On upload, wondeya looks at each image and drafts a description of what it actually shows, plus its topics. Review it: that description is how the agent decides which image answers which question. An image with no description is one the agent will never choose.
6
Set your theme
In your project’s Brand tab, pick five colours (primary, accent, surface, ink, muted), a typeface for headings, a typeface for body text, and a corner radius. The preview beside the form is the real renderer, so what you see is what a visitor gets.Colours are 6-digit hex (
#6d28d9). Typefaces and radii are picked from a list the server owns: wondeya never accepts raw CSS, which is what keeps a theme from becoming a way to inject a stylesheet into a public page.7
Create a page
In your project’s Pages tab, create a page: a type and a path inside the site; a name can come later. A Conversational page is answered by the agent you pick; a Document page shows a markdown file as-is, with no chat, for things like a privacy policy.The path is typed, stored lowercase and unique within the site. Exactly one page lives at
/: it is the home page the site address serves, and the first page you create defaults to it. Platform names and every content language are reserved as the first segment and refused with a clear message.A new page is a draft. Drafts are invisible to the world: they answer 404 on every public address and answer nobody in a conversation, so you can build in the open without publishing anything half-finished.8
Talk to your own agent
In your agent’s Preview tab, ask the questions your customers ask. It runs the real engine against the knowledge and assets you just uploaded, still without publishing anything.If an answer is thin, testing retrieval over MCP (
probe_retrieval) shows exactly which passages a question pulls back and which half of the search found them; the console does not have that screen yet. It is the fastest way to tell “the agent is wrong” from “the material is missing”.9
Publish
Publishing is a deliberate act with its own button, not a field on a settings form. It is what opens the page to the world, so it requires a verified email.Your site’s address was proposed when you created the project, and it serves the page at
/, so that page must be published first: publishing any other page before it is refused with a message that says so. Once the home page is live, other published pages answer at your-site.wondeya.app/their-path. Moving a page back to draft takes effect on the next request.You can connect your own domain from the project’s Domains tab and verify it with the DNS records it hands you, but serving over a custom domain is not enabled yet; the wondeya.app address keeps working meanwhile.Put it on a site you already have
If you have a website, you can run the same agent inside it as an inline component: it sits in your page’s own flow rather than as a floating chat bubble. It is the ask block with the input and suggested questions, answering with the same generated interface as a wondeya page. Mark the spot in your layout with a container element and paste one tag, using a site key for the agent:What is not in this path yet
Being explicit about the edges, so you do not plan around something that is not there:- Lead form submissions. The agent can render a contact form, and today submitting it answers “this form is not enabled yet”. Collect contact details through a link or a CTA until it lands.