> ## 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. # Poll an Oxylabs LLM Job > Fetch an Oxylabs LLM job submitted by post_oxylabs_llm, by its jobId. Fetch an Oxylabs LLM job submitted by [`post_oxylabs_llm`](/docs/api-reference/search/post_oxylabs-llm), by its `jobId`. Returns the same envelope — `id`, `status`, `createdAt`, `completedAt`, `pricing`, `output`, `error`. Repeat until `status` is `completed`, `failed`, or `cancelled`; on success `output` carries `results[]` with the parsed answer text and cited sources. Reads a job only; it cannot start one. **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). [Set this endpoint up in your agent →](https://aisa.one/mcp?from=/api-reference/search/get_oxylabs-llm-job) ## OpenAPI ````yaml openapi/oxylabs.json GET /oxylabs/llm/{jobId} openapi: 3.0.0 info: title: Oxylabs AI Search API version: 1.0.0 description: >- Oxylabs answer-engine access for GEO/AEO (Generative / Answer Engine Optimization) exposed through the AIsa gateway. Oxylabs splits answer engines across two integration styles: - **LLM sources — ChatGPT, Gemini, Perplexity** — are asynchronous (Oxylabs Push-Pull). Submit a job with `POST /oxylabs/llm`, then poll `GET /oxylabs/llm/{jobId}` until it is terminal. These sources take ~40–90s, so they cannot be served synchronously. - **Google sources — Google AI Overviews (`google_search`) and Google AI Mode (`google_ai_mode`)** — are synchronous: call `POST /oxylabs/ai-search` and get the parsed answer back in the same response (~4–8s). Both return the AI-generated answer text together with the cited source URLs, so you can monitor how a brand or product is surfaced and cited across AI answers. The async LLM job is billed a flat $0.00145 per successful job; the synchronous Google endpoint is billed a flat $0.001 per successful result. Only successful responses are billed; 400/429/5xx/6xx and upstream 4xx are not billed. servers: - url: https://api.aisa.one/apis/v1 security: - bearerAuth: [] paths: /oxylabs/llm/{jobId}: get: tags: - https://developers.oxylabs.io/scraper-apis/web-scraper-api/ai-sources summary: Poll an asynchronous Oxylabs LLM job. description: >- Fetch an Oxylabs LLM job submitted by `post_oxylabs_llm`, by its `jobId`. Returns the same envelope — `id`, `status`, `createdAt`, `completedAt`, `pricing`, `output`, `error`. Repeat until `status` is `completed`, `failed`, or `cancelled`; on success `output` carries `results[]` with the parsed answer text and cited sources. Reads a job only; it cannot start one. operationId: get_oxylabs_llm_job parameters: - in: path name: jobId required: true schema: type: string description: The job id returned by the submit call. responses: '200': description: The current state of the LLM job. content: application/json: schema: $ref: '#/components/schemas/AsyncJob' components: schemas: AsyncJob: type: object description: >- An asynchronous Oxylabs LLM job. Returned by the submit call (HTTP 202) and by the poll call. Poll the job by its id until status is terminal (completed, failed, or cancelled). properties: id: type: string description: Unique AIsa job identifier. Use it to poll or cancel the job. example: async_job_351d6f429fb6fbe8f505f7d12bfe56b30739a210 object: type: string description: Always "integration_async_job". example: integration_async_job endpoint: type: string description: The submit endpoint this job belongs to. example: /apis/v1/oxylabs/llm status: type: string enum: - queued - running - completed - failed - cancelled description: >- Customer-facing lifecycle status. queued and running are non-terminal; completed, failed, and cancelled are terminal. createdAt: type: string format: date-time description: When the job was accepted. completedAt: type: string format: date-time nullable: true description: >- When the job reached a terminal status. Null while queued or running. pricing: type: object properties: currency: type: string example: USD authorizedMicrosUSD: type: integer description: >- Amount authorized (held) when the job was admitted, in micro-USD. finalMicrosUSD: type: integer nullable: true description: >- Final settled cost in micro-USD once the job is terminal. Null until settlement. Settles at the flat $0.00145 per successful job (1450 micro-USD, normal tier). billingMode: type: string description: Billing mode for the job. example: fixed_request output: nullable: true type: object description: >- Job result payload. Present only once status is completed. Carries `results[]`; the parsed shape inside each entry's `content` varies by source — `chatgpt`/`gemini` return `response_text` plus `citations[]`, and `perplexity` returns `answer_results` / `answer_results_md` (the answer text) with cited sources under `additional_results.sources_results[]`. properties: results: type: array description: >- One entry per query. A single query returns exactly one result, which is the billed unit. items: type: object properties: content: type: object description: >- Parsed answer payload; structure varies by source (see above). error: type: object nullable: true description: Present when status is failed. Null otherwise. properties: code: type: string description: Machine-readable error code. message: type: string description: Human-readable error message. securitySchemes: bearerAuth: type: http scheme: bearer ````