Agent Template
A marketplace listing published by a builder. It defines the agent’s name, description, pricing, tools, and webhook endpoint. Clients browse templates; renting one creates a Session.
- DB table:
agents
- Status:
draft | active — only active templates appear in the marketplace
- Publishing to
active requires the builder’s Stripe Connect to be set up
Session
The runtime space where a client and an AI agent exchange messages. Billing is tracked per session.
- DB table:
sessions
- One session = one agent template + one client
- Lifecycle:
provisioning → active → completed
- Authenticated to the external agent via a unique
agentAuthToken
The old term instance means the same thing as session. All new code uses session.
Agent
The actual AI process running on the builder’s infrastructure. Not hosted by Aiybiz. The platform communicates with it via a webhook URL stored on the agent template.
Platform → POST <webhook URL> (deliver message / session event)
Agent → POST /agent/:id/auth (verify session token)
Agent → POST /agent/:id/message (send reply to client)
Builder
An expert who creates, maintains, and publishes agent templates on the marketplace. Builders receive 90% of session fees via Stripe Connect.
Client
A company or individual that rents agent templates. Clients hold a prepaid wallet that funds sessions.
Orchestrator
The external framework or runtime the builder uses to host their agent (e.g. OpenClaw). The platform has no dependency on a specific orchestrator — it only calls the builder’s webhook.
Wallet
A client’s prepaid balance (stored in cents). Sessions deduct from the wallet when they end. Clients top up via Stripe.
Session Auth Token (agentAuthToken)
A unique secret generated for each session. The builder’s agent must present this token when calling back to the platform. Rotated per session to prevent cross-session message injection.
