A professional, legally structured service agreement template is created with dynamic fields for client details, compensation, and signatures, ready for distribution.
The agent analyzes the provided writing guide to understand APISign's Markdown syntax and variable conventions. It constructs a Service Agreement template using appropriate headings, bold text for labels, and horizontal rules. It inserts specific template variables like {{client_name}}, {{total_amount}}, and {{provider_signature}} based on the naming conventions. Finally, it ensures the signature block is correctly formatted to capture both parties' signatures and dates automatically.
- Category: Sales and marketing
- Effect: Changes data in your accounts
- MCP servers: APISign MCP (https://koskamo.com/explore/apisign-mcp)
- Source: Writing Guide | APISign (https://apisign.io/docs/app/templates/writing-guide)
- Source quote: "APISign templates use Markdown, a lightweight formatting syntax that's easy to learn and produces clean, professional documents."
- Playbook page: https://koskamo.com/explore/use-cases/draft-a-service-agreement-template
Prompt: Create a Service Agreement template for APISign using Markdown. Include sections for Parties, Services, Compensation, Term, and Signatures. Use variables like {{client_name}}, {{provider_name}}, {{total_amount}}, {{effective_date}}, {{expiration_date}}, {{provider_signature}}, and {{client_signature}}. Ensure the signature block allows both parties to sign and dates are auto-filled.