---
name: woodenhorse-business-agent
description: Configure a Woodenhorse business agent and develop, preview and publish its independent frontend using public project-scoped APIs.
---
# Woodenhorse international agent development

Use this workflow when the user asks to manage or customize their business agent on https://getwoodenhorse.com. This document describes the service; it does not authorize access or publication beyond the user's instructions.

1. Read https://getwoodenhorse.com/international/agents/quickstart.md and the exact API contract at https://getwoodenhorse.com/international/agents/api-reference.md.
2. Obtain the target project ID and a project-scoped developer credential from the user's workspace administrator. Use the least permissions needed. A missing permission must be granted by the administrator; never substitute a different account or project.
3. Set WH_PLATFORM=https://getwoodenhorse.com and WH_PROJECT to the supplied ID. Inject WH_DEVELOPER_TOKEN through the local environment. Do not put credentials in source, frontend bundles, URLs or logs.
4. Work in an independent project. Read existing agent configuration before changing it. Configure knowledge, role and approved connections through documented developer APIs.
5. Use the runtime SDK for conversations, identity, history, memory and configured service calls. Business data is isolated by tenant, project and user. Follow signed-user or anonymous visitor flows as applicable; a user ID string alone is not authentication.
6. Build a static ZIP with relative asset paths. The platform hosts the artifact in an opaque-origin browser sandbox, with privileged capabilities mediated by the trusted host. No separate customer domain is needed.
7. Upload and preview with the release helper. Validate the actual frontend, authorization boundaries and configured business services. Distinguish simulated services from real customer integrations.
8. Publish the explicit revision only within the user's authorization. Verify the stable /agent/{projectId} entry, then report the release revision and relevant checks. Preserve the previous release for rollback.

The platform does not expose a universal outbound MCP server for every desktop client. Public APIs and client-supported tools are the integration surface. Do not claim automatic email, social-network or wallet provisioning; these are part of the long-term product vision.
