Everything a developer needs to know, on one page.

Start in ten minutes

A new account opens on a checklist that ticks itself. These are its steps.

1. Create the account. Your company name, your e-mail, a password, and a sign-in code by mail on every new device. The account is the company; colleagues join it later.
2. Put credit on it. Billing → Top up, from $10 by card. Everything the agent does is paid per step from this credit; there is no subscription and unused credit never expires. A starting credit may already be there when we switched it on for new accounts.
3. Enable T-Builder and add the site. Products and sites → enable T-Builder → add a site by its name. You get a key; it is shown once, copy it.
4. Install the plugin. Download it next to the key, install it on the site like any plugin, paste the key in its setup. Staging first if you have one. The plugin updates itself from then on.
5. Open a project. Projects → the site. Write down what the agent should know about it, drop a template in, and say what you want in the chat.

The checklist on your overview shows which of these is still open and takes you there.

Sites and keys

A key belongs to one product and one site. It is what the plugin uses to talk to your account, and it is how usage is metered: your statement lists every site on its own line because every call carries its key.

• One site, one key. Never reuse a key on a second site; add the second site and give it its own.
• Revoke blocks one site. Revoking a key stops that site that moment and nothing else. Make a new key and paste it to connect again.
• Tools per site. On a site's card you switch tools off that the agent may not use there, for example plugin installs on a client's production site.
• Nothing is published by the agent. Pages, templates and themes land as drafts. You review in WordPress and publish.

Projects and chats

A project is one site and everything the agent knows about it. Its tabs: Chat, Knowledge, Schedules, Activity, Site, SEO.

Knowledge

What you write under Knowledge is read before every answer: the client, the tone, the components, what not to touch. Account-wide knowledge under Preferences applies to every project; skills are how your agency does a job, written once or learned from a chat that went well.

Chats

A project has many chats. The project stays the team's; each chat is private to the person who opened it. Attach a file in the chat, or say the name of one in the library, and the agent uses it.

"Convert nefertari.html to Elementor, keep my section order, and make the hero a slider."

Choices, stop, report

When a job can be built in more than one place, the agent asks once, with its own suggestion marked as the default; answer with one word and it builds. The stop button ends a run before more credit goes. Every answer has Report a problem; the team reads every report and the fix shows on your What's new page.

Models

Pick the model per project under Site. Every model Tredcoo serves is available at its list price plus your account's terms; the cost of each step shows in Activity.

Converting a template

An HTML page, a zip with pages and assets, or a design-tool export goes into the project or the library. One sentence installs, draws, scans and converts it.

1. Drawn, not read. The page is rendered in a real browser first, so every width, gap and font size on the Elementor settings is what the browser measured.
2. Scanned. The agent tells you how many sections the page has and what each becomes before it converts.
3. Native Elementor. Containers with Heading, Text, Image and Button widgets; three or more alike cards become one Items grid; a slider becomes the Slider widget; question lists become the FAQ widget; forms become forms. Your client edits every section.
4. Kept when it serves better. A section with its own JavaScript, a calculator, a map, stays a working section widget or a dynamic section, and the agent says which and why. Switch any time.
5. A theme of its own. Every conversion makes the site a theme: one widget class per section named by its role, a settings page for colours and type, header and footer. It is installed under a guard and only activated when the site answers under it; a broken theme is switched back at once.

A multi-page export that holds the whole site in one file is split into one draft per page with the shared header and footer.

T-Design and the studio

No template? T-Design draws one. It starts with a questionnaire: how to start (from nothing, from a brief, from the address of an existing site), the kind of site, the hero, the header, the blocks, light or dark, pictures, motion, language. Then the brief in your words.

The result opens in the studio: versions on the left, the page on the right, a change written on the version you are looking at. Update this version keeps everything and applies the change; New design from here starts a fresh direction from that version. Every version lands in the library and converts like any template.

"Make it for a dentist in Rotterdam, blue instead of green, add a team section, keep the motion."

Designs with real photographs take them from a licensed picture source the moment they are drawn; your client replaces them. A design made from the address of a site is reinterpreted, never copied.

Forms, plugins and code

Forms

Describe a form, paste its HTML, or take one from a converted section. On a site that runs WPForms, Contact Form 7, Gravity Forms or Forminator, it is built in that plugin through its own API, notifications and anti-spam set. Otherwise it is a T-Builder form with a nonce, honeypot, rate limit, optional Turnstile or reCAPTCHA, stored entries and its own Forms screen in wp-admin.

Plugins and the toolbox

Security scan, broken links, speed and cache, backup, SEO, analytics, cookie banner, redirects, languages, image optimisation: each with the free plugin that does it, installed when missing. Update all the plugins runs the updates WordPress.org offers, one line per plugin.

Code of the site's own

When a job needs code the installed plugins do not offer, a shortcode, a post type with its archive, an integration, the agent writes a small plugin for the site. Every file is parsed before it lands, dangerous calls are refused, activation runs under a guard, and a fatal error switches it off again with the message in the answer. Only plugins it wrote are ever changed or removed.

SEO and connections

The SEO tab of a project holds the connections and the audit.

• Google Search Console, connected by its owner with one click. The agent reads queries, clicks, positions and the pages that are almost on page one.
• PageSpeed Insights in every audit: Core Web Vitals, what loads slow, what shifts, what the fix is.
• Keyword data for every project without any key of your own: volumes, difficulty, related terms and questions, a domain's standing, competitors, backlinks. Paid per request from your credit, cents per question, shown per site.
• Your own Semrush or Ahrefs key, pasted on the project: the agent uses your plan and nothing is metered for those requests.

"Audit the site the way Google sees it, then give me a keyword map for the three service pages."

Schedules

Say it once and it runs on a rhythm: hourly, daily, weekly, monthly, or once at a moment. The agent writes the schedule out and asks you to confirm before it adds it. Each run works in a thread of its own and ends with a report by e-mail, Slack or Discord, whichever you set up under Preferences → Notifications. A schedule may only change the live site when you said so.

"Every Monday at 08:00 check the site for broken links and mail me the list."

Credit, usage and invoices

One prepaid credit for every product and every site. A question costs cents, a whole template converted about $0.41, a design from a brief from a dollar. The overview shows the period's spend against the period before, thirty days drawn per product, and the usage per product, per site and per project.

• Top-ups by card, any amount from $10, a receipt for each. Set a reminder for a low balance, or let it reload itself.
• Statements every month, one line per site, so you bill your own clients from them.
• VAT follows your country: 21 % in the Netherlands, reverse charge for EU businesses with a VAT number, none outside the EU. Keep your company details complete under Company; they print on every invoice.

Team

Invite colleagues under Team. Each person gets view, edit or manage access per project and, if you like, a monthly budget. Their chats inside a project are their own; the project and its knowledge stay the account's. The owner sees what each person spent.

The gallery

tredcoo.ai/templates shows designs made in T-Design and designs offered by designers, sorted by shelf. Signed in, you copy one into your library with one button and the studio writes the next version on your copy. The copy is free; the first change is one design step.

A designer who writes HTML can offer a page from the Library. The platform draws it, scans every section the way T-Builder converts it, and scores it; the team approves it with the designer's name on the card. What a design needs is one page.

Your own product

Agents for your own portal talk to the platform with the same kind of key, over an API in the shape of the model provider's own Messages API, plus knowledge search, memory and learning routes in your own domain. Usage is metered and invoiced the same way. Write to hello@tredcoo.ai and we set up your domain.