API Terms

Read them together with the Terms of Service.

1. What these terms cover

• MCP server (mcp.animatedwebs.com): lets AI assistants, editors and agents you connect search the catalog and read template prompts and other content your plan includes. Free accounts can read free content; Pro content needs a plan that includes it.
• Pro API (animatedwebs.com/api/v1): a JSON API, called from your server, for templates, prompts, UI components and the Brand Studio logo engine. Pro and Lifetime accounts only.
• API keys: the secret keys (they start with aw_) from your dashboard that you use for both.
• API Content: everything the MCP server or Pro API returns.

2. Keys

2.1 Keys are secret. Keep your key secret. Do not put it in client-side code, public repositories, shared prompts, screenshots or support messages. The Pro API has no CORS support on purpose: call it only from your server.

2.2 Keys are personal to your account. A key is for your account and plan only. Do not share, sell, lend or publish it, or use another person’s key.

2.3 You are responsible for your key. You are responsible for all use of your key and for all requests made with it, whether by you, your staff, your clients, your software, or anyone who got the key from you or because you did not keep it safe, until you rotate it. This does not cover use caused by a security breach of our own systems.

2.4 Rotation. Creating a new key revokes your previous key, which stops working within about a minute. Rotate your key at once if you think it has leaked, and tell us through the contact form.

3. AI agents act for you

3.1 Agent actions are your actions. When you connect an AI assistant, agent, editor plugin or automation (“Agent”) to the MCP server or the Pro API with your key, everything the Agent does with that key is done by you, on your behalf and under your responsibility, as if you had done it yourself. This includes requests you did not expect or review, and requests caused by instructions the Agent read elsewhere (for example a prompt injection in a web page or file). This does not cover content we ourselves put into API Content to make an Agent misbehave, or a security breach of our own systems.

3.2 You set the Agent up. You choose which Agents to connect, what permissions and instructions you give them, and how you supervise them. We do not control your Agent, its provider or what it does with API Content after it receives it.

3.3 Agents follow the license. Your Agents must follow these terms, the Terms and the Acceptable Use Policy. An Agent may read Pro content only through the authenticated MCP server or Pro API, never by scraping the website.

3.4 Our connection does not reach your systems. The MCP server answers the requests your Agent sends. It does not give us access to your assistant, your conversations, your editor or your files.

4. Limits

4.1 Rate limits. Today the Pro API allows 60 requests a minute and 1,000 a day per account. Responses carry rate limit headers, and a 429 response tells you when to retry. The MCP server and AI generation through it have their own limits and the daily AI limits in the AI Terms. Limits are per account, not per key or per Agent.

4.2 Changes. We may change limits, quotas, endpoints, response formats and authentication at any time. We will try to give reasonable notice of changes that break existing integrations, but we may make urgent changes without notice for security, abuse, legal or provider reasons.

4.3 No service level. There is no uptime promise, service level agreement or support response time for the API or the MCP server, unless we sign a separate written agreement with you.

4.4 Deprecation. We may retire an endpoint, a version or the whole API or MCP server. Where we reasonably can, we will give at least 30 days’ notice on the API docs page or by email.

5. What you may do with API Content

5.1 License. API Content is licensed content under section 4 of the Terms, not public data. You may use it only as your plan allows: to find and build with templates and components for your own sites and your clients’ sites, and to use the Brand Studio logo engine under the Brand Studio Terms.

5.2 What you may not do. You may not:

• resell, sublicense, rent, share or give access to the API, the MCP server or API Content, or offer them as part of your own service to people who do not hold their own AnimatedWebs plan;
• build a proxy, wrapper, mirror, public MCP server or app that exposes API Content to others;
• copy, store or cache API Content beyond what you need for your own current builds;
• compile API Content into a dataset, library or index, or build a competing template, component, prompt or logo product from it;
• use API Content to train, fine-tune, evaluate or benchmark AI models;
• go around limits, for example with several accounts or keys, or send requests meant to overload or probe the Service;
• remove license notices, attribution or credits from API Content;
• use the API or MCP server in breach of the Acceptable Use Policy, export or sanctions laws, or anyone’s rights.

5.3 Branding. Do not say or suggest that your app is made, endorsed or certified by AnimatedWebs, or use our marks in its name, without our written permission.

6. Our records and monitoring

We log API and MCP requests (for example account, key identifier, endpoint, time, status and usage counts) to run limits, billing, security and abuse prevention, as the Privacy Policy explains. We do not store your MCP search terms. We may monitor use to check that it follows these terms.

7. Suspension and revocation

We may throttle, suspend, rotate or revoke a key, or block an Agent or IP address, without notice if we reasonably believe the key leaked, is being used against these terms, creates a security or legal risk, or puts the Service or other users at risk. We will tell you where reasonable. Keys are revoked when your account ends, and Pro API access ends when your plan no longer includes it.

8. Your systems

You are responsible for your own systems, servers, Agents, their providers and their costs, and for following the terms of the AI provider behind any Agent you connect.

9. Disclaimers, limits and indemnity

The API, the MCP server and API Content are provided “as is” under section 15 of the Terms. The limits on liability in section 16 of the Terms apply. Your duty to cover the AnimatedWebs Parties in section 17 of the Terms includes claims arising from use of your keys, your Agents and your integrations.

10. Changes

We may change these terms. Material changes follow section 26.1 of the Terms. If a change requires it, we will ask you to accept the new API Terms the next time you create a key or visit the developer dashboard.