Custom logo

Predict Gender from Name (Utility)

Custom → Predict Gender from Name (Utility)

POST/v1/custom-predict-gender
texau__custom-predict-genderutility
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/custom-predict-gender
{
  "unique_name": "Jane Doe"
}
200 Accepted
{
  "ok": true,
  "data": {
    "gender": "sample",
    "probability": 1,
    "count": 1
  }
}

Predicts the likely gender from a first name using statistical analysis.

Install

Add predict gender from name (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__custom-predict-gender

When to use this.

Predicts the likely gender from a first name using statistical analysis.

Try it

Run a sample request.

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

Predict Gender from Name (Utility)

Try it

First name to predict

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • gender
    Gender
    text
  • probability
    Probability
    number
  • count
    Count
    nullablenumber

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/custom-predict-gender. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/custom-predict-gender
curl -X POST 'https://v3-api.texau.com/api/v1/custom-predict-gender' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"unique_name":"Jane Doe"}'
200 Accepted
{
  "ok": true,
  "data": {
    "gender": "sample",
    "probability": 1,
    "count": 1
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Predict Gender from Name (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 → predict gender from name (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Predict Gender from Name (Utility)Custom 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 limit1000 / min
  • Per-day limit1,000,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__custom-...` 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 Predict Gender from Name (Utility) in 60 seconds.

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

Start free →Read the API docs