> For the complete documentation index, see [llms.txt](https://docs.timeseal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.timeseal.com/the-api.md).

# The API

Welcome to the TimeSeal API documentation! This guide will help you integrate and utilize the powerful features of the TimeSeal service seamlessly.

### Getting Started

Before you start using the TimeSeal API, you'll need to sign up for an account and obtain an API key. Follow these steps to get started:

1. **Sign up**: If you haven't done so already, go to the TimeSeal website ([https://www.timeseal.com](https://www.timeseal.com/)) and create a new account. After successful registration, you'll be taken to the dashboard.
2. When you create a new project, an API key specific to that project will be provided to you.
3. **Authentication**: All API requests require authentication using your API key. You need to include the API key in the `Authorization` header of your HTTP requests.

   Example:

   ```makefile
   Authorization: Bearer YOUR_API_KEY
   ```
4. **Base URL**: The base URL for all API endpoints is `https://api.timeseal.com`.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.timeseal.com/the-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.