# API integrations

Want to embed Pletor's agents directly into your product? Our API lets you integrate your agents seamlessly into your platform or workflow.

Our API enables:

* **Direct agent execution** from your platform
* **Custom workflow triggers** based on your application events
* **Embedded asset generation** within your user interface

### Availability

API keys are available on **paid plans only**. If you're on the free plan, upgrade to unlock API access.

### Generate your API key

1. Go to **Settings → API Keys** ([direct link](https://app.pletor.ai/?settings=api))
2. Click **Generate API Key**
3. Copy and store your key securely — for security reasons, you won't be able to view it again after closing the dialog

### Quickstart

Test your key with a quick request:

```bash
curl -X GET "https://api.pletor.ai/api/public/v1/agents" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### Agent skills <a href="#agent-skills" id="agent-skills"></a>

Skills are reusable building blocks for common Pletor workflows. They follow the Agent Skills specification and can be used with compatible coding assistants. Get the skill here:

{% file src="/files/FiE28mYWM3PYpeJn6nY7" %}

### Security best practices

* Never commit your API key to version control
* Don't expose your key in client-side code
* Use environment variables in your applications
* Rotate your key if you suspect it's been compromised

### Next steps

Full API reference [available here](https://docs.pletor.ai/documentation/api-reference).


---

# Agent Instructions: 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:

```
GET https://docs.pletor.ai/automate/api-integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.