Count logo

Count Item Occurrences (Utility)

Count → Count Item Occurrences (Utility)

POST/v1/count-item-occurrences
texau__count-item-occurrencesenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/count-item-occurrences
{
  "input": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "result": "sample",
    "result_item": "sample",
    "result_count": 1,
    "total_item": 1,
    "unique_item": 1
  }
}

Counts the frequency of each unique item in a string array with totals.

Install

Add count item occurrences (utility) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__count-item-occurrences

When to use this.

The "Count Item Occurrences" action is a utility designed to analyze a string array and determine the frequency of each unique item within it. By providing an input parameter, "input," which is the array of items to be evaluated, users can efficiently obtain insights into item distribution. The action outputs several key fields: "result," a summary of the findings; "result_item," which specifies each unique item; "result_count," indicating the number of occurrences for each item; along with "total_item," the overall count of items processed, and "unique_item," the count of distinct items identified. This action falls under the enrichment category and is particularly useful in data analysis, reporting, and text processing scenarios where understanding item frequency is essential for decision-making and insights generation.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Count Item Occurrences (Utility)

Try it

The array of items (strings) to count occurrences for.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • result
    Result
    nullablearray
  • result_item
    Result Item
    nullabletext
  • result_count
    Result Count
    text
  • total_item
    Total Item
    number
  • unique_item
    Unique Item
    number

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/count-item-occurrences. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/count-item-occurrences
curl -X POST 'https://v3-api.texau.com/api/v1/count-item-occurrences' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"input":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "result": "sample",
    "result_item": "sample",
    "result_count": 1,
    "total_item": 1,
    "unique_item": 1
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Count Item Occurrences (Utility)→Enrich→Push to CRM

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → count item occurrences (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Count Item Occurrences (Utility)Count action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit300 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__count-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Count Item Occurrences (Utility) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs