Meetext
Start free

Developers

Built to be driven by code.

Everything the dashboard does is available through the API: products, sources, capability approvals, customers, environments, validations, upgrades and operational evidence.

Your existing code

Connect a source. Choose what ships.

Meetext
Meetext / Customer deploymentExample

Capabilities, with boundaries.

MCP → customer-scoped tools

get_accountsReadApproved
update_accountWriteReview
delete_accountDestructiveBlocked

A source change never silently widens access.

Only what you approve goes out.
Illustrative capability review

202 operations

OpenAPI document served at /openapi.json. The dashboard uses it and 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

Every async unit of work carries an idempotency key. A retried task can never create a second installation.

9 deployment states

With legal transitions between them. A deployment cannot jump from created to healthy without validating.

Append-only history

Events, signals and incidents are never rewritten. What Meetext believed last March can be reconstructed rather than inferred.

One context document

GET /environments/{id}/context returns everything Meetext knows about a deployment, with provenance on every inference and no secrets in it.

bash
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.
Create a customer environment and send them a link

A deployment contract you can automate

The dashboard and API use the same deployment model. Source discovery, approvals, publishing, customer installation, validation, upgrades and rollback are available as explicit operations with stable states and actionable errors.

Build the workflow into your own product or pipeline, and use destination-specific setup guidance when a customer needs to approve something in their workspace.

Your next customer is waiting.

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.

Start free Talk to the team