# Sources

Check out the [Sources catalog](/features/sources/sources-catalog.md) if you merely want to look at the Commanders Act sources and how each is implemented.

## Sources vs Destinations <a href="#sources-vs-destinations" id="sources-vs-destinations"></a>

The platform has [Sources](/features/sources.md) and [Destinations](/features/destinations.md). Sources send data *into* the platform, while Destinations receive data *from* the platform.

{% hint style="info" %}
A source is an emitter of events, more information [here](/getting-started/concepts.md#source).
{% endhint %}

## Source key

The source key is a unique identifier for each Source. It allows Commanders Act to identify which Source is transmitting the data and which destinations should be the recipients of that data. It is also employed to deactivate a source when necessary.

To locate a source key, you initially need to have or create a source like a website, server, or mobile source.

Next, within the Source, navigate to “Settings", and then proceed to “source key".


---

# 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://doc.commandersact.com/features/sources.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.