Texau logo

Get Website Tech Stack

Texau → Get Website Tech Stack

POST/v1/texau-web-tech-stack
texau__texau-web-tech-stackenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-web-tech-stack
{
  "url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "tech_name": "sample",
    "tech_category": "sample",
    "tech_confidence": 1,
    "tech_summary": "sample"
  }
}

Identifies the technologies, tools, and GTM signals (like estimated tech spend and company stage) used by a website.

Install

Add get website tech stack 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-web-tech-stack

When to use this.

The "Get Website Tech Stack" action identifies the technologies and tools utilized by a specified website, providing valuable insights into its tech stack and go-to-market signals, such as estimated tech spending and company stage. By inputting a target URL, users can retrieve detailed information about the technologies in use. The output includes key fields such as tech_name (text), tech_category (text), tech_confidence (number), and tech_summary (text), which collectively offer a comprehensive overview of the website's technological landscape. This action is particularly useful for businesses seeking to analyze competitors, enhance marketing strategies, or inform technology investment decisions, making it an essential tool in the enrichment category for data-driven insights.

Try it

Run a sample request.

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

Get Website Tech Stack

Try it

The target URL to detect technologies on.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • tech_name
    Tech Name
    string
  • tech_category
    Tech Category
    string
  • tech_confidence
    Tech Confidence
    nullablenumber
  • tech_summary
    Tech Summary
    nullablestring

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-web-tech-stack. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-web-tech-stack
curl -X POST 'https://v3-api.texau.com/api/v1/texau-web-tech-stack' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "tech_name": "sample",
    "tech_category": "sample",
    "tech_confidence": 1,
    "tech_summary": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Get Website Tech Stack→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 → get website tech stack → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Get Website Tech StackTexau 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 limit60 / min
  • Per-day limit50,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.

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 Get Website Tech Stack in 60 seconds.

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

Start free →Read the API docs