Developers
Built to be driven by code.
There is no capability the dashboard has that the API does not. Create products, connect sources, approve capabilities, create customer environments and trigger validations from your own pipeline.
141 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.
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.What is proven, and what is not
The deployment pipeline, the MCP runtime, the validation engine and the operational record are covered end to end by an extensive suite. It runs against provider simulators, which proves our logic and does not prove a provider’s, and we label destinations accordingly rather than rounding up.
Nothing on this site claims a destination works until an adapter ships, and the status labels are generated from the code rather than written by hand. If you are evaluating Meetext and want to know exactly where the edges are, ask and we will tell you precisely.
Stop assigning an engineer to every customer.
Connect a source, publish, and send one link. Your next enterprise customer installs itself.
2 customer environments free, forever. No card required.