> ## 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.

# BytePlus Fetch

> Fetch a URL and return clean, structured page content — title, body text, and publish time.

Fetch a single URL and get back clean, structured page content under `Result.Data` — `Title`, `ContentText` (clean body text), `PublishTime` (Unix seconds), plus `StatusCode` and `Url`. `Url` is required. The response wraps `ResponseMetadata.RequestId` and a `Result` object holding `Data` and `LogId`. Billed a flat \$0.00088 per successful call; failed requests are not charged. Use this to extract full page content for URLs you already have — typically pairing it with [`post_byteplus_web_search`](/docs/api-reference/search/post_byteplus-web-search) results to turn a list of links into readable content for RAG or analysis.


## OpenAPI

````yaml openapi/byteplus-search.json POST /byteplus/fetch
openapi: 3.0.0
info:
  title: BytePlus SearchInfinity API
  version: 1.0.0
  description: >-
    BytePlus SearchInfinity (by ByteDance's BytePlus) exposed through the AIsa
    gateway. Two synchronous endpoints for AI/agent workflows: a real-time web
    search that returns titled results with links and snippets, and a fetch
    endpoint that returns clean, structured content for a single URL. Pair them
    for RAG retrieval augmentation, competitive/PR monitoring, fact-checking,
    and targeted content collection.


    Web Search is billed at a flat $0.00528 per successful call and Fetch at a
    flat $0.00088 per successful call. Only successful requests are billed;
    failures are not charged. Authenticate with your AIsa API key as a Bearer
    token.
servers:
  - url: https://api.aisa.one/apis/v1
security:
  - bearerAuth: []
paths:
  /byteplus/fetch:
    post:
      tags:
        - https://www.byteplus.com
      summary: Fetch clean, structured content for a URL.
      description: >-
        Fetch a single URL and return clean, structured page content — title,
        body text, and publish time. `Url` is required. The response wraps
        `ResponseMetadata.RequestId` and a `Result` object with the parsed
        content. Use it to extract full page content for URLs you already have,
        typically pairing it with `post_byteplus_web_search` results. Billed at
        a flat $0.00088 per successful call; failed requests are not charged.
      operationId: post_byteplus_fetch
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                Url:
                  type: string
                  description: The URL to fetch. Required.
                  example: https://example.com
              required:
                - Url
            examples:
              basic:
                summary: Fetch a page
                value:
                  Url: https://example.com
      responses:
        '200':
          description: >-
            Fetch completed successfully. `Result` holds the structured page
            content.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ResponseMetadata:
                    type: object
                    description: Upstream request metadata.
                    properties:
                      RequestId:
                        type: string
                        description: Unique identifier for this request.
                      Action:
                        type: string
                      Version:
                        type: string
                      Service:
                        type: string
                      Region:
                        type: string
                  Result:
                    type: object
                    description: Fetch result payload.
                    properties:
                      Data:
                        type: object
                        description: Structured page content.
                        properties:
                          StatusCode:
                            type: integer
                            description: HTTP status code of the fetched page.
                          Url:
                            type: string
                            description: The fetched URL.
                          Title:
                            type: string
                            description: Page title.
                          PublishTime:
                            type: integer
                            description: >-
                              Detected publish time as Unix seconds (0 if
                              unknown).
                          ContentText:
                            type: string
                            description: Clean body text extracted from the page.
                      LogId:
                        type: string
                        description: Upstream log id (equals ResponseMetadata.RequestId).
              examples:
                success:
                  summary: Live gateway 200 response
                  value:
                    ResponseMetadata:
                      RequestId: 20260904155514D7EA140BFD77348BC3FC
                      Action: ''
                      Version: ''
                      Service: ''
                      Region: ''
                    Result:
                      Data:
                        StatusCode: 200
                        Url: https://example.com
                        Title: Example Domain
                        PublishTime: 0
                        ContentText: >-
                          This domain is for use in documentation examples
                          without needing permission. Avoid use in operations.

                          Learn more
                      LogId: 20260904155514D7EA140BFD77348BC3FC
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer

````