> ## Documentation Index
> Fetch the complete documentation index at: https://aisa.one/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Search Intent

> Classifies keywords as informational, navigational, commercial or transactional.

Classifies `keywords` as informational, navigational, commercial or transactional. Returns `language_code`, `items_count` and `items`. Measured at 673 bytes. Wrapped in DataForSEO's envelope: data in `tasks[0].result`, outcome in `tasks[0].status_code` - a rejected request still returns HTTP 200. Intent decides what a page has to be before volume decides whether it is worth writing; pair it with `post_dataforseo_labs_google_keyword_overview_live`.

## Example

<CodeGroup>
  ```bash REST theme={null}
  curl -X POST "https://api.aisa.one/apis/v1/dataforseo/dataforseo_labs/google/search_intent/live" \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -d '[{"keywords": "...", "language_name": "...", "language_code": "..."}]'
  ```

  ```jsonc MCP theme={null}
  // Copy this whole block into Claude Code, Codex, Cursor or any coding agent.
  // It carries everything needed to connect, authorize and run this example —
  // no key to paste, one click of Allow in the browser.
  {
    "operation_id": "post_dataforseo_labs_google_search_intent_live",
    "arguments": {},
    "max_price_usd": 0.05
  }
  // ── for the agent ─────────────────────────────────────────────────────────
  // Register the AIsa MCP server, then call its `use` tool with the JSON above.
  //   name       aisa
  //   endpoint   https://mcp.aisa.one/mcp
  //   transport  streamable-http
  //   auth       OAuth. The server publishes RFC 9728 metadata, so open a
  //              browser and the user clicks Allow once — nothing to paste.
  //              If AISA_API_KEY is set, send it as a bearer header instead.
  // Use your own MCP mechanism, not a hand-edited config file:
  //   Codex        codex mcp add aisa --url https://mcp.aisa.one/mcp
  //   Claude Code  claude mcp add --transport http -s user aisa https://mcp.aisa.one/mcp
  //   Cursor / VS Code   a "url" entry for https://mcp.aisa.one/mcp in the MCP config
  // The server lists five tools over https://mcp.aisa.one/servers worth of APIs:
  // search, get_details, use, batch_use, list_categories. search and
  // get_details are free; use is billed per call and max_price_usd refuses
  // anything above the cap before spending. This operation's full contract —
  // every argument, the response shape, the price and the pitfalls — is at
  //   https://aisa.one/docs/api-reference/dataforseo/post_dataforseo-dataforseo-labs-google-search-intent-live.md
  // Then run the call and show me the result.
  ```
</CodeGroup>

<Note>
  **First time?** Point any MCP client at `https://mcp.aisa.one/mcp` — Claude
  Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client
  opens a browser, you click Allow once, and there is no key to paste. The
  commands per client, and what each call costs, are on
  [aisa.one/mcp](https://aisa.one/mcp#connect).
</Note>

[Set this endpoint up in your agent →](https://aisa.one/mcp?from=/api-reference/dataforseo/post_dataforseo-dataforseo-labs-google-search-intent-live)


## OpenAPI

````yaml openapi/dataforseo.json POST /dataforseo/dataforseo_labs/google/search_intent/live
openapi: 3.0.3
info:
  title: DataForSEO API
  version: 1.0.0
  description: DataForSEO API endpoints exposed through the AIsa unified gateway.
servers:
  - url: https://api.aisa.one/apis/v1
security:
  - BearerAuth: []
paths:
  /dataforseo/dataforseo_labs/google/search_intent/live:
    post:
      summary: Search Intent
      description: >-
        This endpoint will provide you with search intent data for up to 1,000
        keywords. For each keyword that you specify when setting a task, the API
        will return the keyword’s search intent and intent probability. Besides
        the highest probable search intent, the results will also provide you
        with other likely search intent(s) and their probability.
      operationId: post_dataforseo_labs_google_search_intent_live
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: array
              items:
                type: object
                properties:
                  keywords:
                    type: array
                    items:
                      type: string
                    description: >-
                      target keywords required field UTF-8 encoding maximum
                      number of keywords you can specify in this array: 1000;
                      the keywords will be converted to lowercase format learn
                      more about rules and limitations of keyword and keywords
                      fields in DataForSEO APIs in this Help Center article
                  language_name:
                    type: string
                    description: >-
                      full name of the language required field if don’t specify
                      language_code you can receive the list of available
                      languages with their language_name by making a separate
                      request to
                      https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages
                      Note: this endpoint currently supports the following
                      languages only: Arabic, ar, Chinese(Traditional), zh-TW,
                      Czech, cs, Danish, da, Dutch, nl, English, en, Finnish,
                      fi, French, fr, German, de, Hebrew, he, Hindi, hi,
                      Italian, it, Japanese, ja, Korean, ko, Malay, ms,
                      Norwegian(Bokmål), nb, Polish, pl, Portuguese, pt,
                      Romanian, ro, Russian, ru, Spanish, es, Swedish, sv, Thai,
                      th, Ukrainian, uk, Vietnamese, vi, Bulgarian, bg,
                      Croatian, hr, Serbian, sr, Slovenian, sl, Bosnian, bs,
                      Greek, el, Hungarian, hu, Slovak, sk, Turkish, tr example:
                      English
                  language_code:
                    type: string
                    description: >-
                      language code required field if don’t specify
                      language_name you can receive the list of available
                      languages with their language_code by making a separate
                      request to
                      https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages
                      Note: this endpoint currently supports these languages
                      only; example: en
                  tag:
                    type: string
                    description: >-
                      user-defined task identifier optional field the character
                      limit is 255 you can use this parameter to identify the
                      task and match it with the result you will find the
                      specified tag value in the data object of the response
                required:
                  - keywords
                allOf:
                  - anyOf:
                      - required:
                          - language_name
                      - required:
                          - language_code
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  version:
                    type: string
                    description: the current version of the API
                  status_code:
                    type: integer
                    description: >-
                      general status code you can find the full list of the
                      response codes here
                  status_message:
                    type: string
                    description: >-
                      general informational message you can find the full list
                      of general informational messages here
                  time:
                    type: string
                    description: total execution time, seconds
                  cost:
                    type: number
                    description: total tasks cost, USD
                  tasks_count:
                    type: integer
                    description: the number of tasks in the tasks array
                  tasks_error:
                    type: integer
                    description: >-
                      the number of tasks in the tasks array returned with an
                      error
                  tasks:
                    type: array
                    items:
                      type: string
                    description: array of tasks
                  tasks.id:
                    type: string
                    description: >-
                      task identifier unique task identifier in our system in
                      the UUID format
                  tasks.status_code:
                    type: integer
                    description: >-
                      status code of the task generated by DataForSEO; can be
                      within the following range: 10000-60000 you can find the
                      full list of the response codes here
                  tasks.status_message:
                    type: string
                    description: >-
                      informational message of the task you can find the full
                      list of general informational messages here
                  tasks.time:
                    type: string
                    description: execution time, seconds
                  tasks.cost:
                    type: number
                    description: total tasks cost, USD
                  tasks.result_count:
                    type: integer
                    description: number of elements in the result array
                  tasks.path:
                    type: array
                    items:
                      type: string
                    description: URL path
                  tasks.data:
                    type: object
                    description: >-
                      contains the same parameters that you specified in the
                      POST request
                  tasks.result:
                    type: array
                    items:
                      type: string
                    description: array of results
                  tasks.result.language_code:
                    type: string
                    description: >-
                      language code in a POST array if there is no data, then
                      the value is null
                  tasks.result.items_count:
                    type: integer
                    description: the number of results returned in the items array
                  tasks.result.items:
                    type: array
                    items:
                      type: string
                    description: array of items with relevant traffic estimation data
                  tasks.result.items.keyword:
                    type: string
                    description: target keyword in a POST array
                  tasks.result.items.keyword_intent:
                    type: object
                    description: search intent data relevant for the specified keyword
                  tasks.result.items.keyword_intent.label:
                    type: string
                    description: >-
                      search intent name possible values: informational,
                      navigational, commercial, transactional
                  tasks.result.items.keyword_intent.probability:
                    type: number
                    description: >-
                      search intent probability 1 indicates the highest
                      probability
                  tasks.result.items.secondary_keyword_intents:
                    type: array
                    items:
                      type: string
                    description: >-
                      contains objects with other possible search intents for
                      the specified keyword
                  tasks.result.items.secondary_keyword_intents.label:
                    type: string
                    description: >-
                      search intent name possible values: informational,
                      navigational, commercial, transactional
                  tasks.result.items.secondary_keyword_intents.probability:
                    type: number
                    description: search intent probability
        '400':
          description: Bad request
        '401':
          description: Unauthorized
        '429':
          description: Rate limit exceeded
        '500':
          description: Internal server error
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.