Crescendo Lab
Crescendo Lab is a Taiwan-based, Asia-leading AI omnichannel customer communication software company (cresclab.com) serving 800+ global brands, and a LINE Biz-Solutions Gold Partner. Its platform spans MAAC (AI marketing automation), CAAC (conversational applications), and DAAC (data intelligence) across LINE, WhatsApp, SMS, email, and social channels. Its developer-facing surface is MAAC Go (sms.cresclab.com) — a self-serve, NCC-compliant Taiwan SMS API with a published OpenAPI spec, first-party Node/Python SDKs, a CLI, an official MCP server, and delivery webhooks. Surfaced as a 500 Global portfolio company and enriched into the API Evangelist network.
Crescendo Lab publishes 4 APIs on the APIs.io network, including Broadcast API, Contacts API, SMS API, and 1 more. Tagged areas include Company, SMS, Messaging, Marketing Automation, and Customer Engagement.
The Crescendo Lab catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Crescendo Lab’s developer surface includes documentation, engineering blog, pricing, signup flow, CLI, authentication, and 15 more developer resources.
Kin Score
APIs 4
Individual APIs this provider publishes, each with its own machine-readable definition.
Crescendo Lab Broadcast API
Bulk (1-to-many) SMS. Small batches dispatch inline; >30 recipients queue asynchronously.
Crescendo Lab Contacts API
Address book with NCC-consent tracking.
Crescendo Lab SMS API
Transactional (1-to-1) SMS send + status.
Crescendo Lab Teams API
Cost-attribution teams. Tag sends with a team to see which team sent/spent how much (shared wallet — reporting only, not a wallet split).
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
crescendo-lab-mcp.yml
MCP SERVEREvent Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Crescendo Lab Maacgo Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API