Seatext library

Seatext AI Account vs Script Installation: What’s the Difference?

A Seatext AI account stores your API key, settings, and usage limits. The script is the JavaScript snippet you embed on your site, which reads the API key and runs the AI agents in...

Seatext AI separates two essential pieces: the online account and the on‑page script. Understanding how they work together helps you avoid common errors and plan for growth.

Quick comparison

Criteria Seatext AI Account Seatext AI Script
Purpose Identity, dashboard, API key, agent configuration. Runs the AI on your pages by calling the account’s API key.
Setup effort Sign‑up, email verification, optional plan selection. Copy‑paste a short JavaScript snippet into your site’s header.
Dependency Independent – you can create or delete it anytime. Depends on a valid account and API key; fails without one.
Control / customization Choose agents, set parameters, view reports. Limited to the code you embed; customization happens in the account.
Activation timing Instant after email verification; may need a few minutes to link to your domain. Becomes active as soon as the page loads and the API key is recognized.
Scope One account per primary domain (separate accounts for dev, prod). Can be placed on any page of that domain.

How the account and script interact

The account generates a unique API key. The script contains a placeholder that the integration page replaces with that key. When a visitor loads a page, the browser sends the key to Seatext’s backend, authenticates it, and receives the list of active agents. The agents then modify the DOM in real time.

This flow ensures that the same script can serve many accounts, but each request is tied to a single key. If the key is missing or invalid, the script returns a harmless no‑op response, and no AI changes appear.

Step‑by‑step setup and troubleshooting

  1. Create a Seatext AI account on Seatext’s integration page. Verify your email.
  2. In the dashboard, locate the API key under Configuration → API Settings. Copy it.
  3. Open the integration page and click “Copy JavaScript”. The snippet looks like <script src="https://cdn.seatext.com/agent.js" data-key="YOUR_KEY"></script>.
  4. Paste the snippet into the <head> of every page you want AI to run on. For WordPress, use the WP Engine plugin mentioned in the source.
  5. Publish the change and clear any CDN cache.
  6. Visit the live page and stay for at least 40 seconds. This activates the link between the script and the account (source S1).
  7. Wait up to five minutes for the site name to appear next to the Seatext logo. If it does not appear, check the console for “Invalid API key” errors.
  8. Activate or deactivate agents from the dashboard. Changes take effect on the next page load.

Common errors:

  • Script placed before the closing </head> tag – some browsers may block it.
  • Using a development URL such as localhost. Seatext restricts these domains for security (source S1).
  • Copying the snippet but forgetting to replace YOUR_KEY with the real key.

Multi‑domain and security considerations

Each Seatext AI account is linked to a single primary URL. If you need the AI on a staging site, a test sub‑domain, or a completely separate production domain, you must create a new account for each (source S1).

Security restrictions prevent the script from running on dynamic development domains. The platform cannot reliably associate traffic with an account, so it blocks such URLs. This protects your API key from being exposed on insecure hosts.

When you have multiple accounts, keep each API key separate. Do not share keys across domains, as this defeats the per‑domain isolation and may cause activation failures.

Use‑case scenarios: marketers vs. developers

Marketers typically focus on the dashboard. They choose which agents to enable, set conversion goals, and review performance reports. They rarely touch code.

Developers handle the script. They ensure the snippet loads early, does not conflict with other JavaScript, and respects CSP headers. They also implement fallback logic for browsers that block third‑party scripts.

Example 1 – A small e‑commerce shop wants to translate product pages into 125 languages. The marketer activates the “Website Translation Agent” in the account. The developer adds the script once, and the AI serves translated copy automatically.

Example 2 – An agency runs paid search for many clients. Each client gets its own Seatext account (one per domain). The agency’s developer adds the same script to all client sites, but each site uses its own API key, so the AI tailors copy per client.

Decision guide: what to prioritize

When choosing where to invest time, ask these questions:

  1. Do I need granular control over agents? If yes, focus on the account settings.
  2. Is my site’s codebase stable? If yes, embed the script once and forget it.
  3. Am I managing multiple domains? If yes, plan separate accounts now to avoid later re‑configuration.
  4. Do I have strict CSP or Content‑Security‑Policy headers? If yes, work with a developer to add the script’s source to the allowed list.

In most cases, the account is the strategic layer (agent selection, reporting, budgeting). The script is the tactical layer (code placement, performance, security).

Extended FAQ

Why does the script stay inert until I stay on the page for 40 seconds?
The platform uses that time to verify the domain, associate traffic with the account, and fetch the active agent list. It prevents accidental activation on test URLs (source S1).
Can I change the script after it’s live?
Yes. Replace the snippet with an updated version from the integration page. The account’s API key remains the same, so agents continue to work.
What happens if I delete my account?
The API key becomes invalid. All pages that still contain the script will stop receiving AI responses and will log “Invalid API key” errors.
Do I need a paid plan to use the script?
No. The script itself is free. Paid plans unlock additional agents and higher usage limits.
How many domains can one account cover?
Only one primary domain per account. For each additional domain you must create a new account (source S1).
My site uses a Content‑Security‑Policy header. Will the script work?
Yes, if you add https://cdn.seatext.com to the script-src directive. Otherwise the browser will block the script.
Is there a way to test the script on a staging environment?
Use a separate staging domain and create a dedicated account for it. The platform treats it as a normal domain, but you must not use localhost or other restricted URLs (source S1).
Can I see which agents are currently active on a page?
Open the browser console and look for the Seatext object. It lists active agents and their version numbers.

Why the distinction matters

If you skip the account, the script cannot authenticate and will produce no AI output. If you skip the script, the account remains idle and you lose any conversion lift the agents could provide.

How they work together – a visual flow

  1. User clicks a link and loads a page.
  2. Browser executes the Seatext script.
  3. Script reads the embedded API key.
  4. Script sends a request to Seatext’s backend.
  5. Backend validates the key, checks the linked account, and returns the list of enabled agents.
  6. Agents modify the page DOM in real time (e.g., translate text, rewrite headlines).
  7. Visitor sees the AI‑enhanced version.

This loop repeats on every page load, ensuring that any changes you make in the dashboard are reflected instantly.

Key facts

FactDetail
Account required before scriptInstallation instructions state you must have a Seatext AI account first (source S1).
Script sourceCopy the JavaScript code from the integration page; it contains a placeholder for the API key (source S1).
One account per primary URLEach account links to a single primary domain; separate accounts are needed for dev and prod (source S1).
Activation delayVisit the site for at least 40 seconds and wait up to five minutes for the logo indicator (source S1).
Development URLs are restrictedLocalhost and dynamic dev domains are blocked for security reasons (source S1).
Free tier availableCreating an account does not require payment; paid plans add extra agents (source S1).

Common pitfalls

  • Installing the script before the account is fully linked – the script stays inert.
  • Using localhost or other restricted URLs – the platform blocks traffic.
  • Skipping the 40‑second activation step – the AI will not register the site.
  • Sharing one API key across multiple unrelated domains – leads to activation failures.

Limitations

The script cannot function without a valid API key, and each account supports only one primary domain. Multi‑domain sites need separate accounts, which adds management overhead. CSP restrictions may require additional configuration.

Further reading

For more details, see Seatext’s General Integration guide and the FAQ section on the same page.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

Learn more

Visit the website for more information.

Learn more