Jina AI Reader
Jina AI Reader is a powerful URL summarization and web search service that uses advanced neural search technology to fetch, process, and summarize web content. The Jina AI Reader connector enables you to extract and summarize content from web pages, perform neural web searches, and retrieve structured information from URLs. This connector is particularly useful for applications that need to extract content from web pages, perform intelligent web searches, analyze web content, or build content aggregation systems.
Power end-to-end data operations for your Jina AI Reader API with Nexla. Our bi-directional Jina AI Reader connector is purpose-built for Jina AI Reader, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Jina AI Reader or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Jina AI Reader workflows fast, secure, and fully governed.
Features
Type: API
- Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
- Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
- API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
- Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Prerequisites
Before creating a Jina AI Reader credential, you'll need to obtain an API key from your Jina AI account. Jina AI provides API keys for programmatic access to their Reader service through the API dashboard.
To obtain a Jina AI API key:
-
Log in to your Jina AI account at
https://jina.aior create an account if you don't have one. -
Navigate to the API dashboard at
https://jina.ai/api-dashboard/or access it from your Jina AI account settings. -
In the API dashboard, locate the section for API key management. This is typically found in your account settings or a dedicated API/Developer section.
-
Click Create API Key or Generate New Key to create a new API key for your application.
-
Copy the API key immediately after generation, as it may only be displayed once for security purposes. Store it securely, as you'll need it to authenticate API requests.
For detailed information about Jina AI API authentication and API key management, refer to the Jina AI Reader Documentation and Jina AI API Dashboard.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key Value | Yes | Yes |
Create a credential in Nexla
- After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – Jina AI Reader

-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
In the API Key Value field, enter the API key that you obtained from your Jina AI API dashboard. This is the secret API key used to authenticate requests to the Jina AI Reader API.
The API key is sensitive information and should be kept secure. If you've lost your API key, you'll need to generate a new one in your Jina AI API dashboard. API keys are used in the Authorization header as a Bearer token for all API requests.
-
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
Use as a data source
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Jina AI Reader connector tile, then select the credential that will be used to connect to the Jina AI Reader API, and click Next; or, create a new Jina AI Reader credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Jina AI Reader API endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Manual configuration
Jina AI Reader data sources can also be manually configured to ingest data from any valid Jina AI Reader API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom authentication headers and request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Jina AI Reader API endpoints typically follow the pattern https://r.jina.ai/{url-encoded-url} for reading and summarizing URLs, or https://s.jina.ai/?q={url-encoded-query} for web searches. Most Jina AI Reader endpoints use the GET method, and URLs and query parameters must be properly URL-encoded in the endpoint URL.
For Jina AI Reader API responses, common paths to data include $.data for content data or $.data[*] for arrays of results; metadata such as page information, timestamps, or request IDs is typically found at $.meta. You do not need to include authorization headers, as these are automatically included from your credentials, but you may want to include Accept:application/json to specify the response format.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Jina AI Reader data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.