Texau logo

Normalize Company Name (Utility)

Texau → Normalize Company Name (Utility)

POST/v1/texau-normalize-company-name
texau__texau-normalize-company-nameenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-normalize-company-name
{
  "company_name": "Acme, Inc."
}
200 Accepted
{
  "ok": true,
  "data": {
    "case_normalized": true,
    "change_applied": true,
    "normalized_company_name": "sample",
    "original_company_name": "sample",
    "removed_suffix": "sample"
  }
}

Standardizes company names by fixing capitalization and removing legal suffixes like Inc, LLC, and Ltd.

Install

Add normalize company 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__texau-normalize-company-name

When to use this.

The "Normalize Company Name" action is a utility designed to standardize company names by correcting capitalization and eliminating legal suffixes such as Inc, LLC, and Ltd. This process enhances data consistency and improves the quality of company information. The primary input parameter is "company_name," which is the text representation of the company name to be normalized. The action outputs several fields, including "normalized_company_name" (the cleaned and standardized name), "original_company_name" (the input name for reference), "case_normalized" (indicating if case normalization was applied), "changes_applied" (confirming if any modifications were made), and "removed_suffixes" (listing any suffixes that were removed). This action is particularly useful in data enrichment scenarios, such as CRM systems, marketing databases, and business intelligence applications, where accurate and uniform company names are essential for effective analysis and reporting.

Try it

Run a sample request.

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

Normalize Company Name (Utility)

Try it

The company name to normalize and clean for consistent formatting.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • case_normalized
    Case Normalized
    boolean
  • change_applied
    Change Applied
    nullableboolean
  • normalized_company_name
    Normalized Company Name
    text
  • original_company_name
    Original Company Name
    nullabletext
  • removed_suffix
    Removed Suffix
    nullablearray

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-normalize-company-name. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-normalize-company-name
curl -X POST 'https://v3-api.texau.com/api/v1/texau-normalize-company-name' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"company_name":"Acme, Inc."}'
200 Accepted
{
  "ok": true,
  "data": {
    "case_normalized": true,
    "change_applied": true,
    "normalized_company_name": "sample",
    "original_company_name": "sample",
    "removed_suffix": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Normalize Company Name (Utility)→Remove Extra Whitespace (Utility)→Identify Email Type (Utility)

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 → normalize company name (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Normalize Company Name (Utility)Texau 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.

Standard tier

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

Related

More Texau actions.

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__texau-...` 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 Normalize Company Name (Utility) in 60 seconds.

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

Start free →Read the API docs