Developer Documentation
Build agents and automations on top of the MTY Agentic Labs platform — send WhatsApp, Messenger, and Instagram messages, read inbox conversations, pull social and ads analytics, and manage message templates.
Everything here is publicly available to platform users. You don't need access to our codebase to build an integration — only an API key from your tenant.
Pick your integration path
| API Keys | Webhook Agents | MCP Server | |
|---|---|---|---|
| Direction | Your code calls our API | We call your endpoint | Claude Desktop calls our API |
| Triggered by | Your code (cron, user action, etc.) | Inbound end-user messages | A Claude chat |
| Setup | Self-service — 2 minutes | Onboarded by our team | 5 minutes |
| Best for | Outbound automation, analytics pulls, custom dashboards, scheduled jobs | Conversational AI, real-time replies | Ad-hoc operations in Claude Desktop |
| Authentication | X-API-Key: mta_… | Shared callback secret | Same API key, via the MCP server |
| Granularity | Per-key scopes | Per-channel agent assignment | Inherits API key scopes |
Most teams use a combination: a webhook agent for the live conversation, an API key for scheduled broadcasts or KPI dashboards, and the MCP server for ad-hoc queries.
Quick start
- Get an API key — log in, go to Settings → API Keys, click Create, copy the key.
- Try a request:
curl -H "X-API-Key: mta_..." \ https://api-meta.agenticlabs.site/api/social/summary - Read the API Keys guide for the full endpoint reference, code samples in Node / Python, and security best practices.
What we don't expose
For your protection and ours, the public docs deliberately omit:
- Internal deployment infrastructure (hosts, runners, CI configuration)
- Database schemas, migration internals, and backend file paths
- App secrets, OAuth client secrets, encryption keys, JWT signing keys
- Specific tenant or channel identifiers from production accounts
- Webhook signing keys (the value is issued during agent onboarding, not documented here)
If you need any of that for a legitimate reason (e.g., self-hosting, audit), contact the team directly.
Support & roadmap
- Found a bug? Open a ticket with your tenant and a request ID (see the
x-request-idheader on any failed response). - Want a feature? The internal "API key & external integration hardening" epic tracks: per-key rate limits, granular per-route scopes, usage audit log, key rotation flows, CORS tightening, MCP npm publication, tenant-wide oversight, signed outbound webhooks. We prioritize based on user demand.
The base URL https://api-meta.agenticlabs.site is stable. The interactive OpenAPI explorer lives at /docs (no auth required to view the schema).