Search API

Explore the API. Make a real request. Use the code in your application.

API Key & UsageMore

Chatsax API Key

Authorization

Connect your key to run requests with your assigned limits.

Read Full Content of SERP

fullContent

Fetch page content for each result, in addition to its search snippet.

JSON Response

Accept

Include the title, source URL, content and metadata.

With Favicons

X-With-Favicons

Include a favicon URL for each search result.

Country

gl

Two-letter country code for search localization.

City

location

Use a city or region to localize search results.

Language

hl

Language code for the search results.

Pagination

page

Select which page of results to retrieve.

Number of Results

num

Maximum number of returned search results.

Search Within Sites

X-Site

Restrict results to comma-separated domains.

Bypass Cached Content

X-No-Cache

Fetch the latest page instead of a cached copy.

EU Residency

X-Chatsax-Region

Use the upstream experimental EU processing endpoint.

Request
curl 'https://chatsax.com/s/' \
  -H 'X-Respond-With: no-content' \
  -H "Authorization: Bearer $CHATSAX_API_KEY"
Your response will appear here.
API keyNot connected

Find the next useful source.

Turn a question into web results that agents can read, inspect, and cite.

Discover sources

Search from a query instead of starting with a known URL.

Useful controls

Adjust language, region, site restrictions, and result counts.

Readable results

Receive structured results and continue reading selected URLs.

From playground to production.

Use the same request contract in the browser, an HTTP client, or your agent tools. A Chatsax key keeps access and usage separate from the upstream provider account.

Usage & access

Know what your requests use.

Chatsax currently uses invitation-based access. Request limits are assigned to each key; provider usage is recorded when available. No public checkout or standard price plan is offered here.

Your limits

View the current key’s scopes, minute limit, and daily request limit in the dashboard.

Recorded usage

Inspect requests, response status, latency, and available token counts.

Provider costs

Different services count usage differently. A cancelled or long-running request may still consume upstream resources.

Frequently asked questions

Is this a complete web index?

Results are supplied by the upstream search service and may be incomplete or change over time.

Can I restrict sources?

Use supported site and search-region options, then validate sources for your application.

How is Search usage counted?

Provider Search usage differs from text-embedding input usage. Review the response and your dashboard rather than estimating from query length.

Is Chatsax operated by Jina AI?

Chatsax is independently operated. Jina supplies the current underlying APIs; model names and source links identify that provider.