Skip to content

Quickstart

This guide takes one capability from a clear promise to an operated Agent Business. Agent as a Business is a hosted product, so you do not need to clone a repository or run the platform locally.

Sign in at app.agentaab.com, then choose New Agent Business from Portfolio.

Give the business a name and describe the reliable outcome it delivers. Choose who will consume it:

  • Human SaaS for a customer-facing Web experience.
  • Agent SaaS for API, OpenAPI, MCP, or agent-to-agent use.
  • Dual when human and agent surfaces share one business identity.

You can change the delivery mode later, but starting with the primary buyer keeps packaging and pricing decisions clear.

Choose a prompt or workflow source, then define the input and output contract. For Agent SaaS or Dual businesses, the schema is part of the contract that API clients and agents depend on.

Test the capability with representative inputs before creating a release. Provider credentials and payment secrets stay in trusted platform configuration and must never appear in browser-readable fields or generated frontend code.

Choose the surfaces, visibility, language, and pricing intent. A surface can be a hosted Web app, runtime API, OpenAPI document, MCP tool, or downloadable package.

If you need a hosted frontend, configure it under Surfaces. For a machine-facing product, verify that the runtime schema and examples are precise enough for a client that has no human context.

A Capability Release is an immutable executable and trust contract. Review the capability version, schemas, runtime policy, and commercial references before activation.

Do not edit a live release in place. Create a new release when behavior or contracts change, then activate it after validation.

Create an Offer for buyer-facing price, quota, payment, and refund terms. Publish the business to the channels you intend to operate, such as hosted Web, direct API, MCP, or an external agent registry.

For a generated Web surface, follow Deploy to Cloudflare.

Use Portfolio for cross-business status and verified totals. Inside one Agent Business, use Operations for reliability and invocation evidence, and Revenue for recorded earnings and allocation.

Empty states mean that no verified events match the selected period or filters. Agent as a Business does not invent traffic, revenue, or growth trends.