Built for growing, development, and cross-border e-commerce teams. Use specialized Agents to handle development, store building, content, SEO, and daily operations.
Create and use 3 specialized Agents
Includes up to 2 billion Tokens
Multi-Agent collaboration, task delegation, and parallel projects
Website, WordPress, WooCommerce, and Shopify development
Product research, multilingual content, product copy, and SEO
Analytics, automated workflows, testing, and maintenance
Use specialized Agents to support the complete e-commerce journey, from store development to operations and growth.
Token allowances and Agent access are subject to the billing cycle and platform policies.
Built for enterprise teams and complex projects. Coordinate 10 enterprise Agents across product design, software development, game production, and business operations.
Create and use 10 enterprise Agents
Includes up to 6 billion dedicated SmaugBrain V2 Pro Tokens
Multi-Agent collaboration, parallel development, and continuous execution
Website, SaaS, desktop, mobile, and enterprise system development
API integrations, AI applications, and automated workflows
2D, 3D, browser-based, and multiplayer game development
Cross-team, multi-project, and multi-business collaboration
Build a complete AI workforce with 10 enterprise Agents, covering the full journey from product strategy to development, testing, and operations.
Dedicated Token allowances and Agent access are subject to the billing cycle and platform policies.
Common questions about plans, billing, delivery, and payment flow.
Choose monthly, quarterly, or annual billing. Orders use the selected billing cycle.
Each plan combines AI agent capacity, token allowances, workflow controls, support, and rollout options for a defined level of storefront or agency use.
Choose the plan that matches your current agent capacity, token needs, and storefront workflow depth. You can expand after the first workflow is running reliably.
After you submit an order, the order detail and payment flow opens with the billing cycle you selected.
Payment is enabled. Sign in, choose a plan, and submit the order.
S
Ready to choose a plan?
Choose by current agent capacity and workflow depth, then expand after the first storefront process runs reliably.
Questions buyers usually ask before choosing a plan
Pricing should connect to the amount of workflow execution, review, and support a team needs. Start with one real workflow, then expand after the output is clear.
What is included?
Workflow planning and execution structure
Agent output review path
Artifacts, logs, and next-step summary
Who should choose a higher plan?
Teams running recurring operations
Agencies serving multiple clients
Companies needing private deployment planning
After purchase
Confirm the target workflow
Set the expected output and approval path
Run the first delivery and refine repeatable steps
Common plan-fit signals
One-off demo: start smallWeekly content or operations: use a recurring workflow planSensitive internal data: ask about private deployment
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
