Developers
Built to be driven by code.
Everything the dashboard does is available through the API: products, sources, approvals, customers, environments, validations and upgrades.
Connect a source. Choose what ships.
Capabilities, with boundaries.
MCP → customer-scoped tools
get_accountsReadApprovedupdate_accountWriteReviewdelete_accountDestructiveBlockedA source change never silently widens access.
202 operations
OpenAPI document at /openapi.json. The dashboard uses nothing else.
Streamable HTTP MCP
initialize, tools/list, tools/call, ping. Versions 2025-06-18, 2025-03-26, 2024-11-05, negotiated per client.
Idempotent by design
A retried task can never create a second installation.
9 deployment states
A deployment cannot jump from created to healthy without validating.
Append-only history
Events, signals and incidents are never rewritten.
One context document
GET /environments/{id}/context returns everything Meetext knows about a deployment, with provenance and no secrets.
curl -X POST https://api.meetext.xyz/v1/customers \
-H "authorization: Bearer $MEETEXT_API_KEY" \
-d '{"name": "Nike", "contact_email": "it@nike.com"}'
curl -X POST https://api.meetext.xyz/v1/environments \
-H "authorization: Bearer $MEETEXT_API_KEY" \
-d '{"customer_id": "...", "product_id": "...",
"target_kind": "slack",
"entitled_capabilities": ["search_campaigns"]}'
# Returns the install link. From here you are not
# required to be present.A deployment contract you can automate
Publishing, installation, validation, upgrades and rollback are explicit operations with stable states and actionable errors. When a customer must approve something, use the destination-specific setup guidance.
You build the product.
We take it from here.
Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.