Desearch APIdesearch.ai ↗
Access Desearch API metadata including the base URL, documentation URL, and authorization header details via a single structured endpoint.
What is the Desearch API?
The Desearch.ai API exposes 1 endpoint — get_api_info — that returns structured metadata about the Desearch API itself, including the API base URL, a link to the official documentation, and a full authorization object detailing the header name, expected format, and whether a Bearer token prefix is required. This is a useful bootstrap call for any integration that needs to dynamically resolve Desearch connection parameters at runtime.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/0b585e50-fdfb-458b-8e59-0fd165762a24/get_api_info' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace desearch-ai-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Desearch AI API — retrieve API metadata and authorization details."""
from parse_apis.desearch_ai_api import DesearchAi, AuthError
client = DesearchAi()
# Fetch API info including documentation URL, base URL, and auth details.
try:
info = client.api_info.get()
except AuthError as e:
print("Authentication failed:", e)
raise
print("Documentation:", info.api_documentation_url)
print("Base URL:", info.api_base_url)
# Inspect authorization configuration.
auth = info.authorization
print("Auth header:", auth.header)
print("Format:", auth.format)
print("Uses Bearer prefix:", auth.uses_bearer_prefix)
print("Note:", auth.note)
print("exercised: api_info.get")
Fetches Desearch API metadata including the official documentation URL, the API base URL, and authorization details (header name, format, and whether a Bearer prefix is used). Makes one request to the Desearch docs site.
No input parameters required.
{
"type": "object",
"fields": {
"api_base_url": "string — base URL for Desearch API requests",
"authorization": "object containing header name, format description, uses_bearer_prefix boolean, and a note",
"api_documentation_url": "string — URL of the official Desearch API documentation"
},
"sample": {
"data": {
"api_base_url": "https://api.desearch.ai/desearch",
"authorization": {
"note": "Do not prefix the key with Bearer unless your Desearch account or SDK explicitly instructs you to. Use the exact key value shown when the key is generated.",
"format": "Raw API key (no Bearer prefix)",
"header": "Authorization",
"uses_bearer_prefix": false
},
"api_documentation_url": "https://www.desearch.ai/docs/guide/introduction/desearch-ai"
},
"status": "success"
}
}About the Desearch API
What the API Returns
The single get_api_info endpoint returns three top-level fields: api_base_url, api_documentation_url, and authorization. The api_base_url field gives you the root URL against which all Desearch API requests are made. The api_documentation_url field is the canonical link to Desearch's official developer documentation.
Authorization Object
The authorization object is the most structured part of the response. It contains the header name to use when authenticating requests, a human-readable format description, a uses_bearer_prefix boolean indicating whether the token should be prefixed with Bearer , and a note field with any additional context about authentication behavior. Together these fields let you construct a correctly formatted auth header without guessing.
Intended Use
This endpoint is suited for tooling that needs to programmatically discover or validate Desearch API connection details — for example, a configuration layer that bootstraps API clients, a developer onboarding workflow, or an integration test that checks connectivity parameters before making substantive calls. Because get_api_info takes no inputs, it can be called without any prior knowledge of the Desearch API surface.
The Desearch API is a managed, monitored endpoint for desearch.ai — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when desearch.ai changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official desearch.ai API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Bootstrap an API client by resolving the Desearch base URL at runtime rather than hardcoding it.
- Validate that an integration is targeting the current Desearch API base URL before making data requests.
- Programmatically retrieve the
authorizationheader name and format for use in automated credential setup flows. - Check the
uses_bearer_prefixboolean to handle token formatting correctly in multi-API authentication middleware. - Surface the official Desearch documentation URL dynamically inside internal developer portals or wikis.
- Run a lightweight connectivity check in CI pipelines that confirms Desearch API metadata is reachable.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Desearch have an official developer API?+
get_api_info endpoint returns the URL of the official documentation directly in the api_documentation_url field.What exactly does the `authorization` object contain?+
uses_bearer_prefix boolean, and a note with supplementary context. Together they describe exactly how to construct a valid authorization header for the Desearch API.Does this API expose any of Desearch's actual search or data endpoints?+
Can the endpoint be filtered or parameterized to return only part of the metadata?+
get_api_info takes no input parameters and always returns the full metadata object. It does not support filtering to a subset of fields. You can fork the API on Parse and revise it to expose parameterized or partial responses if your use case requires that.