Docs

Guides From First Generation To Team Delivery

The docs help teams understand product workflows, input requirements, outputs, plan benefits, and API integration so Aeaos can fit into daily production faster.

Aeaos docs center visual

Quick Start

Start By Choosing The Task Type

First identify the input type: product URL, product materials, simple prompt, or selling-point text.

01

Confirm the goal

Decide whether the task is a product video, full image set, prompt video, or script and storyboard.

02

Prepare input materials

Product URLs work for automatic parsing. Benefits, audience, platform, and duration work well for prompts and scripts.

03

Review outputs

Check product facts, selling points, visual style, platform sizes, captions, titles, and commercial boundaries.

04

Move into delivery

Add approved assets to your content library for publishing, ads, detail page updates, or API automation.

Product Usage

Inputs, Workflows, And Outputs For Four Task Types

Each product is designed around clear input, controllable generation, and deliverable output.

01

Product Video

Input a product detail URL, parse product data, extract selling points, generate scripts and storyboards, and output a short-form video draft.

  • Works for launches, ad testing, and multi-channel publishing.
  • Review product name, price range, selling-point order, and captions.
View product page
02

Product Image Set

Input a product URL or materials to generate hero images, lifestyle scenes, selling-point graphics, detail images, and ad visuals.

  • Works for listings, detail page optimization, and campaign assets.
  • Define brand color, visual style, platform size, and forbidden elements first.
View product page
03

Prompt To Video

Use a simple prompt to describe product, scene, style, channel, and duration, then generate reviewable video directions.

  • Works for creative exploration, campaign warmups, and ad direction tests.
  • More specific prompts create more stable rhythm and conversion goals.
View product page
04

AI Script Generation

Input benefits, audience, channel, and content goal to generate hooks, voiceover copy, shot plans, and title directions.

  • Works for short-form planning, creator scripts, and ad creative scripts.
  • Confirm tone, audience pain points, and prohibited claims first.
View product page

Pricing

Quota, Limit, And Upgrade Rules

Plans reset monthly and support a path from individual trials to team collaboration and enterprise integration.

How credits work

Task credits measure generation consumption across videos, images, and scripts. Different tasks consume different amounts.

URL parsing limits

Parsing reads titles, images, descriptions, and selling points. Page structure, access restrictions, and product data quality affect results.

Commercial use and watermarks

Free is for trials and internal evaluation. Paid plans fit formal commercial use, team workflows, and batch delivery.

Upgrades and Enterprise

Use Enterprise for more seats, API, Webhook, SSO, private deployment, or SLA requirements.

Choosing a plan

Solo sellers can start with Starter. Teams publishing continuously should consider Growth or Pro. For system integration or custom workflows, contact sales for Enterprise.

View pricing

API Integration

Connect Generation Tasks To Product Databases And Internal Tools

API access helps enterprises embed product content generation into existing systems and reduce manual copying.

1

Request access

Confirm plan, volume, data security, and callback requirements with sales.

2

Create task

Submit product URL, generation type, platform, language, size, and brand constraints.

3

Check status

Use task ID to check parsing, generating, completed, or failed status.

4

Receive result

Fetch videos, images, scripts, and error messages by query or Webhook.

POST /v1/tasks/product-video
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "product_url": "https://example.com/products/sku-123",
  "platform": "tiktok",
  "language": "en",
  "duration": 15,
  "brand_tone": "clear, professional, credible"
}
Developer note

Plan for retries, failure states, task timeout, result review, and asset archiving. Confirm data rights, product image usage, and platform publishing rules before production use.

View API page

FAQ

Key Questions To Confirm Before Use

What if product URL parsing fails?

You can manually provide title, images, benefits, specs, and target platform. Login, region restrictions, or page protections may affect parsing.

Can generated content be published directly?

Teams should review facts, pricing, claims, copyrighted assets, and platform rules. Aeaos accelerates production but does not replace review.

How should multilingual versions work?

Cross-border teams can extend scripts, titles, captions, and asset notes into English or other language versions.

When do we need Enterprise?

Use Enterprise for API, Webhook, SSO, multi-seat approval, private deployment, SLA, or custom generation workflows.

Reading Path

Read From Entry To Delivery By Task Type

First use

Start with Quick Start to identify input type and product entry.

Understand plans

Read Pricing to learn quotas, upgrades, and delivery support.

System integration

Go to API Integration for programmatic calls and examples.

Need help

If the answer is not covered, use the Contact page.