> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/release-notes.md). # Release Notes *** ### 2.1.4-r.1 - August 8, 2026 #### What's New **Improved Retention for Identity Proofing Records and Face Match Accuracy** Identity proofing records — both identity verification results and individual face verification attempts — are now retained for 7 days, giving teams a consistent window for troubleshooting, audit, and downstream retrieval. Previously, these records expired too quickly to retrieve or investigate results in time. Face matching has also been tightened to reduce false positives, lowering the chance that a similar but different face is incorrectly accepted. #### Bug Fixes Fixed an issue where Puerto Rico Driver's License and State ID documents could return incorrect dates during identity verification, which could cause verification to fail. These documents now return the correct date of birth, expiry, and issue dates. *** ### 2.1.3-r.1 - July 11, 2026 #### What's New **Enhanced Device Context Visibility for Identity Verification Sessions** To improve troubleshooting and root-cause analysis of document verification failures, 1Kosmos now captures and displays additional device signals, including Device model information, Image capture resolution, and additional device and browser context used during document capture, within the **Verification Session Details** section of the **View Results** page. **Enhanced Selfie Liveness Retry Configuration** The selfie liveness retry experience for Identity Verification (IDV) has been enhanced with a configurable Max Retry Count (liveness.max\_retry\_count) setting. By default, users are now allowed up to three selfie retry attempts before the verification follows the configured fallback path. Administrators can configure the maximum retry count from 1–10. {% hint style="info" %} **Note**: * The **E\_IDV\_SELFIECAPTURE** event now includes the following fields: * attempt\_number * max\_retry\_count * retries\_remaining * result (retry, success, or fail) * reason (quality or confidence, for retry events) {% endhint %} **API Enhancements** * Added a new ID Proofing endpoint, **POST /proofingsession/{id}/fetch/details**, that returns a proofing session and its session results in a single request, with optional filtering by certificate type. * The DVCID create and update APIs now accept additional properties within the `bypassConfig` object, beyond the standard `enabled` and `criteria` fields. *** ### 2.1.0-r.3 — June 13, 2026 #### What's New **Identify US Real ID Compliance During Document Scanning** The Session Details summary now includes a realIDDetectionStatus parameter indicating whether a scanned document contains the US Real ID star marking. This provides additional transparency during identity verification and helps determine whether a document meets the US Real ID standard. **Retry Document Scanning Without Camera Orientation Issues** Users can now retry document scanning without encountering camera orientation errors, ensuring a consistent and accurate capture experience across retries. **Analyze IDV Sessions Faster with AI-Generated Summaries** 1Kosmos now provides AI-generated summaries for Identity Verification sessions, helping administrators quickly understand verification outcomes without reviewing detailed session data. Each summary is organized into three sections, Session Overview, Failure Reasons, and Key Findings and Recommendations, providing clear, actionable insight into verification results. #### API Enhancements **Perform Selfie-Based Identity Identification via API** A new POST /v1/identify\_selfie endpoint has been added to the 1K Wallet API, enabling applications to perform selfie-based identity identification and retrieve a unique face identifier for biometric verification workflows. #### Bugs Fixed * Fixed an issue where the document scanning camera preview appeared mirrored after an unsupported document was detected during verification. *** ### 1.13.00 — May 15, 2026 #### What's New **Session Summary UI Enhancement for Missing Name Field** The Session Summary has been updated to handle cases where the Name field is unavailable. The field now displays -- instead of appearing blank, ensuring a consistent and clear user interface representation. **Faster LiveID Selfie Startup** LiveID selfie now starts instantly when users open the selfie screen, eliminating the initial loading delay previously experienced. The following performance improvements have been made: Performance improvements apply on first-time access. There is no impact when LiveID selfie is disabled. **Improved User Experience for Front-Only Documents** Documents that only require front-side scanning — including Health Insurance Cards, Metis Cards, PAN Cards, and certain Driver's Licenses in India — no longer prompt users for back-side scanning. This prevents "document not supported" errors and streamlines the capture experience. Additionally, the Data Extracted section on the session UI no longer displays system-derived Date of Issue and Date of Expiry values for PAN cards. Since PAN cards do not contain these fields, they are now correctly shown as N/A. This change applies to all customers. **Fraud Detection UI — Enhanced Checks Breakdown** The Fraud Detection section in the verification results UI has been enhanced to display a more detailed and structured breakdown of fraud checks. Checks are now organized into five categories: * Extracted Data Check (previously labeled "Data"): Includes match check, logic check, field format check, barcode authenticity, suspicious data check, data integrity check, and MRZ check. * Document Liveness: No changes to this category. * Visual Check (new): Displays visual fraud indicators including photo forgery check, security features, and generative AI detection. * Document Validity: Displays expiry and version validation checks. * Image Quality: Displays image quality evaluation results. This enhancement improves transparency by exposing detailed fraud signals within each category, enabling better analysis and troubleshooting of verification results. **Enhanced Session Status in /result API** The /result API now returns granular session states, differentiating between: * Pending — session has been created but not yet started by the user. * In Progress — the user has actively begun the verification process. This aligns the API response with the AdminX interface, ensuring consistent and accurate session tracking for integrations. **Improved Middle Name Matching During Verification Sessions** Name matching when Ignore Middle Name is enabled has been improved for greater accuracy. The system now validates matches based on the presence of all entered name parts, without reducing the match score due to additional names in the document result. Matching is order-independent and requires all entered name parts to be present. Examples: * "Jean Chavez" matches "Jean Carlos Chavez Reyes" ✓ * "Jean C. Chavez" matches "Jean Carlos Chavez Reyes" ✓ * "Chavez Jean" matches "Jean Carlos Chavez Reyes" ✓ * "Jean Chavez Lopez" does not match "Jean Carlos Chavez Reyes" ✗ (name not found) **Selfie Liveness Retry Enhancement** The selfie liveness verification experience has been enhanced with a new retry screen to improve user guidance and reduce failures caused by image quality issues. Previously, selfie liveness verification required both a confidence score and an image quality score to meet the configured threshold for a successful result. With this update, image quality no longer directly causes a liveness failure. Instead, users are guided to retry selfie capture when image quality conditions are not optimal, helping improve completion rates and overall user experience. The retry flow continues until selfie verification succeeds or the configured retry count is exhausted. **Gender Display on Extracted Documents** The Data Extracted section on the session UI now displays gender as M (Male) or F (Female) for passport and driver's license documents, aligning with the official document format. Previously, gender was displayed as numeric values 1 and 2. **Flexible Search for "Completed By" Filter** The Completed By filter in session search now supports flexible search using partial names, full names, first name, or last name, returning matching sessions across all statuses. If no date range is specified, the search defaults to the last 30 days. > Note: Since this feature performs partial matching across non-indexed fields, higher response latency may be observed and is expected behavior. **Accessibility Support for Verification Pages** Accessibility support has been introduced across Verification pages, improving screen reader compatibility, keyboard navigation, and overall user experience. **Improved Handling for Under-21 Document Verification** A bypass configuration has been introduced to support verification of users under 21 years of age using US-issued IDs and Driver's Licenses. #### API Enhancements **Enhanced LiveID Authentication Endpoints** A new optional boolean parameter skip\_liveid has been introduced to the LiveID authentication endpoints. When set to true, liveness detection and face comparison checks are bypassed, while face search/recognition and the standard wallet lookup flow continue as normal. This parameter defaults to false. Affected endpoints: * POST /v1/:tenantId/community/:communityId/authenticate\_with\_liveid * POST /v2/authenticate\_with\_liveid {% hint style="info" %} **Note:** These are LiveID authentication endpoints. When `skip_liveid` is set to `true`, liveness detection and face comparison are bypassed, while face search/recognition and the standard wallet lookup continue as normal. The parameter defaults to `false`. {% endhint %} **New POST /identify\_selfie Endpoint** A new POST /identify\_selfie endpoint has been added to the Wallet API. This endpoint performs face identification and returns a face key, enabling face identification without requiring a full authentication flow. *** ### 1.12.08.03 — April 11, 2026 #### What's New **IAL2 Verification Support for Global Entry and Green Card** Web Identity Wallet now supports Green Card (May 2010 or later) and Global Entry Card for IAL2 requirements. SSN enrollment is enabled once a qualifying document is present. **Improved Verification Success Rate — Extended Name Matching to Last Names** The Ignore middle names capability now supports last name matching in addition to first name comparison. When enabled, the system compares the first word of the first name and the last word of the last name. This setting is now available as a global configuration under the Data Comparison section in AdminX. **Enhanced ID Verification Reports** Reports now include Region, Country, Document Types, and Completed By fields. The "Name" column has been renamed to "Created For". #### API Enhancements * New API added to update proofing templates using verification flows. #### Bug Fixes * Fixed an issue where the "Overall Recommendation" (IDV status) was not displayed to Helpdesk Admin users * Fixed pagination issue where deleting the last record did not navigate to the previous page in Verification Flows * Fixed an issue where scanned document images and selfies failed to render in Microsoft Edge on the Session Details page *** ### 1.12.04.01 — March 14, 2026 #### What's New **Okta BYO IDV Integration** Organizations can now integrate Okta BYO IDV with 1Kosmos to verify identities during onboarding and Self-Service Password Reset (SSPR). See Okta 1Kosmos Identity Verification Integration. **High-Resolution Image Support for Verification** Document capture and image processing now support high-resolution images, improving verification success rates and reducing upload failures. Users see a progress indicator during upload. See Using High-Resolution Images to Improve Verification Success. **AI-Powered ID Proofing Insights \[Beta]** Community administrators or users with the ai.chat\_bot.access permission can now access AI-driven ID Proofing insights via the AdminX chatbot using natural language queries. Capabilities include: session summaries, failure rates, document metrics, regional trends, and tenant-specific insights. See AI-Driven ID Proofing Metrics and Insights. **Verification Filters UI Enhancements** * The None value in the Capture Type field on Session Details is deprecated and removed — now shows only "Auto" and "Manual" * The Review Result and Capture Type filters on the verification list page have been deprecated and removed #### Bug Fixes * Fixed an issue where renewing an expired Affidavit did not restore the user's IAL level from IAL1 back to IAL2 * Fixed an issue where failure reasons were not displayed in the exported IDV report * Fixed an issue in ID Proofing selfie liveness capture where liveness verification consistently failed when the user was positioned at the farthest point * Fixed session status displaying inconsistently across the Verifications list page, Session Details, and downloaded reports * Fixed an issue where Identity Verification reports could not be downloaded for specific journeys * Fixed an issue in IDVerification Analytics where chart data was displayed incorrectly in the 7-day view due to time zone difference *** ### 1.12.01.01 — February 14, 2026 #### What's New **Expiry Status Indicators for Enrolled Documents** The AdminX interface now displays expiry status for previously enrolled documents and affidavits in the Identity Wallet tab under My Profile. Two indicators are displayed: * Expiring Soon — for documents expiring within 30 days * Expired — for documents that have already expired, prompting re-enrollment **Manual Document Capture When Auto Capture Fails** Community administrators or users with permission to configure DVCIDs can now manually capture an identity document if automatic capture fails after a timeout. Depending on backend configuration, users will see a Manual Capture button or a countdown-based capture. Supported in both v1 and v2 verification flows. See Verification Journey. **Manual Review of Verification Sessions** Community administrators or users with the idproofing.manual-review permission can now review certain ID verification sessions later or offline. When used, the session moves into a Review state. Users can filter sessions by: status, overall recommendation (including 'review'), review result (approved/rejected/review pending), and fallback capture mode. An E\_IDV\_MANUAL\_REVIEW\_DECISION event is triggered after the user approves or rejects the ID proofing session. **Review Status in Usage Analytics** The Usage Analytics page under Verification > Analytics now displays the Review status in the Verifications Breakdown tile. **Enhanced Name Matching for Identity Verification** A new Ignore Middle Names option is now available in the AdminX verification flow configuration. When enabled, middle names are excluded from name comparison during ID proofing, reducing false failures caused by middle name mismatches between directory data and identity documents. See Configuring Verification Flows. **Configuring Data Retention Based on Session Outcome** Administrators can now configure data retention policies based on ID verification session outcomes for each outcome type: Success, Failed, Not Performed, Review, and Abandoned. Available when creating a verification flow using the KYC with Face Comparison journey. See Configuring Verification Flows. **New Permission — idproofing.manual-review** Added to control access to the manual review functionality. #### Bug Fixes * Fixed an issue where the selfie\_liveness "skip": true setting in the DVCID face\_liveness configuration was overridden if a user opened and saved the V2 DVCID settings in the UI, even without making any changes. *** ### 1.12.00.01 — January 10, 2026 #### Miscellaneous * Updated site description for ID proofing session URLs to: "Secure link to complete identity verification" * Added warning message "Provide another tag, this tag already exists" to the Unique Tag field in Create Verification Flow #### Bug Fixes * Fixed an issue where ID proofing sessions failed with an unsupported document error when the template did not include a consent or Start Now screen *** ### 1.11.09.01 — December 13, 2025 #### What's New **Automatic Camera Selection During Document Scan** Administrators can now use the new camera\_enforcement property in the ID proofing template to specify whether the front or back camera should be used during document scanning. Values: front, back, or default. > Note: This is part of the V2 DVCID config. **LiveID Capture Enhancements** * Removed repeated "keep your eyes open" prompts under low-light conditions or when wearing glasses * LiveID capture time reduced to 600 milliseconds * The capture circle now turns red when no face is detected and light green when a face is recognized; a darker green animated ring shows capture progress * New UI guidance messages: "Center your face in the circle", "Move closer", "Move back a little", "Keep your head level", "Face the camera directly" {% hint style="info" %} **Note:** * These are LiveID authentication endpoints. Setting `skip_liveid` to `true` bypasses liveness detection and face comparison, while face search/recognition and the standard wallet lookup continue as normal. * These enhancements apply to the LiveID selfie-capture experience and are used across both identity verification and LiveID login flows. {% endhint %} **Optimized Camera Permissions Overlay During Document Scan** Fixed an issue where granting camera permissions after a 40-second idle caused a "No camera detected" error. Once permission is granted, the camera now opens correctly. #### Bug Fixes * Resolved an issue where v2 DVCIDs configured with only SSN, Face Compare, or AAMVA checks would trigger errors in the Verify API after migration from v1 * Resolved intermittent failures when downloading ID Proofing reports *** ### 1.11.08 — November 15, 2025 #### What's New **Improved SSN Verification Success Rate** Name matching requirements for SSN document checks have been relaxed — verification will no longer fail due to minor name differences between SSN data and the ID document. #### API Enhancements * The {{tenantDNS}}/api/r1/community/{{community\_name}}/userid/johndoe/ial API now includes the expiry date (YYYYMMDD format) for all documents enrolled in the wallet #### Bug Fixes * Fixed LiveID capture failing during identity verification on Android and iOS with "Face not found" error *** ### 1.11.06.01 — October 10, 2025 #### What's New **Configure Identity Verification Flow Through UI** Community administrators with the idproofing.add-journey permission can now configure and manage custom ID verification journeys in AdminX under Verification > Verification Flows. Key capabilities: creating and managing journeys, generating and sharing session links, editing or deleting journeys, and defining accepted ID documents by country and region. See Configuring Verification Flows. **Granular Document Controls for ID Verification** Administrators can now define which identity documents are allowed or blocked during the ID Verification journey — by country, region, and document type. A new event E\_IDV\_DOCUMENT\_NOT\_ALLOWED is triggered with full metadata when a user scans a blocked document. **Enhanced IAL2 Identity Verification Flow** Users can now enroll their LiveID to a wallet, enabling future comparisons against identity documents stored in the wallet. Administrators can configure whether LiveID capture appears within the verification flow or in a separate tab. If the initial selfie session does not start within 2 seconds, a new session is automatically created. **New Form Input Controls** A new form step has been introduced in the verification flow, allowing users to enter information through various input types: text, number, password, email, date, and checkbox fields. *** ### 1.11.04 — September 5, 2025 #### What's New **One-Time IAL2 Identity Verification** Community administrators can now create and manage a one-time Identity Assurance Level 2 (IAL2) verification flow requiring two identity documents, biometric data, and an SSN. User identity data is not stored after verification. See Kantara Certified IAL2 Verification. #### API Enhancements * Session poll API enhanced with a new responseStatus parameter {% hint style="info" %} **Note:** The Session poll API returns the verification session status through the new `responseStatus` parameter, consistent with the V3 Poll API. {% endhint %} #### Deprecated * The expiry timestamp (expiryTs) has been removed from IDProofing event data. Data retention is now handled through dedicated database archiving processes. *** ### 1.11.02 — August 9, 2025 #### What's New **Manual Document Capture Support** The verification UI now supports manual document capture when auto-capture fails. Fallback options include Manual Capture and Retry Auto buttons appearing after a timeout. > Note: Controlled via a configuration flag; may not be available in all environments. **Enhanced V3 Poll API** * Added liveid\_object key containing selfie details * Included rawData for session-level raw information * Added token, reason, reasonCode, and fuzzyMatchScore * Updated resultStatus for sessions where verification was not performed to return NOT\_PERFORMED instead of FAILED #### Bug Fixes * Fixed Take Selfie button remaining disabled even when face is correctly positioned * Fixed "No camera detected" error after a previous document capture attempt failed * Fixed incorrect error codes when scanning expired or photographed documents *** ### 1.11.00 — July 12, 2025 #### What's New **Two New Languages in ID Proofing Templates** Simplified Chinese and Spanish have been added, expanding support to four languages: English, French, Simplified Chinese, and Spanish. **Retry Mechanism for Unsupported Documents** A retry mechanism has been implemented with configurable attempt limits. An E\_IDV\_SESSION\_RETRY event is displayed when a retry attempt is made. **Passport Instructional Text in Vertical Mode** Instructional text during passport scanning is now properly aligned and readable in both vertical and horizontal orientations. **Enhanced SSN Behavior During Verification** When multiple records are returned for the same user, the system now selects the record(s) with the highest idVerificationScore. If a unique match is found, verification proceeds; otherwise it fails gracefully. *** ### 1.10.19 — June 14, 2025 #### What's New **WCAG Compliance for ID Proofing Templates** 1Kosmos has implemented Web Content Accessibility Guidelines (WCAG) compliance for ID Proofing Templates. Voiceover support has been introduced across all screens for visually impaired users. Key elements and instructions are now fully navigable and readable using the keyboard. **reCAPTCHA on Verification Journeys** reCAPTCHA verification has been added to the Verification > Journeys page when an administrator sends a session link via SMS. If reCAPTCHA config is missing, the admin will see: "Recaptcha configuration is missing, please contact your administrator." #### Miscellaneous * New /proofingsession/recaptcha\_config/fetch API added *** ### 1.10.18.01 — May 12, 2025 #### What's New **Retry Mechanism for ID Proofing Sessions** Community administrators can configure the number of retry attempts (default: 2, max: 5) when users fail verification. If the retry count is set above 4, the UI prompts the administrator to correct the configuration. See Verification Journey. #### Bug Fixes * Fixed document enrollment error for IAL2 in SAML/OIDC authentication flow *** ### 1.10.17 — April 12, 2025 #### What's New **Expired and Abandoned Statuses in ID Proofing** Two new statuses added: Expired and Abandoned. * Default expireSessionInMin: 7 days * Default abandonSessionInMin: 1 hour * New events: E\_IDV\_SESSION\_EXPIRED and E\_IDV\_SESSION\_ABANDONED See ID Verification Events. *** ### 1.10.16.01 — March 15, 2025 #### What's New **Adding Affidavit on Behalf of a User** Community/Helpdesk administrators can now add an affidavit to a user's web wallet allowing them to become IAL2 certified without physically scanning documents. Required permissions: user.affidavit.add, users.view-user, users.edit, users.all-users. See Bypassing Verification Using Notarized Documents. > Note: New users will no longer be required to enter a PIN. **Filter Verification Results by Journey Name and UID** Two new filters — Journey Name (DVCID) and UID — have been added to the Verification > Verification page. See Verification Journey. *** ### 1.10.15 — February 21, 2025 #### What's New **Download Verification Results** Community administrators or users with idproofing.reports.verification-sessions-download or idproofing.session-management permissions can now download verification reports from AdminX under Verification > Verification. Reports can be filtered by document type, verification status, and completed by. If the report exceeds 2 million records, users will be prompted to refine their search. See Downloading Verification Reports. *** ### 1.10.14 — January 10, 2025 #### What's New **IAL2 Device Removal Warning** When an end user attempts to remove an IAL2-authenticated device from the Devices tab under My Profile, a warning message now appears alerting them of the impact. *** ### 1.10.13.01 — December 14, 2024 #### What's New **New Verification Status — Verification Not Performed** A new status distinguishes cases where fraud verification could not be completed. Displayed when: * Verification process is partially completed * Front side of document is processed but backside is unclear * Document extraction process fails * Unsupported document is submitted See Verification Journey. *** ### 1.10.12 — November 8, 2024 #### What's New **New Filters for ID Proofing Verification Events** New filter values added: Authenticator ID, Device ID, Mobile Document ID, Mobile Session ID. *** ### 1.10.03 — April 25, 2024 #### What's New **Fraud Detection Panel** Community administrators can now view which specific verification check failed when identity verification is deemed fraudulent. **Confidence Score Retention While Discarding PII** Administrators can selectively discard PII while retaining confidence scores for the verification journey. A new summary object within the session result stores confidence scores for all verification checks. **ID Verification Session Metrics** A new analytics page displays the count of verification sessions completed, passed, and total sessions generated, with a 90-day time-series graph. **Reduced Verification Time** Significant performance optimizations reduce the overall time required to submit images and receive a verification result. *** ### 1.10.00 — February 10, 2024 #### What's New **Web Identity Wallet — ID Cards from Any Country** For tenants subscribing to the web Identity Wallet, 1Kosmos now supports enrollment of ID cards from any country and document. Expired ID cards cannot be enrolled. When enrolled, users can view document details. *** ### 1.09.04 — May 18, 2023 #### What's New **Unenroll Documents from Identity Wallet** Users can now remove identity documents (driver's license, passport, and SSN) from their identity wallet. Once removed, data from the document is no longer available. The user's IAL is recalculated when a document is removed. *** ### 1.09.02 — April 13, 2023 #### What's New **Trigger Identity Verification Flow Using OIDC** OIDC clients can trigger an identity verification flow by including the /assurance/ial/2 custom scope. The platform checks if the user is verified to IAL2 and, if not, triggers a verification flow. #### Improvements and Bug Fixes * Improved page load times for identity wallet document uploads *** ### 1.07.06.01 — January 5, 2023 #### What's New **Trigger IAL2 Verification Using OAuth2/OIDC** Passing ial2 as an acr value on an OIDC claim triggers an authentication journey for users to upload and verify identity documents online, resulting in IAL2 verification. *** ### 1.07.03 and v1.07.04 — November 17, 2022 #### Improvements and Bug Fixes * Silently handled AAMVA timeout responses to allow users to proceed * Fixed Driver's License enrollment to the Identity Wallet when AAMVA verification fails *** ### 1.07.02 and v1.07.03.02 — October 20, 2022 #### Early Access **Verify Identity with Passport** The 1Kosmos Identity Wallet now supports enrollment of a US Passport. For IAL2 credentialing, the user must additionally verify their SSN. **Passport Attributes** The 1Kosmos platform allows the CSP to request passport attributes through SAML or OIDC workflows with user consent. *** ### 1.07.01 and v1.07.00 — September 12, 2022 #### Deprecated * Enrollment of GovID documents by attributes request. Enrollment is now supported based on Authn Context of the incoming request. *** ### 1.06.04 — May 26, 2022 #### What's New **Web-Based Identity Proofing Journey** Introduced a new web-based identity proofing journey with capabilities to: * Allow users to self-enroll and create an account * Create a new identity wallet after registration * View identity documents connected to the user profile * Trigger text messages to scan a GovID * Enroll a driver's license as an identity document * Validate driver's license against AAMVA * Enroll and validate SSN * Triangulation logic to verify Driver's License and SSN belong to the same user * Present data sharing and consent screens * Trigger proofing journeys based on incoming requests from a relying party * New SAML attribute set for sharing identity document data --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.1kosmos.com/identity-verification/release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.