> ## Documentation Index
> Fetch the complete documentation index at: https://dev.jolts.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Common questions

> What Jolts does, who it helps, and what to expect before you connect.

## What does Jolts do?

Jolts helps an AI assistant research companies. It returns matching companies, the activity reported
about them, and supporting sources. Use those results to decide which companies deserve a closer
look. A match is not a promise that a company will buy your product.

## Who is it for?

Founders, salespeople, and go-to-market teams researching potential business customers. For example,
a seller of charging equipment can look for companies with relevant procurement requests, then
review the source before reaching out. See [company-list workflows](/workflows).

## Do I need to write code?

Not to ask questions after a compatible AI assistant has been connected. Someone still needs to
create an API key and configure the connection. MCP is the connection standard that lets the
assistant discover and use Jolts' tools. The [connection guide](/mcp) explains the requirements.

Developers can also call the HTTP API from their own software. This is the same company-data
service, not a separate subscription or a different dataset.

## Which programming languages can use the API?

Any language that can send HTTPS requests with headers and read JSON. The API Reference includes
request examples for cURL, Python, JavaScript, Ruby, PHP, Go, and Java. Choose a language in the code
panel on an endpoint page. These are HTTP examples, not a claim that Jolts supplies a dedicated SDK
for each language. Keep API keys on your server, not in a public website's JavaScript.
See the [language prerequisites](/quickstart#choose-how-to-connect) before running an example.

## Which AI assistants can connect?

The current data server requires remote Streamable HTTP and an `Authorization: Bearer` header.
Client support depends on the client's version and configuration. Jolts does not currently implement
OAuth for this server, so an OAuth-only connector will not work. Do not assume that every assistant
with an “MCP” setting supports this authentication method. See [MCP setup](/mcp).

## What data is available today?

The implemented observation types are procurement requests and facility expansions in Canada and
the United States. Coverage is partial. You can ask a natural-language company question, but that
does not make unsupported countries, events, or data fields available.

Jolts does not currently provide personal email addresses, phone numbers, personal profiles, or
contact enrichment. It does not send outreach. [Understand your results](/evidence) explains the
difference between an observed fact and a possible sales opportunity.

## Can I get a list, or only research one company?

Both. Company search returns a list with supporting observations. You can include or exclude
known company IDs and domains, continue through available pages, and open a returned company or
observation for more detail. A detail read uses currently available evidence; it is not a new
research job or a full company profile.

## Does a result mean the company is ready to buy?

No. An explicit request is stronger evidence of an expressed need than an indirect signal, but
neither proves budget, purchasing authority, or a future sale. Confidence describes an observation,
not the probability of closing a deal. Check the source and dates before using a claim in outreach.

## Why did my search return nothing?

An empty completed result is not an error and does not prove that no prospect exists. It can mean
the available evidence does not match your question and filters. Review the query, supported
coverage, and exclusions. An error response is different: read its error code and follow
[troubleshooting](/troubleshooting).

## Is everything real-time or independently verified?

Do not assume either. Each observation includes dates, confidence, and evidence. Several references
can repeat one original source; they are not necessarily independent verification. Evidence can
expire or be withdrawn. Read the returned coverage limitations rather than assuming an exhaustive
or always-current view of a company.

## Do I need a subscription and an API key?

Yes for searches: use an account-scoped API key and an active or trialing subscription. A key alone
does not activate a plan. All keys on the same subscription share limits. MCP tool discovery can
succeed without search access; discovering tools is not proof that a paid operation will run.
See [authentication](/authentication).

## Will retrying charge me again?

An identical retry using the same request key refers to the same operation. Polling its status does
not start another search. A new key means new work; use one for a changed query or the next page.
Do not automatically generate new keys when a request times out. First retrieve or retry the
original operation. [Workflows](/workflows) explains usage and pagination.

## What should I share when asking for help?

Share the operation's `usage.id`, the error code, the affected tool or endpoint, and what you expected.
Remove confidential query details. Never send an API key, authorization header, password, or a
screenshot containing credentials. A support assistant cannot establish your private account
status from public documentation alone.