Texau logo

Bing Search

Texau → Bing Search

POST/v1/texau-search-bing
texau__texau-search-bingenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-search-bing
{
  "query": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "result_title": "sample",
    "result_url": "https://acme.com",
    "result_description": "sample",
    "result_position": 1,
    "result_displayed_url": "https://acme.com",
    "result_date_published": "sample",
    "total_result": 1,
    "query_used": "sample"
  }
}

Query Bing web search and return structured results, including titles, descriptions, and URLs.

Install

Add bing search 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-search-bing

When to use this.

The "Bing Search" action, identified as texau-search-bing, enables users to perform web searches using Bing and retrieve structured results that include essential information such as titles, descriptions, and URLs. The primary input parameter is the "query," a string representing the search term or phrase. Upon execution, the action outputs various fields, including "result_title," "result_url," "result_description," "result_position," "result_displayed_url," and "result_date_published," all of which are crucial for understanding the search results. Additionally, it provides "total_results," indicating the overall count of results found, and "query_used," which reflects the original search term. This action is particularly useful for data enrichment, allowing developers to integrate Bing search capabilities into applications, enhance user experiences, and facilitate information retrieval across various domains.

Try it

Run a sample request.

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

Bing Search

Try it

The search term or phrase to query on Bing.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • result_title
    Result Title
    string
  • result_url
    Result Url
    string
  • result_description
    Result Description
    nullablestring
  • result_position
    Result Position
    nullablenumber
  • result_displayed_url
    Result Displayed Url
    nullablestring
  • result_date_published
    Result Date Published
    nullablestring
  • total_result
    Total Result
    nullablenumber
  • query_used
    Query Used
    nullablestring

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-search-bing. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-search-bing
curl -X POST 'https://v3-api.texau.com/api/v1/texau-search-bing' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"query":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "result_title": "sample",
    "result_url": "https://acme.com",
    "result_description": "sample",
    "result_position": 1,
    "result_displayed_url": "https://acme.com",
    "result_date_published": "sample",
    "total_result": 1,
    "query_used": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Bing Search→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 → bing search → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Bing SearchTexau 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 Bing Search in 60 seconds.

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

Start free →Read the API docs