{
  "listings": [
    {
      "slug": "sequenzy",
      "name": "Sequenzy",
      "company": "Nic Tech Solutions, LLC",
      "grade": "B",
      "fit": "yes",
      "why": "Create segment takes flat filters or a nested filter tree, and GET /segments/{id}/count recalculates the active subscriber count from the saved filters, two calls in all.",
      "source": "https://docs.sequenzy.com/openapi.yaml",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/sequenzy"
    },
    {
      "slug": "braze",
      "name": "Braze",
      "company": "Braze, Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "create_segment takes a filter tree checked against get_segment_filters, but size comes back as a daily estimate and the member list only through an async segment export to a ZIP URL, not paged in 3 calls.",
      "source": "https://www.braze.com/docs/user_guide/brazeai/mcp_server/available_api_functions",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/braze"
    },
    {
      "slug": "customer-io",
      "name": "Customer.io",
      "company": "Peaberry Software, Inc. d/b/a Customer.io",
      "grade": "A",
      "fit": "caveat",
      "why": "customer_count and paged membership read a segment back, but POST /v1/segments creates only empty manual segments; data-driven segments come through the MCP server, whose filter validation is not documented.",
      "source": "https://docs.customer.io/openapi.json",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/customer-io"
    },
    {
      "slug": "klaviyo",
      "name": "Klaviyo API + MCP",
      "company": "Klaviyo, Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "POST /api/segments takes a definition, profile_count is an additional field and segment profiles page back, but creation is capped at 100 a day, filter-key validation isn't documented, and acc-07 found the SDK dropped the paging links.",
      "source": "https://raw.githubusercontent.com/klaviyo/openapi/main/openapi/stable.json",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/klaviyo"
    },
    {
      "slug": "mailchimp-marketing",
      "name": "Mailchimp Marketing API",
      "company": "The Rocket Science Group LLC d/b/a Mailchimp",
      "grade": "C",
      "fit": "caveat",
      "why": "Create Segment takes match and conditions, member_count is returned and members page back up to 1,000 with total_items, but acc-21 shows Mailchimp silently ignoring a non-existent filter and returning everyone.",
      "source": "https://mailchimp.com/developer/marketing/api/lists/segments/create-segment.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/mailchimp-marketing"
    },
    {
      "slug": "moengage",
      "name": "MoEngage",
      "company": "MoEngage, Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "create_custom_segment takes filters and start_segment_count then poll_segment_count returns a count in three calls, but event and event-attribute names are never checked at creation, so a wrong one fails later with no reason unless deep_validate_segment_filters runs first.",
      "source": "https://www.moengage.com/docs/user-guide/ai-and-intelligence/merlin-ai/moengage-mcp-server.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/moengage"
    },
    {
      "slug": "nitrosend",
      "name": "Nitrosend",
      "company": "Nitrosend Pty Ltd",
      "grade": "BB",
      "fit": "caveat",
      "why": "nitro_define_segment previews filters by default and saves on request, but counts are refreshed in the background as an operational guide, not exact, and no paged member read-back was found for a segment.",
      "source": "https://docs.nitrosend.com/mcp.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/nitrosend"
    },
    {
      "slug": "omnisend",
      "name": "Omnisend",
      "company": "Omnisend, UAB",
      "grade": "B",
      "fit": "caveat",
      "why": "POST /segments takes contact and event filters and segment statistics return contactsCount, but the count answers 409 while the segment builds, and whether unknown filter keys are rejected wasn't found.",
      "source": "https://api-docs.omnisend.com/reference/post_segments.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/omnisend"
    },
    {
      "slug": "activecampaign",
      "name": "ActiveCampaign",
      "company": "ActiveCampaign, LLC",
      "grade": "E",
      "fit": "unchecked",
      "why": "Not read: hosts paused under the terms question. The 8 October notes say create_segment exists and unsupported filter keys are silently ignored, which would make this a caveat at best.",
      "confidence": "low",
      "url": "https://www.anchorterminal.com/tools/activecampaign"
    },
    {
      "slug": "clevertap",
      "name": "CleverTap",
      "company": "WizRocket Inc.",
      "grade": "D",
      "fit": "no",
      "why": "Create Segment takes only a segment_name and customer_segment_id, with no filter conditions, so a segment with stated conditions cannot be built; Get Profile Count can count an event query separately.",
      "source": "https://developer.clevertap.com/docs/create-segment-api.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/clevertap"
    },
    {
      "slug": "dreamlit",
      "name": "Dreamlit",
      "company": "Notika AI (d/b/a Dreamlit AI)",
      "grade": "C",
      "fit": "no",
      "why": "There is no segment object or member read-back; a workflow's audience is described in its prompt and resolved by query steps against the app database.",
      "source": "https://dreamlit.ai/docs/resources/mcp-server",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/dreamlit"
    },
    {
      "slug": "iterable",
      "name": "Iterable",
      "company": "Iterable, Inc.",
      "grade": "C",
      "fit": "no",
      "why": "POST /api/lists creates static lists only; no operation builds a list from conditions, though list size and getUsers read a list back.",
      "source": "https://api.iterable.com/api-docs",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/iterable"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "useCase": {
    "accounts": 3,
    "after": [
      "lifecycle-marketing.campaign-draft",
      "lifecycle-marketing.send-with-approval"
    ],
    "area": "communication",
    "asks": [
      "who are our lapsed purchasers",
      "build a segment of VIPs who haven't opened in 90 days",
      "how many people will get this"
    ],
    "before": [
      "lifecycle-marketing.profile-event-sync"
    ],
    "blockers": [
      "no API to build a dynamic segment (Iterable)",
      "segment creation limited to 100 a day (Klaviyo)",
      "a filter the API ignores silently, returning everyone"
    ],
    "capabilities": [
      "marketing.segments",
      "marketing.profiles"
    ],
    "category": "lifecycle-marketing",
    "categoryName": "Lifecycle marketing \u0026 customer engagement",
    "checked": "2026-11-15",
    "companies": {
      "fit": 1,
      "fitWithLimit": 7,
      "tagged": 11
    },
    "competition": "one",
    "fits": [
      "sequenzy"
    ],
    "fitsWithLimit": [
      "braze",
      "customer-io",
      "klaviyo",
      "mailchimp-marketing",
      "moengage",
      "nitrosend",
      "omnisend"
    ],
    "id": "lifecycle-marketing.segment-build-readback",
    "listings": {
      "caveat": 7,
      "no": 3,
      "notRead": 0,
      "tagged": 11,
      "unchecked": 1,
      "yes": 1
    },
    "name": "Build a segment and confirm who is in it",
    "status": "draft",
    "success": "A segment exists with the stated conditions and its full member list or exact count can be read back with paging, before any send. Measured: the read-back takes at most 3 calls.",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/lifecycle-marketing.segment-build-readback.json",
    "weight": 10,
    "weightBasis": "3 of 30 counted mentions (acc-07, 13, 21); vendor pages (Customer.io, Klaviyo) push this use case harder than accounts do"
  }
}
