Agents quickstart
Describe your own agent, supply its instructions and knowledge, and choose how it runs. You can configure agents before billing setup. AI runs require completed billing setup and available SetCloud credits.
1. Create your own agent
Open Agents → Create agent in the dashboard. Name the agent and write its instructions: the task, the expected result, and the rules it should follow. Add your own knowledge and tools. SetCloud does not provide agent templates or prewritten agent instructions.
You can also import a JSON agent configuration you wrote yourself. Existing saved agents retain their settings and automations. For a custom runtime, choose Agents → Custom code → Import repository.
2. Configure your agent
In Build, choose a model, add knowledge and optional HTTP tools. If your agent needs built-in business actions, select those capabilities in Business setup, enter your business name and website, and complete their settings. Selecting capabilities preserves your instructions. The business website is read for each run; add specific product, service, policy or help pages under Knowledge for more complete answers.
Choose a model from the full AI Gateway catalog. Search by model, family or capability. Available custom models appear too. Embedding models remain visible as knowledge-search models; action workflows require a model with tool support. Prices shown use the same rates as AI Gateway. Set a maximum cost per run.
Knowledge supports notes, public HTTPS pages, and UTF-8 TXT, Markdown, CSV and JSON uploads. Each file can be up to 100 KB, with at most 10 sources and 200 KB total configuration. Export PDF and word-processing files as text first. Published website chat can use this knowledge to answer visitors, so review it before publishing.
3. Try a task and review the records
Choose Try it → Run once. The result and cost appear in History. Under Business records, review workspace leads, this agent’s quote drafts, follow-ups, website conversations and appointments.
Quotes use saved prices and exact cent arithmetic. Approve a draft before sharing its private link or allowing a website visitor to accept it. Quote acceptance records the customer’s decision; it does not collect payment.
Follow-up agents prepare drafts. Copy them into your own tool or approve sending through a connected delivery API. Replied, closed and do-not-contact leads stop future drafts. Keep reply and lead stages up to date in the dashboard or your API.
Appointment proposals hold a slot for 15 minutes. A customer or authorized team member must explicitly confirm it. The built-in calendar permits one appointment at a time across the workspace. Download confirmed events as calendar files.
4. Automate, publish, or connect your app
Automate creates hourly, daily, weekday or weekly tasks in your chosen time zone. Lead research, follow-up preparation and website checks fit recurring tasks. Reports stay in History with dashboard notifications.
Website & API publishes supported customer-facing agents as a website widget. Add allowed HTTPS website origins, set a rolling 24-hour chat allowance, enable website chat, save, and paste the embed into your site. The embed has no secret key. Visitors can share contacts, ask the team, review approved quotes, and confirm appointment proposals. Website conversations retain their own message history.
You can reply to visitors in Business records → Conversations. Replies appear in the same website conversation; they are not emails. Visitor sessions last 24 hours. Connected support forwarding is optional and requires a deliberate action.
For your own applications, create an expiring agent key and use the server-side example. App runs start with fresh context; include earlier messages when needed. Optional key permissions allow reading business records and creating leads or quote drafts. Existing keys retain their original run-only access.
Optional API connections
SetCloud records and website chat work without another business service. Connect APIs you control under Website & API, then select them under Build → Business setup → Connect your own tools. Credentials are stored encrypted and never shown again. No shared, verified third-party app is required for these client-owned API connections. An existing API may need a small adapter for SetCloud’s request contract. See API and connection details.
Lead finder reads your selected public sources and discovered links. It does not include an unrestricted search engine or a purchased contact database. A client-owned search API can extend discovery. Missing contact facts remain missing.
Costs and recovery
Runs have a three-minute deadline, up to six model turns and eight tool calls (ten turns and 24 calls for prospect research and follow-up preparation). Available credits, spending controls and the per-run estimate gate each model step. Performed model usage is billed even if a later step fails. Agent usage does not trigger a card auto-reload. Website requests reserve the full per-run limit against their chat allowance before being queued.
Interrupted external actions never retry automatically. Check the connected API and record its outcome in Business records: use API activity for lead syncs and support tickets, Follow-ups for messages, and Appointments for bookings. Include what you checked. Reconciliation records that evidence without sending again. A recorded API acceptance means that API accepted the action; it is not proof of email delivery.
Custom code remains available for clients who need their own runtime and repository deployment. It is separate from these ready-to-configure business workflows.
Keep your model current
The model picker shares AI Gateway’s available models and prices. Choose a model with the tools capability when your agent uses actions, and use Refresh models to load catalog updates. Long-context price conditions appear below the selected model. Changing the catalog does not silently change a saved agent.