> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/self-service/quickstart-tutorial.md).
# Quickstart Tutorial
Get started with Coresignal's no-code tools. Search, preview, and download fresh B2B data in JSON or CSV – no engineering setup required.
## Get started with no-code tools
If you're new to working with public web data or just looking for a faster way to access it, Coresignal's no-code tools offer a simple starting point. Whether you want to check how many records match your search, explore a subset of the data, or enrich your own files, you can do it all without writing a single line of code.
### Explore data with ease
**Use prompts**. The fastest way to preview the data is through the [**AI Data Search**](https://dashboard.coresignal.com/data-assistant/) and [**API Playground**](/self-service/features-and-tools/api-playground.md#api-playgrounds-environment) where you can test queries and instantly see how many results match your criteria.
## Dashboard
Let's start from the beginning – the dashboard's Home page. On the left, you’ll find quick access to the main features – tools and playgrounds. Your account – settings, details, and team management options are located in the upper-right corner. In the central workspace, you’ll see your API key, subscription plan details, recent queries, and – all in one place for easy navigation and control.
## Credits
We use a credit-based system to manage API usage. You can use credits to download data in **JSON**, **JSONL**, or **CSV** formats. Read more about the API credits in [Pricing](/pricing/pricing.md) page.
## Data download options
You can download data records by either calling our APIs directly or simply using our self-service platform.
{% hint style="info" %}
Please note that if you collect records one by one, you will get them in JSON format. For easier data processing, if you use the bulk download option, you can download data in JSONL or CSV format.
{% endhint %}
### Differences between JSON and JSONL files
**JSON (JavaScript Object Notation) files:** JSON files store data as a single, hierarchical structure, typically as an object or an array within curly or square brackets. Data in JSON files is one complete data structure.
**JSONL (JSON Lines) files:** JSONL files store data as individual JSON objects, each on a new line. Each line is a valid JSON object, but the file as a whole is not a valid JSON object because the objects are not enclosed within a larger array or object.
JSONL format is ideal for handling large datasets as it enables incremental processing of data. This is especially valuable for machine learning applications or for processing large datasets.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.coresignal.com/self-service/quickstart-tutorial.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
